Scanning a Self-Hosted Environment

This procedure describes how to scan your self-hosted Control-M environment with BMC Services or a BMC certified partner. The scan produces qualification reports that enable you to determine the following:

  • The migration type that best suits your organization, as described in Control-M SaaS Migration.

  • The steps that you must take before you can migrate to Control-M SaaS.

You can run this tool from your Windows- or Linux-based Control-M/EM host.

You cannot migrate the following components to Control-M SaaS, but you can connect them to Control-M SaaS Unified View: 

  • Control-M for z/OS environments.

  • Control-M/Servers that are connected to the following types of Agents:

    • Agents that are installed on operating systems which are not supported in Control-M SaaS.

    • Agents that run plug-ins which are not supported in Control-M SaaS.

Before You Begin

  • Verify that Control-M/EM 9.0.20 or higher is installed.

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

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

    BMC recommends that you use the latest version of Control-M Automation API. For more information, see Setting Up the API.

Begin

  1. Log in to the host where Control-M/EM is installed with a username that is associated with an Admin role.

  2. Download the Control-M SaaS Qualification Tool from Control-M SaaS/EM Scanning and Migration Tools, and unzip it to a temporary directory.

  3. From a command line, navigate to the temporary directory where you unzipped the Control-M SaaS Qualification Tool, and run the following command:

    • Linux: SaasQualificationTool.sh -u <Control-M/EM_Username> -p <Control-M/EM_Password>

    • Windows: SaasQualificationTool.bat -u <Control-M/EM_Username> -p <Control-M/EM_Password>

    The tool scans your Control-M/EM and all connected Control-M/Servers, creates one Control-M/EM qualification report, and creates two Control-M/Server reports for every connected Control-M/Server. These reports are saved to the <Temporary_Installation_Directory>/report directory, as follows:

    • EM_Helix_Qualification.xlsx: Contains the Control-M/EM qualification scan results, which describes the actions that you must take before you can migrate to Control-M SaaS.

    • Server_Qualification_<Control-M/Server_Name>.xlsx: Contains the self-hosted-to-SaaS Control-M/Server qualification scan results, which describes the actions that you must take before you can migrate this Control-M/Server to a SaaS Control-M/Server.

    • Server_Qualification_Self_Hosted_<Control-M/Server_Name.xlsx>: Contains the self-hosted Control-M/Server qualification scan results, which describes the actions that you must take before you can connect this self-hosted Control-M/Server to Control-M SaaS Unified View.

  4. Send the compressed ControlMSaasQualificationResults_<Timestamp> file, which contains the results of the qualification scan, to BMC Services or a BMC certified partner.

  5. Navigate to the report directory, review the qualification reports, and do the following:

    1. Based on the qualification report results, determine which self-hosted Control-M/Servers will fully migrate and which will connect to Control-M SaaS Unified View.

    2. Follow the directions in the relevant qualification reports.

    3. Migrate to Control-M SaaS, as described in Control-M SaaS Migration.