Reverse Proxies

Requirements for third party reverse proxies for use with SAP Mobile Platform.

The reverse proxy must be a straight pass-though proxy server. Ensure the reverse proxy meets these requirements:

Does not change the content encoding of the requests or responses. Chunked transfer encoding is the required data transfer mechanism. Content-length encoding is not supported.
Does not remove any HTTP headers.
The timeout period (if any) must be greater than the timeout used by the clients.
The resulting URL that is passed to the SAP Mobile Platform must be http://HostName/[public/]<AppID>, where [public] is optional and if included anonymous connection is allowed. Example, http://suphost/public/empDir.

Using Reverse Proxy for REST application

The REST application needs to communicate to the web service port. Configure the reverse proxy between client and SAP Mobile Server. The reverse proxy can be configured to map client request URL sent to reverse proxy with the URL sent to SAP Mobile Server. The default HTTP port which can be used for communication is 8000. The configuration policies are:

Map the root context of http://reverseProxy:8000 to http://smpServer:8000. The REST application sends a request directly to SAP Mobile Server. For example, http://reverseProxy:8000/odata/applications/v1/empDir and http://reverseProxy:8000/public/empDir.
Map the "/smp/rest" context of http://reverseProxy:8080 to http://smpServer:8000. The REST application needs to add the "/smp/rest" context in request URL. For example, http://reverseProxy:8080/smp/rest/odata/applications/v1/empDir and http://reverseProxy:8080/smp/rest/public/empDir.