When you install more than one event processor (EP), and Jetty Web Application server, you can implement IBM® Control Center Monitor in a high availability environment.
To understand what an IBM Control Center Monitor high availability implementation can look like, it is best to first consider a non-high availability implementation as shown in the following diagram:
In a non-high availability environment with IBM Control Center Monitor, your components include the web console, production database, one EP, one Jetty Web Application server, and your selected monitored servers.
The following diagram shows IBM Control Center Monitor deployed in a high availability environment:
In a high availability environment with IBM Control Center Monitor, your components include the web console, production database, load balancers, multiple EPs, multiple instances of Jetty Web Application server, an event repository, and your selected monitored servers.
High availability with event processors
In a high availability environment, the servers that are monitored by a failed EP can be temporarily reassigned to other EPs in the cluster. If multiple EPs are installed, the controller EP periodically checks to see whether any EPs in the cluster are down. If the controller EP detects that an EP is down, the controller EP temporarily distributes the servers that the EP monitors to other EPs.
High availability with controller event processors
All EPs in a cluster periodically check whether the controller EP is active. The first EP that notices that the controller EP is down takes over as the controller EP. When the controller EP is back online, it joins the cluster as a normal EP.
High availability with the console
When a console connects to an EP in the cluster, you can view all servers that are monitored by all EPs in the cluster and their property information. With the console, you can also perform the following actions for the servers that are monitored by any EPs in the cluster:
- Pausing or resuming monitoring
- Refreshing the adapter list for a Sterling B2B Integrator server
- Refreshing the BP list for a Sterling B2B Integrator server
- Retrieving the license key for a Sterling B2B Integrator server
- Resetting the Max Concurrent Process Count
- Testing connection
- Turning on or turning off the debug level logging
The consoles also supports failover. When a console connects to an EP in the cluster and the EP goes down, the console automatically connects to another active EP in the cluster.
High availability with Jetty Web Application Server
Multiple web consoles and event repositories (ERs) can be hosted on multiple Jetty Web Application server. You can configure a load balancer to evenly distribute web console sessions and ER workloads across any Jetty Web Application server that is installed, and to provide failover of web consoles and ERs. In a high availability environment, you can configure a Jetty Web Application server to not automatically shut down when an EP is stopped.
High availability with databases
IBM Control Center Monitor supports native database high availability solutions such as the database high availability solution provided by Oracle Real Application Clusters (RAC).