Helix Control-M Unified View Migration

The Helix Control-M Unified View Migration process enables you to migrate your self-hosted Control-M/EM data and connect your self-hosted Control-M/Servers, Control-M for z/OS environments, and Agents to Helix. This eliminates the need to maintain Control-M/EM and its database, and allows you to access your self-hosted components from Helix.

The migration process consists of the following steps:

1. Migration: Migrates your self-hosted Control-M/EM to Helix Control-M. For more information, see Migrating to Helix Control-M.

2. Token Generation: Generates a token that enables you to add a self-hosted Control-M/Server or Control-M for z/OS to Helix Control-M, as described in Generating a Server Token.

3. Registration: Connects a self-hosted Control-M/Server or Control-M for z/OS to Helix Control-M, as described in the following procedures:

   • Control-M/Server: Connecting a Self-Hosted Control-M/Server to Helix Control-M Unified View

   • Control-M for z/OS: Connecting a Self-Hosted Control-M for z/OS to Helix Control-M Unified View

4. Resume Production: Resumes all connected, self-hosted Control-M/Servers and Control-M for z/OS environments, as described in Resuming All Connected Self-Hosted Control-M/Servers and Control-M for z/OS Environments.

Migrating to Helix Control-M

This procedure describes how to migrate your self-hosted Control-M/EM to Helix Control-M. The migration exports your Control-M/EM data to an export file, uploads it to an Amazon S3 bucket, transfers the file, uncompresses it, and then integrates it into your new Helix Control-M tenant. If your Control-M/EM is not connected to the internet, you can transfer the export file to any internet-accessible Windows or Linux host and then continue the migration.

Before You Begin

• Verify that you are qualified to migrate your self-hosted Control-M/EM to Helix Control-M, as described in Helix Control-M Qualification.

• Verify that Control-M/EM 9.0.21.300 or higher is installed on your self-hosted Control-M/EM.

Begin

1. Log in to Helix Control-M with a user that is associated with an Admin role, and generate and record the value of an API token, as described in Creating an API Token.

2. Download the Helix Control-M/EM Migration Tool to your self-hosted Control-M/EM from Helix Control-M/EM Migration Tool, and unzip it to a temporary folder.

3. From the command line, navigate to the export directory in the unzipped migration folder, and then run one of the following commands to export your Control-M/EM data to a compressed archive (*.tar.gz) file:

   • Windows: run_saas_migration_export.bat

   • Linux: run_saas_migration_export.sh

   The export tool runs, produces a compressed archive export file named EMExportForSaaS.tar.gz, which contains your self-hosted Control-M/EM data, and saves it to the temporary folder.

4. Do one of the following:

   • Import the Control-M/EM Data from the Control-M/EM Host

   • Import the Control-M/EM Data from a Separate Host

Importing the Control-M/EM Data from the Control-M/EM Host

This procedure describes how to import and integrate your exported Control-M/EM data into your new Helix Control-M tenant from the Control-M/EM host.

Begin

1. If you use a proxy server, define the following environment system variable:

   • Name: https_proxy

   • Value: http://<Proxy_Server_Address>:<Proxy_Server_Port>

2. Verify that you have outgoing internet access to the following locations:

   • *.controlm.com:443

   • *.amazonaws.com:443

3. From the import directory in the unzipped migration tool folder, run the following command to import your Control-M/EM data to Helix Control-M:

   • Windows: em ./run_saas_migration_import.bat

   • Linux: em ./run_saas_migration_import.sh

4. At the prompts, type the requested information, as described in Import Parameters.

   The import tool runs and a number of status messages appear that describe the steps of the import process.

Importing the Control-M/EM Data from a Separate Host

This procedure describes how to import and integrate your exported Control-M/EM data into your new Helix Control-M tenant from a separate internet-accessible Windows or Linux host.

Begin

1. Download the Helix Control-M/EM Migration Tool from Helix Control-M/EM Migration Tool, and unzip it to a temporary folder.

2. Transfer the EMExportForSaaS.tar.gz from the Control-M/EM host to another temporary folder.

3. Verify that Python 3.8 or higher and a pip or pip3 Python package-management system is installed.

4. From the import directory in the unzipped migration tool folder, run one of the following commands:

   • Pip: pip install -r requirements.txt

   • Pip3: pip3 install -r requirements.txt

5. If you use a proxy server, define the following environment system variable:

   • Name: https_proxy

   • Value: http://<Proxy_Server_Address>:<Proxy_Server_Port>

6. Verify that you have outgoing internet access to the following locations:

   • *.controlm.com:443

   • *.amazonaws.com:443

7. From the import directory in the unzipped migration folder, run the following command to import your Control-M/EM data to Helix Control-M:

   • Windows: ./run_saas_migration_import.bat

   • Linux: ./run_saas_migration_import.sh

8. At the prompts, type the requested information, as described in Import Parameters.

   The import tool runs and a number of status messages appear that describe the steps of the import process.

Import Parameters

The following table describes the parameters that you must provide at the import tool prompts in Migrating to Helix Control-M.

Parameter	Description
Helix Control-M Automation API Endpoint	Defines the Helix Control-M Automation API endpoint, in the following format: <Tenant_Name>-aapi.<Zone>.controlm.com
Control-M Automation API Token	Defines the API token that you created in Migrating to Helix Control-M.
Compressed Archive Export File Pathname	Defines the pathname of the compressed archive export file that you created in Migrating to Helix Control-M. <Temporary_Folder>HelixEmMigrationTool\export\EMExportForSaaS.tar.gz
Python Interpreter Name	Defines the name of the Python interpreter that converts source code into machine language, as follows: Control-M/EM Host: bmcpython Separate Host: <Python_Interpreter_Name> Press ENTER to define the default Python interpreter—python3.

Generating a Server Token

This procedure describes how to generate a Server token, which enables you to add a self-hosted Control-M/Server or self-hosted Control-M for z/OS to Helix Control-M.

Begin

1. Log in to Helix Control-M with a user ID that is associated with an Admin role.

2. From the icon, select Configuration.

   The Configuration domain appears.

3. From the drop-down list, select Control-M/Servers.

   The Control-M/Servers pane appears.

4. Toggle on Self-Hosted and verify that your self-hosted Control-M/Servers or self-hosted Control-M for z/OS environments appear in the Self-Hosted area of the Control-M/Servers pane.

   In the Status column, a Ready to Connect button appears next to the added self-hosted Control-M/Servers or self-hosted Control-M for z/OS.

5. Select the required self-hosted Control-M/Server or self-hosted Control-M for z/OS, and then click Ready to Connect.

   A Control-M/Server Token dialog box appears with the token value and enables you to copy it to your clipboard.

   Record this token, which you must provide when you are prompted by the registration utility, as described in Connecting a Self-Hosted Control-M/Server to Helix Control-M Unified View and Connecting a Self-Hosted Control-M for z/OS to Helix Control-M Unified View.

Connecting a Self-Hosted Control-M/Server to Helix Control-M Unified View

This procedure describes how to disconnect a self-hosted Control-M/Server from your self-hosted Control-M/EM and connect it to Helix Control-M Unified View via the ctm_menu utility.

Before You Begin

• Verify that you are qualified to migrate your self-hosted Control-M/Server to Helix Control-M Unified View, as described in Helix Control-M Qualification.

• Verify that you have generated a server token in Helix Control-M, as described in Generating a Server Token.

Begin

1. Pause the self-hosted Control-M/Server, as described in Pausing a Control-M/Server or config server::pause.

2. Disable the self-hosted Control-M/Server, as described in Disabling a Control-M/Server, and verify that the Actual State is Disabled.

3. Unmanage the self-hosted Control-M/Server, as described in Unmanaging a Control-M/Server or config server::unmanaged.

4. Set the desired state of the Control-M/EM Gateway to Down from the CCM or via the following ccmcli utility command:

   ccmcli -u <Username> -p <Password> -t Gateway -n <Component_Name> -h <Component_Host> -cmd stop

5. From the self-hosted Control-M/Server host, do the following:

   1. Run the following command:

      ctm_menu

      The Control-M Main Menu appears.

   2. Press 1.

   3. Type 11 and follow the prompts.

      The registration utility runs and connects the self-hosted Control-M/Server to Helix Control-M.

6. From the Control-M/Servers pane in Helix Control-M, verify that the self-hosted Control-M/Server status changes from Ready to Connect to OK.

   The self-hosted Control-M/Server is now disconnected from the self-hosted Control-M/EM and is connected to Helix Control-M.

Connecting a Self-Hosted Control-M for z/OS to Helix Control-M Unified View

This procedure describes how to disconnect a self-hosted Control-M for z/OS from your self-hosted Control-M/EM and connect it to Helix Control-M Unified View via the ICE utility.

Before You Begin

• Verify that you are qualified to migrate your self-hosted Control-M for z/OS to Helix Control-M Unified View, as described in Helix Control-M Qualification.

• Verify that you have generated a server token in Helix Control-M, as described in Generating a Server Token.

• Verify that the Control-M API Gateway is installed, as described in Step 12 – Install Control-M API Gateway in the INCONTROL documentation.

Begin

1. Pause the self-hosted Control-M for z/OS, as described in Pausing a Control-M/Server or config server::pause.

2. Disable the self-hosted Control-M for z/OS, as described in Disabling a Control-M/Server, and verify that the Actual State is Disabled.

3. Unmanage the self-hosted Control-M for z/OS, as described in Unmanaging a Control-M/Server or config server::unmanaged.

4. Set the desired state of the Control-M/EM Gateway to Down from the CCM or via the following ccmcli utility command:

   ccmcli -u <Username> -p <Password> -t Gateway -n <Component_Name> -h <Component_Host> -cmd stop

5. From your Control-M for z/OS, load ICE, as described in Installing INCONTROL Products with ICE.

6. Select Installation.

   The IOA Installation menu appears.

7. Select Customized Installation.

   The IOA Customized Installation menu appears.

8. From the IOA Customized Installation menu, at the Option ===> prompt, type 2, at the Product ID ===> prompt, type CTM, and then press ENTER.

   The Major Steps Selection menu appears.

9. Select 13 - Register Control-M for z/OS to Helix CTM.

   The Minor Steps Selection menu appears for major step 13 - Register Control-M for z/OS to Helix CTM.

10. Follow steps 1–8 in the Minor Steps Selection menu, as described in Step 13 - Register Control-M for z/OS to Helix CTM.

    The self-hosted Control-M for z/OS is now connected to Helix Control-M.

Resuming All Connected Self-Hosted Control-M/Servers and Control-M for z/OS Environments

This procedure describes how to resume all connected, self-hosted Control-M/Servers and self-hosted Control-M for z/OS environments, which enables you to run jobs from Helix Control-M.

Before You Begin

• Verify that you have connected all required self-hosted Control-M/Servers and self-hosted Control-M for z/OS environments.

Begin

1. From the icon in Helix Control-M, select Configuration.

   The Configuration domain appears.

2. From the drop-down list, select Control-M/Servers.

   The Control-M/Servers pane appears.

3. Do one of the following:

   • From the Control-M/Servers Pane: Toggle on Self-Hosted and select the required self-hosted Control-M/Server or self-hosted for Control-M for z/OS, and then click Resume.

   • From a Command Prompt: Run config server::resume.

4. Verify that the self-hosted Control-M/Server or self-hosted Control-M for z/OS Actual State changes from Paused & Up to Up.

5. Resume the remaining connected, self-hosted Control-M/Servers and self-hosted Control-M for z/OS environments.

   You can now access your resumed, self-hosted Control-M/Servers and self-hosted Control-M for z/OS environments from Helix Control-M Unified View.

Removing a Self-Hosted Control-M/Server from Helix Control-M

This procedure describes how to remove a self-hosted Control-M/Server from Helix Control-M, which disconnects the self-hosted Control-M/Server and deletes its data from Helix Control-M.

Begin

1. From the icon in Helix Control-M, select Configuration.

   The Configuration domain appears.

2. From the drop-down list, select Control-M/Servers.

   The Control-M/Servers pane appears.

3. Toggle on Self-Hosted and from the Self-Hosted area of the Control-M/Servers pane, select the required self-hosted Control-M/Server, and click Delete.

   The Control-M/Server and all of its data is deleted from Helix Control-M.

4. Log in to Control-M/Server and run the following command:

   ctm_menu

   The CONTROL-M Main Menu appears.

5. Press 1 to select CONTROL-M Manager.

   The CONTROL-M Manager Menu appears.

6. Type 12 to select Unregister Control-M/Server from Helix Control-M/EM.

   The self-hosted Control-M/Server is removed from Helix Control-M.

You can now reconnect your self-hosted Control-M/Server to a self-hosted Control-M/EM.