
Set up a Relay Server outbound enabler on each SAP Mobile Platform Server in the cluster.
The outbound enabler connects the SAP Mobile Platform Server running in the corporate LAN to the Relay Server farm running in the DMZ.
dbsvc -as -s auto -t rsoe -w oes "%SQLANY16%\Bin<XX>\rsoe.exe" -cr "host=<host_name_or_IPaddress>; port=<host_port>; url_suffix=/rs16/server/rs_server.dll" -cs "host=localhost;port=80" -f <farm_name> -id <server_name>
To set up an auto-started outbound enabler service named oes (Outbound Enabler service) on Apache host on Linux:
dbsvc -y -s auto -a <Apache-user-account> -t rsoe -w oes -cr "host=<host_name_or_IPaddress>; port=<host_port>; url_suffix=/srv/iarelayserver" -cs "host=localhost;port=80" -f <farm_name> -id <server_name>
On either Windows or Linux, you can enter parameters into an outbound enabler configuration file (<oe_config_file>), using same syntax as at the command prompt.
| rsoe Option | Description |
|---|---|
| -cr "<connection-string>" | Specifies the Relay Server connection string. The format
of the Relay Server connection string is a semicolon
separated list of name-value pairs. The name-value pairs
consist of the following:
|
| -cs "<connection-string>" | Specifies the SAP Mobile Platform Server (backend server) connection string.
Sets the host and port used to connect to the back-end
server. The default is
"host=localhost;port=80;https=0". To
enable periodic back-end server status requests, add the
status_url parameter to -cs. The
status_url parameter is specified
in the format
status_url=/<your-status-url>.
The following example shows how to specify
status_url with
-cs.-cs "host=localhost;port=80;status_url=/getstatus/"
|
| -d <seconds> | (Optional) Sets the frequency of the back-end server liveness ping and back-end server status request. The default is 5 seconds. |
| -dl | (Optional) Displays log messages in the Relay Server Outbound Enabler console. By default, log messages are not displayed for verbosity levels 1 and 2. |
| -f <farm> | Specifies the name of the farm that the back-end server belongs to. |
| -id <id> | Specifies the name assigned to the back-end server. |
| -o <file> | (Optional) Specifies the file to log output messages to. |
| -oq | (Optional) Prevents the appearance of the error window when a start-up error occurs. |
| -os | (Optional) Sets the maximum size of the message log files. The minimum size limit is 10 KB. |
| -ot | (Optional) Truncates the log file and logs messages to it. |
| -q | (Optional) Run with a minimized window on start-up. |
| -qc | (Optional) Shuts down the window on completion. |
| -s | (Optional) Stops the Outbound Enabler. |
| -t <token> | (Optional) Sets the security token to be passed to the Relay Server. |
| -uc | (Optional) Starts the rsoe in shell mode. This is the default. Applies to Linux and Mac OS X. You should only specify one of -uc, -ui, -um, or -ux. When you specify -uc, this starts the rsoe in the same manner as previous releases of the software. |
| -ud | (Optional) Runs the rsoe as a daemon. Applies to Linux platforms only. |
| -ui | (Optional) Starts the rsoe in shell mode if a usable display is not available. This
option is for Linux with X window server support. When -ui is specified, the server attempts to find a usable display. If it cannot find one, for example because the X window server is not running, the rsoe starts in shell mode. |
| -ux |
(Optional) For Linux, opens the rsoe messages window where messages are displayed. When -ux is specified, the rsoe must be able to find a usable display. If it cannot find one, for example because the DISPLAY environment variable is not set or because the X window server is not running, the rsoe fails to start. To run the rsoe messages window in quiet mode, use -q. On Windows, the rsoe messages window appears automatically. |
| -v <level> |
(Optional) Set the verbosity level to use for logging. The level can be 0, 1, 2, or
higher (higher levels are used primarily for technical
support):
|