Installation checklist

There are several considerations and tasks to complete when you install IBM® Sterling Control Center Monitor for the first time. The installation checklist helps you install IBM Sterling Control Center Monitor successfully for either a high availability or non-high availability environment.

Important: If you do not enable the globalization parameter for the Microsoft SQL server during an IBM Sterling Control Center Monitor installation, then you cannot use multi-byte characters. When you use a multi-byte character without enabling this parameter, then IBM Sterling Control Center Monitor cannot run and you must manually remove the character from your database. If you choose to enable the globalization parameter later, you must reinstall IBM Sterling Control Center Monitor.

The following table is a checklist of items to follow when you install IBM Sterling Control Center Monitor for either a high availability or non-high availability environment:

#	IBM Control Center installation checklist	Related links
1	Create your production database for IBM Sterling Control Center Monitor use. In a high availability environment, all event processors must use the same database.	Creating Linux, UNIX, and Windows DB2 database and database user Creating DB2 databases and database users on z/OS Creating an Oracle database and database users (schemas) Creating Microsoft SQL Server database and database user Configuring secure connections
2	Install and configure the IBM Sterling Control Center Monitor event processor. Complete the installation through a GUI installer or command line installer.	Installing and configuring IBM Sterling Control Center Monitor from the command line on UNIX Installing and configuring IBM Sterling Control Center Monitor by using the GUI installer on Microsoft Windows Installing and configuring IBM Sterling Control Center Monitor on z/Linux
3	If you are installing IBM Sterling Control Center Monitor for a high availability environment, install your first event processor. To install your next event processor, your first event processor must be configured and started. Important: If you enable JMS when you configure your event processors, then ensure that all event processors are JMS-enabled and have the same JMS configuration parameters.	Installing IBM Sterling Control Center Monitor in a high availability environment Installing and configuring IBM Sterling Control Center Monitor for high availability with the GUI installer Installing and configuring IBM Sterling Control Center Monitor for high availability from the command line
4	Run the configcc utility to change the IBM Sterling Control Center Monitor settings.
5	If you plan to secure the connections between the IBM Sterling Control Center Monitor event processor and the database, then complete the necessary setup on the database server, IBM Sterling Control Center Monitor engine.	Creating a secure connection between the event processor and the databases Configuring a secure connection to the non-z/OS DB2 database server Configuring a secure connection to the DB2 for z/OS database server Configuring a secure connection to the Microsoft SQL Server 2016 database server Configuring a secure connection to the Oracle database server
6	If you plan to monitor FTP servers, install the FTP agents. Configure your FTP servers to send SNMP traps to the active event processor. If you plan to have a high availability environment, configure the Sterling Connect:Direct® File Agent to send traps to the controller event processor.	Setting up IBM Control Center to monitor Sterling Connect:Direct File Agent
7	Note: Skip this step if you are not using IBM Sterling Control Center Monitor to monitor IBM Sterling Connect:Enterprise® for z/OS® servers. Configure IBM Sterling Connect:Enterprise for z/OS servers to communicate with IBM Sterling Control Center Monitor, and send traps that contain event data to the event processors that are installed. All traps must be sent to the same port. If you plan to have a high availability environment, configure IBM Sterling Connect:Enterprise for z/OS to send traps to all installed event processors.	Configuring Sterling Connect:Enterprise for z/OS
8	Note: Skip this step if you are not using IBM Sterling Control Center Monitor to monitor IBM Global High Availability Mailbox servers. Configure Global Mailbox servers to communicate with IBM Sterling Control Center Monitor.	Configuring IBM Global High Availability Mailbox to publish events to IBM Control Center
9	Install the IBM Sterling Control Center Monitor console.	Setting up a console
10	If the console needs to access the IBM Sterling Control Center Monitor event processor with a secure connection, configure a secure connection between the IBM Sterling Control Center Monitor event processor and the consoles.	Configuring the console for a secure connection
11	If you want to create a secure connection between the IBM Sterling Control Center Monitor event repository and OSA servers, CCM must be configured to support secure HTTP connections..	Creating a secure connection between the event repository and dynamically discovered servers
12	Enable authentication to the event repository. Enabling this authentication means that servers in a high availability environment need to pass IBM Sterling Control Center Monitor authentications to send events to IBM Sterling Control Center Monitor.	Enabling authentication for posting events to the IBM Control Center event repository
13	Start IBM Sterling Control Center Monitor.