Copying configuration objects between UNIX installations

You can copy configuration objects from one IBM® Sterling Control Center Monitor installation on UNIX to another installation.

1. Stop the engine from where you are planning to copy the IBM Sterling Control Center Monitor configuration objects.
2. Archive the entire conf folder in the latest SCCInstallDirectory/conf-exported/YYYYMMDDHHMMSS/ folder.
   For example, you can use the following command:

   tar -cvf conf.tar conf

3. Transfer the archived file to the target installation host.
4. Optional: Restart the engine.
5. Stop the IBM Sterling Control Center Monitor engine that is running on the target installation.
6. Make a backup of the conf folder on the target installation.
7. Rename or delete the existing conf folder on the target installation.
   For example, you can use the following command:

   mv conf conf_old

   CAUTION:

   Do not attempt to merge the source configuration data with any existing target configuration data.
8. From the target IBM Sterling Control Center Monitor engine installation location, extract the archive file that was transferred from the source installation.
   For example, you can use the following command:

   tar -xvf conf.tar

   After the extraction, the conf folder is in the SCCInstallDirectory folder.
9. Run configCC.sh to change the database connection details.
   If you do not change the database connection details, the database connection that is used by the target installation is the same connection as the source installation. When you run configCC, you receive a message that all steps are already configured, but you might need to specify different values in the following steps:
   1. Optional: Engine Name configuration step - Specify a different engine name.
   2. Optional: Time Zone configuration step - Specify a different time zone value.
      If the source installation and target installation were not in the same time zone, you must specify a different time zone value.
   3. Required: JDBC Driver configuration step - Select the appropriate database type and specify the JDBC Driver for that database type.
   4. Required: Production Database connection parameters configuration step - Specify different connection details.
      If you do not specify different database connection details, then two different engines might use the same database.
   5. Required: Production Database initialization step - Answer No to keep existing data in the database.
      Warning: If you answer Yes, then all existing data in the database becomes lost.
   6. Optional: Keystore/Truststore configuration step - Specify a valid keystore and truststore.
      If you previously specified a valid keystore and truststore, then you must specify them again.
   7. Required: HTTP Connector Configuration - Reconfigure the appropriate port number.
   8. Optional: Secure HTTP Connector Configuration - Configure the appropriate port number.
      If you need a secure connection between the engine and console, the you must reconfigure
   9. Required: Servlet Container Configuration step - Reconfigure the appropriate port number and host name.
10. Take one of the following actions to start the engine:
    • To collect the statistics that were generated when the engine was down, use runEngine.sh.
    • To start collecting statistics now, use runEngineCold.sh.
11. In the IBM Sterling Control Center Monitor console, click Menu button () > System Settings > Email Server and update the following system settings as needed:
    • Email server connection on the Email Server screen.
    • Host computers where SNMP traps are sent on the SNMP Hosts tab.
    • Simultaneous pollers on the Services tab.
    • Settings effecting the monitor performance on the Console tab.
    • Settings that are related to moving data from the Production to the Staging databases on the Database tab.