Installing Control-M Workload Archiving on Windows

This procedure describes how to install Control-M Workload Archiving on Windows.

Before you begin

• Verify that the Control-M/EM database server is up and running.
• Install Control-M/Enterprise Manager 8.0.00.800 on both Control-M/EM server and the Workload Archiving server.

NOTE: If you are using an Oracle database, you do not need to install the fix pack.

• Download the Control-M Workload Archiving installation files (see Product Distribution in the Control-M Workload Archiving Release Notes).

To install Control-M Workload Archiving on Windows:

1. From the Control-M Workload Archiving activation CD, double-click the setup.exe file.

   The Control-M Workload Archiving 8.0.00 Installation wizard appears.

2. Do one of the following:
   • Interactive install: Follow the on-screen instructions until the installation is complete.
   • Automatic install: Do the following:
     1. Follow the on-screen instructions until the Summary window.
     2. Click Generate and select the location to create the XML parameter file.
     3. Click Yes to quit the installation.

        A confirmation message appears.

     4. Click Yes.
     5. Copy the automatic installation parameters file to a network location that is accessible to all computers where you want to perform an automatic installation.
     6. Log in using a user ID that has Administrator permissions on the current computer.
     7. Ensure that the installation DVD is still in the DVD drive, and run the installation script, as follows:

        <source_path>\Setup.exe -silent <filename.xml>

        The installation log can be found at the following location:

        <installFolder>\BMCINSTALL\log\BMC_Control-M_Workload_Archiving_Install_<date-time>.log

3. Click Done.
4. Start up the Workload Archiving Server, as described in Starting up the Workload Archiving Server.

   NOTE: If you cannot connect to Control-M Workload Archiving from the CCM, see 000087384.

5. If you are installing in a cluster environment, you need to run the following script on the secondary host:

   <install_path>\Control-M Workload Archiving\data\create_service.cmd