Configuring a Web GUI load balancing environment

Edit online

You can setup a load balancing cluster of nodes with identical configurations to evenly distribute user sessions. Load balancing is ideal for environments with a large user population. When a node within a cluster fails, new user sessions are directed to other active nodes. The load balancing functionality is provided in Dashboard Application Services Hub.

Work load is distributed by session, not by request. If a node in the cluster fails, users who are in session with that node must log back in to access the Web GUI. Any unsaved work is not recovered.

For more information about setting up and configuring a load balancing environment, see Load balancing for Dashboard Application Services Hub external link in the Jazz® for Service Management documentation.

For more information about configuring an ObjectServer failover pair to support high availability for Web GUI and Dashboard Application Services Hub see Configuring an ObjectServer failover pair to support load balancing external link in the Tivoli® Netcool®/OMNIbus documentation.

In addition to the load balancing configuration on Dashboard Application Services Hub, you need to make settings in the Web GUI server.init file whenever you add a node to a load balancing cluster, or whenever you remove a node from a cluster. The configuration for the server.init file is described in the following steps.

Procedure

Complete the following steps to start Web GUI load balancing operations on a node.
  1. Open the server.init file in a text editor and locate the properties that begin with the cluster.mode property.
  2. Set the values of the properties as described in the following table.
    Table 1. Setting the load balancing properties
    Property Value
    cluster.mode on
    cluster.db The database to store high availability configuration data, db2 (Db2® default value) or os (ObjectServer).
    cluster.hostname The name or TCP/IP address of the host that is running the new node. For example, server1.
    cluster.port The number of the SSL port that the Web GUI server uses. For example 16311.
  3. Set the timedtasks.enabled value to true.
  4. Configure the schedules for timed tasks as required.
    Define the same set of timed tasks with identical schedules on all nodes in the cluster.
  5. Restart the server.
The node is joined to the cluster and reads it configuration data from the database.