Adding an application server pool

Create an application server pool to define a collection of one or more IBM Notes Traveler high-availability clusters. Each cluster can contain multiple Traveler servers. Using an application server pool, you can manage your Traveler clusters as a single entity and balance the load across servers. After you add an application server pool, you assign it to an HTTP access service.

Currently, application server pools support Traveler only. You cannot define server pools for iNotes, Sametime, IBM Connections, or other applications.

When the SafeLinx Server receives a request for a new Traveler session, it applies the configured balancing algorithm to determine the server to which a user is assigned. The algorithm is applied across the defined server pools and among the servers within each cluster. Nodes within a pool are treated as equal peers. The SafeLinx Server first selects a pool, and then a node, based on the configured threshold criteria and the number of existing assignments.

To add a server pool, complete the following procedure.

  1. From the SafeLinx Administrator Resources pane, right-click the OU in which you want to add an application server pool, and then click Application server pool.
  2. In the Service URL field, add the URLs of the application servers that you want to include in the pool.
  3. In the Maximum users field, specify the greatest number of users that the SafeLinx can assign to this pool.
    The default value is 10,000.
  4. In the Minimum users field, specify the minimum number of users that SafeLinx must assign to this pool before it assigns users to other pools.
    By default, pools do not enforce a minimum number of users.
  5. In the Pool assignment matching strings field, specify one or more attribute strings to be used in determining the application pool assignments for users. Insert a comma between strings.

    The first time that a new user attempts to access the application server, SafeLinx searches the user's directory record for attribute values that match the strings in this field. If there is a match, the user is assigned to the pool.

    By default, SafeLinx does not check the values in this field. The attribute strings are checked only if you activate a similar setting for the HTTP access service. The values in the Pool assignment matching strings must match values in the Server/pool assignment attribute to query field for the HTTP access service. The strings in each field must be exact matches. Any string is valid, if it is contained in both locations. For more information about enabling SafeLinx to look up LDAP attributes to determine a user’s Traveler server, see Enabling LDAP lookups to determine a user's Traveler server.