This procedure describes how to install a secondary Control-M full, Control-M/EM, or Control-M/Server for high availability on Windows. A secondary installation uses the same installation parameters, database and schema, as the primary installation.
Before You Begin
Ensure that you have met the following requirements:
Verify that the target computer is clean and does not have any previous Control-M version installed.
To install a secondary on Windows:
Log in to the computer using a user ID that has Administrator permissions.
Do one of the following:
From the installation DVD, double-click the Setup.exe file.
From a command prompt window, enter <source_path>\Setup.exe.
Do one of the following:
Interactive install: Select the Additional Installations > Secondary installation for High Availability option and continue with the on-screen instructions until the installation is complete.
Automatic install: Create a parameter file and then run the automatic install in a non-interactive mode, as follows:
Select the Additional Installations > Secondary installation for High Availability option and continue with the on-screen instructions until the Summary window.
Click Generate and select the location to create the XML parameter file.
Click Yes to quit the installation.
A confirmation message appears.
Click Yes.
The automatic installation XML parameters file that is created (<filename>.xml) is relevant only for computers with the same agent instance name. Otherwise, a separate <filename>.xml file must be created for each computer, or modified manually for each computer.
Copy the automatic installation parameters file to a network location that is accessible to all computers where you want to perform an automatic installation.
Log in using a user ID that has Administrator permissions on the current computer.
Ensure that the installation DVD is still in the DVD drive, and run the installation script, as follows:
If you are using Oracle or MSSQL, the high availability environment is now activated. If you are using PostgreSQL, verify that all requirements have been met, as described in High availability requirements, and then start the replication process, as described in Starting database replication.