Importing configuration data from event processors

After you export configuration data from an event processor (EP) in a cluster on the source IBM® Control Center Monitor instance, import the data into the EPs in a cluster on the target IBM Control Center Monitor instance.

Export the configuration data of one EP from the source IBM Sterling Control Center Monitor instance.
Back up the configuration data of one EP in the target IBM Sterling Control Center Monitor instance, if one exists.
If any EPs exist, ensure in the target IBM Sterling Control Center Monitor instance the EPs can connect to the database.
When you copy the conf directory, the directory structure must be CCInstalledLocation/conf. See Exporting configuration data.
When you are instructed to run configCC, you must complete the configCC steps for the following reasons:
- To clear the existing configuration data in the database of the target IBM Sterling Control Center Monitor instance, so that the EPs there can start.
- To ensure that the configuration data points are imported to new database for the target IBM Sterling Control Center Monitor instance.
- To define new database connections for EP.
- To name the EP in the target IBM Sterling Control Center Monitor instance the same as one of the EPs in the source IBM Sterling Control Center Monitor instance.
- To change other settings if necessary, such as the following settings:
  - Keystore and truststore configuration
  - JDBC driver files
  - Database connection parameters
  - HTTP connector configuration
  - Secure HTTP connector configuration
  - Jetty Web Application Server configuration

Attention: When you run configCC in the following procedure, ensure that your production database is set to the target database that you want to use because the production database is going to be reset to the source database when the exported conf directory is copied from the source to the target system. IBM Control Center Monitor does not support importing configuration data to an existing EP on Microsoft Windows.

To import configuration data from the source instance that has more event processors than the target instance:

Stop all, if any, EPs on the target IBM Control Center Monitor instance.
Complete one of the following choices:
- Import to a new EP on the target IBM Control Center Monitor instance on Microsoft Window. Complete this step by creating a new target installation directory, copy the exported conf folder to the directory, and install IBM Control Center Monitor with the directory.
- Import to a new EP on the target IBM Control Center Monitor instance on UNIX/Linux. Complete this step by running the installer, copy the exported conf folder to the installed directory, and run configCC from the installed directory.
- Import to an existing EP on UNIX/Linux. Complete this step by renaming the existing conf folder in the existing directory, copy the exported conf folder to the existing directory, and run configCC from the existing directory.
Start the EP from step 2 in the cluster on the target IBM Control Center Monitor instance.
For any other existing target EPs, uninstall, delete the old directory, and reinstall in a new directory. This step requires setting the EP name to match one of the imported EP names.
Install more EPs in the cluster as needed on the target IBM Control Center Monitor instance to map to all of the EP names from the target cluster.
Start the remaining EPs in the cluster on the target IBM Control Center Monitor instance.

After the event processor starts, the following configuration objects are loaded into database tables:

Rules
Actions
Calendars
Email lists
File Agent information
Metadata rules, actions, schedules, and type mapping
Metric Types
Monitored servers
Schedules
SLCs and supporting schedules and message lists
Servers
Server messages
Server message categories
Category limits
Tag mapping
Tag labels
Views
UI column layouts
Event processor names

After these objects are loaded into the database, the copy of the data in the file system is moved to a subfolder labeled with the prefix imported-date-time.

In this Microsoft Windows example, the source instance has two event processors, EP1 and EP2, and the target instance has one event processor, EPA. To import configuration data into the target instance, follow these steps:

Uninstall event processor EPA and delete its directory.
Create a directory for a new EP on the target instance.
Copy the configuration data in the conf-exported/YYYYMMDDHHMMSS/conf folder from EP1 and into the directory created in step 2.
Install IBM Control Center Monitor into a new directory. The installer is going to require you to name the EP either EP1 or EP2. In this example, assume that the user selects the name EP1.
Start the new event processor EP1 on the target instance.
Install one more IBM Control Center Monitor instance on a different host. The installer is going to require that you to set the name of the EP to EP2.
Start the new event processor EP2 on the target instance.

In this Microsoft Windows example, the source instance has three event processors, EP1, EP2, and EP3, and the target instance has no EPs. To import configuration data into the target instance, follow these steps

Create a directory for a new EP on the target instance.
Copy the configuration data in the conf-exported/YYYYMMDDHHMMSS/conf folder from EP1 and into the directory created in step 1.
Install IBM Control Center Monitor into the new directory on the target instance and set the name to EP1.
Start the new event processor EP1 on the target instance.
Install two more IBM Control Center Monitor instances on different hosts. The installer is going to require the user to set the names of the EPs to EP2 and EP3.
Start the new event processors EP2 and EP3 on the target instance.

In this UNIX/Linus example, the source instance has one event processor, EP1, and the target instance has three event processors, EPA, EPB, and EPC. To import configuration data into the target instance, follow these steps:

Stop event processors EPA, EPB, and EPC on the target instance.
Rename the existing conf folder in the existing EPA directory.
Copy the configuration data in the conf-exported/YYYYMMDDHHMMSS/conf folder from EP1 and into conf folder for EPA.
Run configCC on EPA to name it EP1.
Start the new event processor EP1 on the target instance.
Uninstall EPB, delete the old directory, and reinstall EPB. Run configCC for event processor EPB. ConfigCC.sh is going to ask the user name the EP anything, for example, EP2.
Uninstall event processor EPC, delete the old directory, and reinstall event processor EPC. Run configCC for event processor EPC. ConfigCC.sh is going to ask the user name the EP anything, for example, EP3.
Start the event processors EP2 and EP3 on the target instance.

In this UNIX/Linux example, the source instance has three event processors, EP1, EP2, and EP3, and the target instance has three event processors, EPA, EPB, and EPC. To import configuration data into the target instance, follow these steps:

Stop event processors EPA, EPB, and EPC on the target instance.
Rename the existing conf folder in the existing EPA directory.
Copy the configuration data in the conf-exported/YYYYMMDDHHMMSS/conf folder from EP1 and into conf folder for EPA.
Run configCC on EPA to name it EP1.
Start the new event processor EP1 on the target instance.
Uninstall EPB, delete the old directory, and reinstall EPB. Run configCC for EPB. ConfigCC is going to require the user to set the EP name to either EP2 or EP3. The user selects EP2.
Uninstall EPC, delete the old directory, and reinstall EPC. Run configCC for EPC. ConfigCC is going to require the user to set the EP name to EP3.
Start the new event processors EP2 and EP3 on the target instance.

In this UNIX/Linux example, the source instance has three event processor, EP1, EP2, and EP3. The target instance has no event processors that are installed. To import configuration data into the target instance, complete the following steps:

Install IBM Control Center Monitor in a new directory on the target instance.
Copy the configuration data in the conf-exported/YYYYMMDDHHMMSS/conf folder from EP1 and into the conf folder of the new directory in step 1.
Run configCC on the EP from step 1 and name it EP1.
Start the new event processor EP1 on the target instance.
Install IBM Control Center Monitor on a new host and run configCC. The installer is going to require the user to set the EP name to either EP2 or EP3. The user selects EP2.
Install one more IBM Control Center Monitor instance on a new host, and run configCC. The installer is going to require the user to set the EP name to EP3.
Start the new event processors EP2 and EP3 on the target instance.

In this UNIX/Linux example, the source instance has three event processors, EP1, EP2, and EP3, and the target instance has one event processor, EPA. To import configuration data into the target instance, follow these steps:

Stop event processor EPA on the target instance.
Rename the existing conf folder in the existing EPA directory.
Copy the configuration data in the conf-exported/YYYYMMDDHHMMSS/conf folder from EP1 and into conf folder for EPA.
Run configCC on EPA and set to name it EP1.
Start the new event processor EP1 on the target instance.
Install IBM Control Center Monitor on a new host and run configCC. ConfigCC is going to require the user to name the EP either EP2 or EP3. In this example, assume that the user selected the name EP2.
Install one more instance of IBM Control Center Monitor on a new host and run configCC. ConfigCC is going to require the user to set the name of the EP to EP3.
Start the new event processors EP2 and EP3 on the target instance.