The Outbound Enabler runs on the same computer as the back-end server. Its purpose is to:
When the Outbound Enabler starts, it makes an HTTP request to retrieve the list of Relay Servers running in the farm. This is done using the server URL that maps to the web server extension component of the Relay Server. The server URL can map directly to a Relay Server or it can map to a load balancer. If the server URL maps to a load balancer, the load balancer forwards the request to one of the Relay Servers running in the farm. The Relay Server that receives the request from the Outbound Enabler returns the connection information for all Relay Servers in the farm. The Outbound Enabler then creates two outbound connections, called channels, to each Relay Server returned. One channel, called the up channel, is created using an HTTP request with an essentially infinite response. The response is a continuous stream of client requests from the Relay Server to the Outbound Enabler. The second channel, called the down channel, is created using an HTTP request with an essentially infinite content length. The request is formed by a continuous stream of server responses to client requests.
When the Outbound Enabler receives a client request on the up channel from one of the Relay Servers it has connected to, it forwards it to the back-end server that the Outbound Enabler is servicing. Once a response is received from the back-end server, it gets forwarded to the Relay Server from which it received the corresponding request using the down channel.
The following back-end servers are supported for use with the Relay Server:
Sybase Unwired Platform
Refer to your license agreement or the SQL Anywhere Components by Platforms page for information about which back-end servers are supported. See http://www.sybase.com/detail?id=1061806 .
Options The following options can be used with the Outbound Enabler. Options that have defaults are optional. At a minimum, the Outbound Enabler needs to supply the connection string for the Relay Server (-cr), the farm (-f) and server (-id) names. If a security token is configured, it must also be specified (-t).
Reads options from the specified environment variable or configuration file. If you want to protect passwords or other information in the configuration file, you can use the File Hiding utility to obfuscate the contents of the configuration file. See File Hiding utility (dbfhide).
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:
For https=1, the following options can also be specified:
For more information, see MobiLink client network protocol options.
Sets the host and port used to connect to the back-end server. The default is
To enable periodic back-end server status requests, add the status_url parameter to -cs. The status_url parameter is specified
in the format
The following example shows how to specify status_url with -cs.
Use the -d option to specify the frequency of the back-end server status requests.
Sets the frequency of the back-end server liveness ping and back-end server status request. The default is 5 seconds.
Use this option to display log messages in the Relay Server Outbound Enabler console. By default, log messages are not displayed for verbosity levels 1 and 2.
Specifies the name of the farm that the back-end server belongs to.
Specifies the name assigned to the back-end server.
Specifies the file to log output messages to.
Prevents the appearance of the error window when a startup error occurs.
Sets the maximum size of the message log files. The minimum size limit is 10 KB.
Truncates the log file and logs messages to it.
Run with a minimized window on startup.
Shuts down the window on completion.
Stops the Outbound Enabler.
Sets the security token to be passed to the Relay Server.
Starts the rsoe in shell mode. This is the default. Applies to Unix 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.
Instructs the rsoe to run as a daemon. This option applies to Unix platforms only.
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 isn't running, then the rsoe starts in shell mode.
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.
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):
Levels 1 and 2 are only written to the log file and are not displayed. To have all log messages displayed, use the -dl switch.
The File Hiding utility (dbfhide) uses simple encryption to obfuscate the contents of configuration files and initialization files.
dbfhide original-configuration-file encrypted-configuration-file
|original-configuration-file||Specifies the name of the original file.|
|encrypted-configuration-file||Specifies a name for the new obfuscated file.|
The Relay Server and Outbound Enabler detect that a configuration file has been obfuscated using dbfhide and process it.
This utility does not accept the @data parameter to read in options from a configuration file.
By using the oe protocol for the -x option for mlsrv12, you can use an integrated Outbound Enabler instead of the stand-alone Outbound Enabler invoked with the rsoe command. Using the integrated Outbound Enabler has the following advantages:
Reduced use of system resources, especially sockets.
Provides a single, integrated log file. Lines printed to the MobiLink server log from the integrated Outbound Enabler will have the prefix <OE>.
Deployment is simplified.
Liveness checks between the Outbound Enabler and the MobiLink server are eliminated.
For more information about how to use the integrated Outbound Enabler, see -x mlsrv12 option.
The following considerations should be noted when using the Outbound Enabler:
Outbound Enabler as a service The Outbound Enabler may also be set up and maintained as a service using the Service utility.
Authentication You cannot use simple or digest authentication. The rsoe.exe does not support simple or digest authentication with web servers, regardless of the web server type or operating system.
Discuss this page in DocCommentXchange.
|Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1|