Using a Reverse Proxy in Front of Relay Server

Configure a dedicated port for the Relay Server port, and configure separate ports and contexts for each Relay Server farm.

This task implements configuration policies using an Object API application as the example. The configuration details for Hybrid Apps, OData SDK, DOE applications, and REST applications are similar.

Configure one port to serve each Relay Server port.

If you map an /smp/relayserver context of http://reverseProxy:8080 to http://relayServer:80, you must add the /smp/relayserver context as a prefix of the URL suffix of the Relay Server.

For example, set /smp/relayserver/ias_relay_server/client/rs_client.dll as ConnectionProperties.UrlSuffix, and set /smp/relayserver/ias_relay_server/client/rs_client.dll/RBSFarm as the ConnectionProfile.StreamParams.Url_Suffix for synchronization. Set the FarmId separately for ConnectionProperties.
Configure two ports, with each port serving one Relay Server farm.

For example, if you map the root context of http://reverseProxy:5001 to http://relayserver:80/ias_relay_server/client/rs_client.dll/MBSFarm, and map the root context of http://reverseProxy:2480 to http://relayserver:80/ias_relay_server/client/rs_client.dll/RBSFarm, the Object API application then can set connection properties to connect directly to SAP Mobile Server.
Configure two contexts, with each context serving one Relay Server farm.

For example, if you map the /smp/message context of http://reverseProxy:8080 to http://relayserver:80/ias_relay_server/client/rs_client.dll/MBSFarm, and map the /smp/mobilink context of http://reverseProxy:8080 to http://relayserver:80/ias_relay_server/client/rs_client.dll/RBSFarm, the Object API application needs to set the URL suffix (/smp/message for registering the application and /smp/mobilink for synchronization). This is the same as connecting to SAP Mobile Platform through a Relay Server that is not installed at the default location; the only difference is that there no FarmId for a reverse proxy.