Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 12.0.1 » Relay Server


Outbound Enabler

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:

  • Afaria

  • Mobile Office

  • MobiLink

  • Mobile Office

  • SQL Anywhere

  • Unwired 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 [external link] .

 Outbound Enabler syntax
 File Hiding utility (dbfhide)
 Integrated Outbound Enabler (recommended for MobiLink)
 Deployment considerations
 See also

Outbound Enabler as a service