Backend server section

The backend server section defines a back-end server connection. It specifies the information that is used by the Outbound Enabler when it connects to the Relay Server farm on behalf of a back-end server. There is a backend server section for each Outbound Enabler connecting to the Relay Server farm. The backend server section also assigns a back-end server to a back-end server farm.

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

Note

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] http://www.sybase.com/detail?id=1061806 .

This section is identified by the backend_server keyword.

Backend server section properties

The following properties can be specified in a backend server section:

description Enter a custom description to a maximum of 2048 characters. This property is optional.
enable Specifies whether to allow connections from this back-end server. Possible values are:
- Yes Allows connections from this back-end server.
- No Disallows connections from this back-end server.
The default is Yes. This property is optional.
farm The name of the back-end server farm that this back-end server belongs to.
id The name assigned to the back-end server connection, to a maximum of 2048 characters.
MAC The MAC address of the network adapter used by the Outbound Enabler to communicate with the Relay Server. The address is specified using the IEEE 802 MAC-48 format. To get the MAC address in the correct format, look in the Relay Server Outbound Enabler console or log. This property is optional. If it is not specified, MAC address checking does not occur.
token A security token that is used by the Relay Server to authenticate the back-end server connection, to a maximum of 2048 characters. This property is optional.
verbosity You can set verbosity to the following levels:
- 0 Log errors only. Use this logging level for deployment. This is the default.
- 1 Request level logging. All HTTP requests are written to the log file.
- 2 Request level logging. Provides a more detailed view of HTTP requests.
- 3 or higher Detailed logging. Used primarily for technical support.
Errors are displayed regardless of the log level specified, and warnings are displayed only if the log level is greater than 0.

Discuss this page in DocCommentXchange.