Control-M for VMware Plug-in Migration Tool

The Control-M for VMware Plug-in Migration Tool converts the Control-M for VMware plug-in to the Control-M for VMware by Broadcom Application Integrator-based plug-in.

Migrating Control-M for VMware to Control-M for VMware by Broadcom

This procedure describes how to migrate the Control-M for VMware plug-in to the Control-M for VMware by Broadcom plug-in.

Before You Begin

• Install Control-M for VMware by Broadcom and create a connection profile.

• Verify that Automation API is installed, as described in Automation API Installation.

Begin

1. Download the Control-M Migration Tool for Integrations from EPD.

2. Extract the downloaded files into a temporary directory.

3. From a command line, run the following command to export the workspace with Control-M for VMware jobs to a JSON file:

   ctm deploy jobs::get -s "server=<server name>&folder=<VMware_folder>" >input.json

4. Edit the configuration file downloaded with the migration tool from the EPD with the following steps:

   • Navigate to the Control-M Migration Tool for Integrations directory that you downloaded.

   • Open the migration_configuration_file.json in a text editor.

   • Add the job type, connection profiles, and hosts that you want to convert. See Configuration File Parameters.

5. Do one of the following to run the migration tool:

   • Windows: Run the following command:

     plugins_migration_tool.exe -i <Exported_Workspace_Pathname> -c <Migration_Configuration_File_Pathname> -o <Output_File_Pathname>

     For more information, see Control-M Migration Tool Parameters.

   • UNIX: Do the following:

     1. Run the following command to ensure that you are authorized to run the migration tool:

        chmod +x plugins_migration_tool

     2. Run the following command:

        ./plugins_migration_tool -i <Exported_Workspace_Pathname> -c <Migration_Configuration_File_Pathname> -o <Output_File_Pathname>

        For more information, see Control-M Migration Tool Parameters.

6. Import the output file with the updated job definitions, as described in Importing a Workspace.

Configuration File Parameters

The Control-M Migration Tool contains the migration_configuration_file.json file that instructs the tool how to handle the different job types in the exported JSON file.

You must edit the configuration file with the job type, connection profiles, and hosts that you want to convert. The Control-M Migration Tool only converts the job types, connection profiles, and hosts that you define in the configuration file.

The tool does not convert the following Control-M for VMware parameters to Control-M for VMware by Broadcom parameters:

• Configuration Tasks action parameters:

  • Clone

  • Migrate

  • Deploy

• Snapshot Tasks action parameters:

  • Revert to Snapshot

  • Remove Snapshot

  • Remove All Snapshots

The following example shows a configuration file to migrate the original Control-M for VMware to Control-M for VMware by Broadcom:

[
{
"Type": "Job:VMware",
"ConnectionProfile": "{VMware1:VMwareByBroadcom1},{VMware2:VMwareByBroadcom2}",
"Host": "{VMware_Agent1:VMwareByBroadcom_Agent1},{VMware_Agent2:VMwareByBroadcom_Agent2}"
}
]

The following table describes the migration_configuration_file.json file parameters.

Control-M Migration Tool Parameters

The following table describes the migration tool parameters.