Copying configuration objects between installations

You can copy all IBM® Sterling Control Center Monitor configuration objects from a source IBM Sterling Control Center Monitor installation to a target IBM Sterling Control Center Monitor installation. After these steps are performed, any existing configuration objects at the target installation are not used by the IBM Sterling Control Center Monitor engine because you either delete or rename the old \conf folder on the target installation.

You may want to perform this copy procedure for a variety of reasons including:

  • To prepare for disaster recovery
  • To copy a test instance of IBM Sterling Control Center Monitor to a production instance.

The source installation and target installation must be the same version level, including the minor version. For example, if the source IBM Sterling Control Center Monitor installation is 5.4.1, then the target installation must be 5.4.1.

You must copy the entire configuration objects directory as a whole. Do not copy configuration objects selectively. You must not attempt to merge the source configuration data with any existing target configuration data. The source configuration is a complete replacement of all the target configuration's objects.

The following IBM Sterling Control Center Monitor configuration objects are stored in the installation directory\IBM\ControlCenter\conf directory, where installation directory is the directory where you installed IBM Sterling Control Center Monitor:

  • Definitions and checkpoint files for all managed servers
  • Rules and Actions
  • Rule Schedules, SLC Schedules and Automated Report Schedules
  • Calendars
  • Email Lists
  • Metadata Rules and Actions
  • Report definitions
  • Automated Report Definitions
  • Users, Roles, and User Profiles
  • Server Groups
  • Templates for Batch creation utility
  • Password Policy file
  • Welcome Message file
  • Various engine connector service definitions
  • Various System Service files such as JDBC Service

The configuration objects include the JDBC Configuration (Database connection) details. After you copy the configuration objects to another installation, you must run configCC.bat (for Microsoft Microsoft Windows) or configCC.sh (for UNIX) to change the database connection details so the target installation uses the appropriate database.

The checkpoint files for managed servers are also included in the configuration objects. Therefore, when the configuration objects are copied to another installation, the target engine will use those checkpoint files and start collecting the statistics onwards from the date and time found in those files. If you do not want this to be the case, use runEngineCold.bat (for Microsoft Windows) or runEngineCold.sh (for UNIX).