Load balancer configuration for IBM Sterling Control Center Monitor

To maximize high availability in your IBM® Sterling Control Center Monitor environment, you can configure a load balancer for web console sessions across instances of the Jetty Web Application Server.

Load balancer configuration for the Jetty Web Application Server

You can configure a load balancer to evenly distribute IBM Sterling Control Center Monitor web console sessions across multiple instances of the Jetty Web Application Server. To configure the load balancer across multiple instances of the Jetty Web Application Server, follow these high-level steps:
  • Specify the load balancing policy as round robin.
  • Enable session affinity based on JSESSIONID cookies for requests to /sccwebclient/* URLs.
  • Disable session affinity for requests to /sccwebclient/events URLs.
    Tip: You do not have to create a session affinity policy that is different than the session affinity policy for the web console. The requests to the event repository do not include JSESSIONID cookies.
  • Set the session affinity timeout value greater than or equal to the web console timeout value. See Setting console preferences.

With this configuration, any IBM Sterling Control Center Monitor web console session request is routed by a load balancer to a corresponding instance of the Jetty Web Application Server based on a round robin policy. The load balancer applies the session affinity principle to ensure that the same session requests are always routed to the same instance of the Jetty Web Application Server. When an instance of the Jetty Web Application Server goes down, new web console sessions are transparently routed by the load balancer to any remaining instances of the Jetty Web Application Server. If an instance of the Jetty Web Application Server goes down mid-session, then the user is prompted to log in to the IBM Sterling Control Center Monitor web console. Then, a new web console session begins.

This load balancer configuration also affects Jetty Web Application Server RESTful API clients, such as the event repository. The load balancer can evenly distribute events that are posted to the IBM Sterling Control Center Monitor event repository in a high availability environment. However, session affinity is not applied, so multiple events from the same instance can be balanced across multiple event repositories for improved performance.