Consider these on-premise and cloud guidelines when migrating OData applications to
REST API. The guidelines may require coding changes to your application.
- A cloud application may support CAPTCHA if required. If CAPTCHA is enabled,
the application must be able to process the CAPTCHA challenge.
- Applications that support both on-premise and cloud must incorporate logic
to determine the system to which the application should connect. This may
extend to user interface elements that prompt the user to identify the
correct system. You can set up an application to determine the system via
the provided Server URL, but you must implement the logic for this.
- New versions of resource bundles on the server are not automatically pushed
to the applications in the cloud scenario. You must add application logic to
request new resource bundles from the server if needed.
- Security Configuration HTTP Headers are not supported, and are ignored by
the cloud.
- The cloud always uses HTTPS, whereas it is optional in on-premise
scenarios.
- Application connection registration is required in the cloud, whereas it is
optional for on-premise scenarios.
- Domains are not supported in the cloud.
- Application connection templates are not supported in the cloud.
- A subset of the SAP Mobile Platform PUSH registration settings
is available for the cloud scenario, from the full set available for the on
premise scenario.
- Since the cloud enables for cross-site request forgery (XSRF) attacks,
applications used in the cloud must include XSRF token handling logic, if
the back-end service demands it.