active_cookie   Specifies whether or not a cookie is set to retain client-server affinity.

For best results, set this control as follows:

For a MobiLink server back end, setting both active_cookie and active_header to yes should always work. However, setting both to yes may put redundant session information in every HTTP request/response in a session. To potentially save on cumulative on-the-wire byte charges, you may be able to set either active_cookie to no. You should test all network scenarios to make sure the chosen settings work in all cases.

active_header   Specifies whether or not a header is set to maintain client-server session affinity.

backend_security   Specifies the level of security required of an Outbound Enabler in the back-end server farm to connect to the Relay Server farm. The possible values are:

This property is optional. If no value is specified, either HTTP or HTTPS can be used to connect.

client_security   Specifies the level of security the back-end server farm requires of its clients. The possible values are:

This property is optional. If no value is specified, clients can connect using either HTTP or HTTPS.

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 farm. Possible values are:

The default is Yes. This property is optional.

id   The name assigned to the back-end server farm, to a maximum of 2048 characters.

forward_x509_identity   The SAP NetWeaver Gateway provides several means of authenticating clients, including X.509 certificate forwarding through trusted intermediaries. When this property is set to yes, Relay Server can extract forwarded client identity information from a trusted forwarder and forward it to the SAP NetWeaver Gateway or Web Dispatcher using HTTP headers. The default setting is no.

forwarder_certificate_issue   In the case where a chain of SAP intermediaries exists, the client identity headers may already be present in the request. However, not all clients may be granted permission to act as forwarders. The default behavior, therefore, is to replace the existing headers with the identity of the forwarder. To grant permission for a forwarder to forward other client identities, you can set forwarder_certificate_issuer=<match-string> and forwarder_certificate_subject=<match-string>, where <match-string> is checked against a serialized form of the corresponding compound name field in the certificate. You can use '?' to match any character and '*' to match any string. Use '\' as the leading escape character for '?', '*' or '\' if they need to be matched literally.

For example:

forwarder_certificate_issuer = 'CN = quicksigner, OU = security department, O = my org, L = my city, S = my state, C = my country'

forwarder_certificate_subject   In the case where a chain of SAP intermediaries exists, the client identity headers may already be present in the request. However, not all clients may be granted permission to act as forwarders. The default behavior, therefore, is to replace the existing headers with the identity of the forwarder. To grant permission for a forwarder to forward other client identities, you can set forwarder_certificate_issuer=<match-string> and forwarder_certificate_subject=<match-string>, where <match-string> is checked against a serialized form of the corresponding compound name field in the certificate. You can use '?' to match any character and '*' to match any string. Use '\' as the leading escape character for '?', '*' or '\' if they need to be matched literally.

For example:

forwarder_certificate_subject = 'CN = mySapWD??.my.com, OU = Sybase, O = SAP, *'

verbosity   You can set verbosity to the following levels:

Errors are displayed regardless of the log level specified, and warnings are displayed only if the log level is greater than 0.