Getting started with IBM Sterling Control Center Monitor in a high availability environment

The getting started with IBM® Sterling Control Center Monitor in a high availability environment workflow outlines high-level steps to set up a high availability environment for IBM Sterling Control Center Monitor. This workflow describes how to plan, configure, and administer a high availability environment.

There are several considerations when you enable a high availability environment for IBM Sterling Control Center Monitor. The following sections help you identify the steps that you need to complete successfully to enable a high availability environment.

Planning for a high availability environment

Determine which operating system you want to install and configure your IBM Sterling Control Center Monitor event processors (EPs) on. You can install and configure IBM Sterling Control Center Monitor for a high availability environment on Microsoft Windows, Linux, AIX, and UNIX platforms.
Determine how many instances of IBM Sterling Control Center Monitor you want installed. You must install more than one instance of IBM Sterling Control Center Monitor to have a high availability environment.
Determine if you want one of your instances of IBM Sterling Control Center Monitor without the Jetty Web Application.
Determine if you want your Jetty Web Application servers to be configured to prevent an automatic shutdown when an event processor is stopped. Preventing an automatic shutdown of the server ensures that users can still access their data.
Determine your CPU allocation for each event processor (EP). If you are running at 80 percent or more CPU capacity with IBM Control Center Monitor V6.0, then in V6.2 you need to add more CPU. Adding more CPUs is necessary to properly scale an IBM Control Center Monitor environment with multiple EPs. For more information, see Detailed System Requirements.
Determine your planned heap memory allocation. The max heap default allocation for an EP is 4 GB and web console is 2 GB, but to increase performance in a high availability environment, the allocation can be set to 8 GB for an EP and 4 GB for the web console.

Installing and configuring for a high availability environment

After you plan for a high availability environment, you must set up and configure the environment. The following list contains tasks to complete when you are configuring a high availability environment:

Install and configure your IBM Sterling Control Center Monitor EPs for a high availability environment.
Important: When you configure your EPs, ensure that all EPs have the same configuration for enabling events to the JMS queue.
- For more information, see Installing IBM Control Center in a high availability environment, Installing and configuring IBM Control Center for high availability from the command line, and Installing and configuring IBM Control Center for high availability with the GUI installer.
Configure any secure connections you need for IBM Sterling Control Center Monitor in a high availability environment.
- For more information, see Configuring secure connections.
Configure your Sterling Connect:Enterprise® for z/OS® and WS_FTP servers to send traps to the assigned EP. Any Sterling Connect:Direct® File Agent must be configured to send traps to all EPs, not just one, So, the EP, which becomes the controller EP can process the traps and none will be missed. Another option is to set up a trap forwarder. You would configure the servers that send traps to go to the trap forwarder, and configure the trap forwarder to send all the received traps to all the EPs..

Administering a high availability environment

After you plan, install, and configure your IBM Sterling Control Center Monitor environment for high availability, you can complete the following administrative tasks to maintain a high availability environment. You must have the System Settings - Manage permission to access the EPs in your IBM Sterling Control Center Monitor environment.

Verify that all of your EPs are running in your environment. Ensure that one of your EPs is marked as the controller event processor.
- For more information, see Viewing the servers assigned to an event processor.
Manually assign servers to another event processor. By default the controller EP assigned newly added servers to an EP with the least number of assigned servers.
- For more information, see Manually assigning monitored servers to an event processor .
Select failover, load balancing, and monitoring policies for your event processors.
- For more information, see Setting a server assignment, failover, and monitoring policy for an event processor.
Rebalance your servers for a more even distribution among your EPs.
Important: By default, if you have Sterling Connect:Enterprise for z/OS, FTP z/OS, or WS_FTP server types, then those server types are pinned and not included in a rebalance. If you want to unpin these server types and include them in the rebalance, then go to the advanced properties for each server. However, the system administrator of those servers must reconfigure the SNMP host to send traps to the new EP.
- For more information, see Rebalancing servers across event processors.
Ensure that the system times for your event processors are synchronized. If the clocks are not synchronized, then the events from your EPs can display out of order in a report, for example.