Control-M SaaS Full Migration

A Contol-M SaaS full migration copies the data from one self-hosted Control-M/EM to one SaaS Control-M/EM, and all self-hosted Control-M/Servers to SaaS Control-M/Servers.

This migration eliminates the need to maintain these self-hosted components and their associated databases.

The following diagram shows the logical architecture of a typical full migration:

Migrating to Control-M SaaSLink copied to clipboard

This procedure describes how to migrate your self-hosted Control-M/EM and Control-M/Server data to Control-M SaaS, based on your organizational needs and the results of the qualification scan.

Before You Begin

• Verify that you are qualified to migrate to Control-M SaaS, as described in Scanning Control-M Self-Hosted.

Before You Begin

1. Verify that you are qualified to migrate to Control-M SaaS, as described in Scanning Control-M Self-Hosted.

   The scan produces qualification reports that enable you to determine the steps that you must take before you can migrate to Control-M SaaS.

2. Register for Control-M SaaS, as described in Registering for Control-M SaaS.

   This enables BMC to provide you a SaaS Control-M/EM with SaaS Control-M/Servers that match the time zones and Control-M/Server names in your current self-hosted environment.

3. Migrate your self-hosted Control-M/EM and Control-M/Server data to Control-M SaaS, as described in Migrating to Control-M SaaS.

   Migrates Self-Hosted Control-M to Control-M SaaS, applies necessary adjustments, and generates an Excel-based migration report that identifies any remaining incompatibility issues and the actions you must take to resolve or work around them.

Scanning Control-M Self-HostedLink copied to clipboard

This procedure describes how to scan a self-hosted Control-M/EM and Control-M/Server, which generates an Excel-based Qualification Report that identifies incompatibilities and describes the steps you must take to migrate to Control-M SaaS. You must perform this procedure for every Control-M/Server connected to Control-M Self-Hosted.

You can run this tool from any Windows or Linux computer.

Before You Begin

• Verify that Control-M Automation API 9.0.20.245 or higher is installed on the self-hosted Control-M/EM server.

• Verify that you have access to the self-hosted Control-M/EM server database.

Begin

1. Download the Helix Control-M/Server Data Migration tool, based on your operating system, from Control-M SaaS Migration Tool, and unzip it to a temporary folder.

2. (Optional) Migrate your variable lists to pool variables, as described in Creating a LIBMEMSYM Control File.

3. From the inputParameters folder inside the unzipped migrateToHelix temporary folder, open the parameters.txt file in a text editor, and then define the required parameters, as described in Migration Tool Parameters.

4. Do one of the following:

   • Qualification Mode: To scan your components and export up to 5,000 folders (default) to a *.json file, do the following:

     1. (Optional) To change the default 5,000-folder export limit, from the path/data/ directory in the unzipped migrateToHelix folder, open the configuration.json file in a text editor and redefine the foldersCountLimit parameter value, as shown in the following example:

        CopyCopied to clipboard

        "foldersCountLimit": 10000

     2. From the command line, navigate to the unzipped migrateToHelix folder and run the following command:

        migrateToHelix.bat qualification

   • Export Mode: To scan your components and export all folders to a *.json file, do the following:

     1. Install the most recent version of Control-M Automation API on Control-M/EM server, as described in Setting Up the API.

     2. From the command line, navigate to the unzipped migrateToHelix folder and run the following command:

        migrateToHelix.bat extract

        Scan and export time depends on the size of your components.

   The scan runs and produces an Excel-based Qualification Report.xlsx file in the report folder, which includes one or more of the following results in the Qualification Summary sheet:

   • Passed

   • An automatic adjustment was made.

   • Manual action is required.

   • An incompatibility was found.

5. From the report folder, open, review, and follow the directions in the Qualification Report.

   Depending on the report results, you might have to scan your components more than once.

Registering for Control-M SaaSLink copied to clipboard

This procedure describes how to register for Control-M SaaS, which enables BMC to provide you a with a SaaS Control-M/EM and SaaS Control-M/Servers that match the time zones and Control-M/Server names in your current self-hosted environment. You must perform this procedure only once.

Begin

1. Run the Helix Control-M/Server Data Migration tool in Qualification Mode, as described in Scanning Control-M Self-Hosted.

2. Open the migration metadata file from the following location:

   • UNIX: <migrateToHelix>/output/migration_metadata.xlsx

   • Windows: "<migrateToHelix>\output\migration_metadata.xlsx"

3. From the Control-M/Server column, delete all Control-M/Servers that must remain self-hosted and do not migrate to SaaS Control-M/Servers.

4. From the Time Zone drop-down list next to each Control-M/Server, select your Control-M/Server time zone.

5. Save the file and upload it in the Helix Control-M Migration - Technical Migration Details section of the SaaS Subscription Registration form.

6. Complete and submit the SaaS Subscription Registration form.

   A confirmation email with a link to your new Control-M SaaS tenant arrives after it is ready. If you do not receive this email, you must contact your customer service representative.

Migrating to Control-M SaaSLink copied to clipboard

This procedure describes how to migrate your self-hosted Control-M/EM and one Control-M/Server to Control-M SaaS. You must perform this procedure for every self-hosted Control-M/Server that is connected to the self-hosted Control-M/EM.

You can run this tool from any Windows or Linux computer.

Before You Begin

• Verify that the most recent version of Control-M Automation API is installed on Control-M/EM server. For more information, see Setting Up the API.

• Verify that you have access to the Control-M/EM database.

Begin

1. Download the Helix Control-M/Server Data Migration tool, based on your operating system, from Control-M SaaS Migration Tool, and unzip it to a temporary folder.

2. (Optional) Migrate your variable lists to pool variables, as described in Creating a LIBMEMSYM Control File.

3. From the inputParameters folder, inside the unzipped migrateToHelix folder, open the parameters.txt file in a text editor, define the parameters for the required parameters, as described in Migration Tool Parameters. If necessary, redefine the parameters that you defined when you last ran the tool.

4. Do the following:

   1. From the command line, navigate to the unzipped migration tool folder.

   2. Do one of the following: 

      • To rescan and migrate your defined self-hosted components to Control-M SaaS, run the following command:

        migrateToHelix.bat migrate

        The tool rescans your components, migrates your self-hosted Control-M/EM and the defined Control-M/Server to Control-M SaaS, and produces an Excel-based Migration Report.xlsx file in the report folder.

      • To immediately migrate your defined self-hosted components to Control-M SaaS, run the following command:

        migrateToHelix.bat deployOnly

        The tool migrates your self-hosted Control-M/EM and the defined Control-M/Server to Control-M SaaS, and produces an Excel-based DeployOnlyReport.xlsx file in the report folder.

5. From the report folder, open, review, and follow the directions in the Migration or Deploy Only Report.

   Your self-hosted Control-M/EM and one self-hosted Control-M/Server has been migrated to your Control-M SaaS.

6. (Optional) Migrate Control-M MFT local connection profiles and Application-Integrator-created plug-in connection profiles to SaaS-supported centralized connection profiles, as described in Migrating Local to Centralized Connection Profiles.

7. Get started with Control-M SaaS, as described in Getting Started.

Migrating Local to Centralized Connection ProfilesLink copied to clipboard

This procedure describes how to migrate Control-M MFT local connection profiles and Application-Integrator-created plug-in connection profiles to centralized connection profiles in Control-M SaaS. You must perform this procedure on every Agent that contains Control-M MFT and Application-Integrator-plug-in-created local connection profiles that you want to migrate.

Before You Begin

• Verify that Control-M/Agent 9.0.21 or higher is installed.

• Verify that Control-M SaaS Agent 9.0.21.200 or higher is installed.

Begin

1. Download the Helix Control-M LCP-to-CCP Migration Tool, based on your operating system, from Control-M SaaS Migration Tool, and unzip it to a temporary folder.

2. From the Agent host, navigate to the temporary folder where you unzipped the LCP-to-CCP migration tool, and run the following command to export your local connection profiles:

   lcpToCcp -export [-pluginType <MFT, AI, or ALL>] [-agentDir <Windows_Agent_Directory_Pathname>]

   For more information, see Connection Profile Migration Parameters.

   The directory path and filename of the zipped, exported local connection files appears.

3. Copy the zip file to the SaaS Agent.

4. From the SaaS Agent, run the following command to migrate the zipped local connection profiles to centralized connection profiles:

   lcpToCcp -import -path <ZIP_Pathname_and_Filename> -url <Automation_API_URL> -token <API_Token> -ctm <Control-M/Server> -agent <Agent> [-cpnp <OVERWRITE, SKIP, or ASK>] [-d <TRUE or FALSE>] [-agentdir <Agent_Directory_Pathname>]

   For more information, see Connection Profile Migration Parameters.

   The local connection profiles from the Agent are migrated to centralized connection profiles in Control-M SaaS.

Migration Tool ParametersLink copied to clipboard

The following table describes the parameters that you must define when Scanning Control-M Self-Hosted and Migrating to Control-M SaaS, depending on the mode.

Connection Profile Migration ParametersLink copied to clipboard

The following table describes the parameters that you must define when you migrate your Control-M MFT and Application Integrator local connection profiles to centralized connection profiles in Control-M SaaS.

Creating a LIBMEMSYM Control FileLink copied to clipboard

This procedure describes how to create a LIBMEMSYM control file, which the migration tool uses to transfer your %%LIBMEMSYM variable lists to Pool variables. For more information, see List Variables.

Begin

1. Find all unique LIBMEMSYM files that each %%LIBMEMSYM variable points to, and copy these files from the self-hosted Control-M/Server to a temporary folder on your host.

2. Open a text editor and for each unique %%LIBMEMSYM list variable, type the following entries, separated by commas, on a new line:

   • Pathname of the copied LIBMEMSYM file that you copied from the self-hosted Control-M/Server, on your host.

   • Pathname of the LIBMEMSYM file on the self-hosted Control-M/Server.

   • Pool Name that each variable in the %%LIBMEMSYM list variable is migrated into.

     c:\temp\libMem1.txt,C:\Program Files\BMC Software\Control-M Server\ctm_server\libMem1,PoolName1

     c:\temp\libMem2.txt,C:\Program Files\BMC Software\Control-M Server\ctm_server\libMem2,PoolName2

     c:\temp\libMem3.txt,C:\Program Files\BMC Software\Control-M Server\ctm_server\libMem3,PoolName3

3. Save the LIBMEMSYM_Control_File.csv file and type the pathname after the = (equals sign) in the %%LIBMEMSYM list variable Parameter, as described in Migration Tool Parameters.

Migration TroubleshootingLink copied to clipboard

The following table describes migration problems that might occur and corrective actions you can take to troubleshoot the migration process.

[
  {{{}}
    "name": "ctmcore",
    "host": "ctmcore",
    "state": "Up",
    "message": "",
    "version": "9.0.20.200"
  }
]