Backend Server Farm Properties window: General page

This page has the following components:

  • Enable this backend server farm   Click to allow connections from this back-end server farm. The default is selected.

    • ID   Specify the name assigned to the back-end server farm. You can use a maximum of 2048 characters.

    • Client security Protocol   Specify the level of security the back-end server farm requires of its clients. The possible values are:

      • Either HTTP or HTTPS   Select to allow clients to connect using either HTTP or HTTPS. This is the default.

      • HTTP   Select to force clients to connect using HTTP.

      • HTTPS   Select to force clients to connect using HTTPS.

    • Backend security Protocol   Select and specify 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:

      • Either HTTP or HTTPS   Select to allow connections from the back-end farm to use either HTTP or HTTPs. This is the default.

      • HTTP   Select to force all connections from the back-end farm to use HTTP.

      • HTTPS   Select to force all connections from the back-end farm to use HTTPS.

    • Description   Provides a place for you to type a text description of the backend server farm. For example, you could use this area to describe the backend server farm's purpose in the system. You can use a maximum of 2048 characters.

  • Affinity Server type   Specifies the type of backend server. Select SQL Anywhere for SQL Anywhere web services using standalone Outbound Enablers. Select MobiLink for either MobiLink server with embedded Outbound Enabler or MobiLink HTTP server with standalone Outbound Enablers. Select Custom for setting advanced affinity options tailored for the backend servers in your HTTP environment.

    • Active cookie   Specifies whether or not the Relay Server is going to inject a standard HTTP cookie to maintain client-server affinity.

      • If selected, the Relay Server injects a standard HTTP set-cookie command with a proprietary cookie name in the response to maintain client-server affinity.

      • If the checkbox is cleared, then no standard HTTP set-cookie command is injected into the response. The client-server affinity is either maintained by active header or no affinity is required by your application.

    • Active header   Specifies whether or not the Relay Server is going to inject a proprietary header to maintain client-server affinity.

      • If selected, the Relay Server injects a proprietary header in the response to maintain client-server affinity. This is useful in case where intermediaries tamper with active cookies. Active header works only if the client application supports the Relay Server active header reflection. Web browsers in general does not support Relay Server active header.

      • If the checkbox is cleared, then no proprietary header is injected into the response. The client-server affinity is either maintained by active cookie or no affinity is required by your application. Clear the checkbox to cut down on traffic volume if the backend farm is serving only browser applications, or if the active_cookie is working well for all the clients of this backend farm.

    See Backend farm section.

  • Description   Provides a place for you to type a text description of the backend farm.

 See also
Copyright © 2010, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.0