Installing Control-M Workflow Insights on Windows

This procedure describes how to install Control-M Workflow Insights on Windows on a Control-M/EM Distributed instance.

Do not install multiple instances simultaneously.

Before You Begin

  • Verify that all Workflow Insights hosts meet the Windows requirements, as described in Control-M Workflow Insights System Requirements on Windows. If you cannot open any of the ports as described, you must define custom ports.

  • Verify that you have upgraded a primary Control-M/EM to version 9.0.20.200 or higher and installed at least two Control-M/EM Distributed hosts, as described in Control-M/Enterprise Manager Installation.

  • Verify that all Workflow Insights hosts are set to the same date-time.

  • Verify that the Firewall is open during installation by defining a Windows Inbound Rule and a Windows Outbound Rule that allows connection to all local TCP ports.

  • Enable the Automatically manage paging files size for all drives and No paging file parameters. Do not enable these parameters on the Control-M/EM Primary instance.

  • (Control-M Full Install only) From the Control-M Full Install host, run the following command to shut down the Control-M/Server:

    shut_ctm

  • Download the installation package, as described in Obtaining Control-M Installation Files.

Begin

  1. Log in to the Control-M/EM distributed host.

  2. Click the setup.exe file.

    The Control-M Workflow Insights Installation wizard appears.

  3. Do one of the following:

    • Interactive Installation: Follow the on-screen instructions until the installation is complete.

    • Automatic Installation: Do the following:

      1. Follow the on-screen instructions until the Summary window.

      2. Click Generate and select the location to create the XML parameter file.

      3. Click Yes to quit the installation.

        A confirmation message appears.

      4. Click Yes.

      5. Copy the automatic installation parameters file to a network location that is accessible to all hosts where you want to perform an automatic installation.

      6. Log in using a user ID with Administrator permissions on the current host.

      7. Run the following installation script:

        <Source_Path>\Setup.exe -silent <xml_path>\<filename.xml>

        The installation log can be found at the following location:

        <Installation_Folder>\<Control-M/EM home dir>BMCINSTALL\log\BMC_Control-M_Workload_Insights_Install _<date-time>.log

  4. Click Done.

    After you have installed or upgraded the primary Control-M/EM and installed Workflow Insights on the Control-M Distributed instances, you need to run a script on all these components that removes the Log4j v2 vulnerability, as described in 000391322.

  5. Repeat the previous steps for all Control-M/EM Distributed hosts.

  6. Open the CCM and locate the Primary and Control-M/EM Distributed instances and verify that all components and services are up with the status OK.

  7. From Control-M Web, from the Configuration domain, from the I_Web_Dropdown drop-down list > Workflow Insights Settings > Details, verify that the Control-M/EM Primary host and the Control-M/EM Distributed hosts related to the Workflow Insights installation are set to OK.

  8. Define the Workflow Insights Backups, as described in Defining Workflow Insights Backups.

    The Control-M Workflow Insights installation is complete.

To replace a lost Control-M/EM Distributed to the Workflow Insights environment, install Control-M/EM Distributed on a new host and then run the following script:

em_home/services/bin/WI_ReplaceDistrbuitedEM

Uninstalling Control-M Workflow Insights from Windows

This procedure describes how to uninstall Control-M Workflow Insights from Windows.

Begin

  1. From the Start menu, select Control Panel.

  2. Click Programs and Features.

  3. Select Control-M Workflow Insights and click Uninstall.

  4. Click OK to continue.

    Control-M Workflow Insights is successfully removed from your host.

If the Control-M Workflow Insights environment has two Control-M/EM Distributed instances, uninstalling one of the Control-M/EM Distributed instances automatically uninstalls the other Control-M/EM Distributed instance.