Control-M for AWS Plug-in Migration Tool

The Control-M for AWS Plug-in Migration Tool converts the Control-M for AWS plug-in to the following Application Integrator-based plug-ins:

• Control-M for AWS Batch

• Control-M for AWS Lambda

• Control-M for AWS Step Functions

Migrating Control-M for AWS to Control-M for AWS Batch, Control-M for AWS Lambda, or Control-M for AWS Step FunctionsLink copied to clipboard

This procedure describes how to migrate the Control-M for AWS plug-in to Control-M for AWS Batch, Control-M for AWS Lambda, or Control-M for AWS Step Functions plug-ins.

Before You Begin

Install the required plug-ins and create their connection profiles, as described in the following topics:

• Control-M for AWS Batch

• Control-M for AWS Lambda

• Control-M for AWS Step Functions

Begin

1. In Control-M SaaS, from the Configuration domain, click the orange drop-down arrow button and select Plug-ins.

2. Click Install Plug-in.

3. Select AWS.

4. In the textual instructions on the right, click Download the Control-M for AWS Plug-in Migration Tool.

5. Export the Workspace with Control-M for AWS jobs to a JSON file, as described in Exporting a Workspace.

6. Edit the configuration file with the following steps:

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

   2. Open the migration_configuration_file.json in a text editor.

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

7. 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.

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

Configuration File ParametersLink copied to clipboard

Control-M Migration Tool for Integrations contains the migration_configuration_file.json file that instructs the Control-M Migration 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, hosts, and state machines that you want to convert. The Control-M Migration Tool only converts the job types, connection profiles, hosts, or state machines that you define in the configuration file.

The following example shows a configuration file to migrate the original Control-M for AWS to Control-M for AWS Batch, Control-M for AWS for Lambda, and Control-M for AWS for Step Functions:

[
    {
        "Type": "Job:AWS:Batch",
        "ConnectionProfile": "{AWS1:AWS_BATCH1},{AWS2:AWS_BATCH2},{AWS3:AWS_BATCH3}",
        "Host": "{AWS_Agent1:Batch_Agent1},{AWS_Agent2:Batch_Agent2}"
    },
    {
        "Type": "Job:AWS:Lambda",
        "ConnectionProfile": "{*:AWS_LAMBDA}",
        "Host": "{AWS_Agent1:Lambda_Agent1}"
    },
    {
        "Type": "Job:AWS:StepFunctions",
        "ConnectionProfile": "{*:AWS_StepFunctions}",
        "Host": "{*:StepFunctions_Agent}",
        "State Machine ARN": "{AWS_StateMachine:StepFunctions_State_Machine_ARN}"
    }
]

The following table describes the migration_configuration_file.json file parameters.

Control-M Migration Tool ParametersLink copied to clipboard

The following table describes the migration tool parameters.