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 computers meet the Windows requirements, as described in Control-M Workflow Insights System Requirements for Windows. If you cannot open any of the ports as described, you must define custom ports.
-
Verify that you upgraded a primary Control-M/EM version 9.0.20.200 or later and installed at least two Control-M/EM Distributed hosts, as described in
-
Verify that all Workflow Insights computers are set to the same date-time.
-
Download the Control-M Workflow Insights activation CD, as described in Obtaining Control-M Installation Files.
-
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.
Begin
-
Log in to the Control-M/EM distributed computer.
-
From the Control-M Workload Insights activation CD, click the setup.exe file.
The Control-M Workflow Insights Installation wizard appears.
-
Do one of the following:
-
Interactive install: Follow the on-screen instructions until the installation is complete.
-
Automatic install: Do the following:
-
Follow the on-screen instructions until the Summary window.
-
Click Generate and select the location to create the XML parameter file.
-
Click Yes to quit the installation.
A confirmation message appears.
li class="listalpha2"> Click Yes.
-
Copy the automatic installation parameters file to a network location that is accessible to all computers where you want to perform an automatic installation.
-
Log in using a user ID with Administrator permissions on the current computer.
-
Ensure that the installation CD is still in the CD drive, and run the installation script, as follows:
<source_path>\Setup.exe -silent <xml_path>\<filename.xml>
The installation log can be found at the following location:
<installFolder>\<Control-M/EM home dir>BMCINSTALL\log\BMC_Control-M_Workload_Insights_Install _<date-time>.log
-
-
-
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.
-
Repeat the previous steps for all Control-M/EM Distributed hosts.
-
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.
-
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 computer and the Control-M/EM Distributed computers related to the Workflow Insights installation are set to OK.
-
Define the Workflow Insights Backups, as described in Defining Workflow Insights Backups.
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
-
You must periodically replace the Kibana and Elasticsearch certificates, as described in Kibana Certificate Management and Elasticsearch Certificate Management.
Uninstalling Control-M Workflow Insights from Windows
This procedure describes how to uninstall Control-M Workflow Insights from Windows.
Begin
-
From the Start menu, select Control Panel.
-
Click Programs and Features.
-
Select Control-M Workflow Insights and click Uninstall.
-
Click OK to continue.
Control-M Workflow Insights is successfully removed from your computer.
If the Control-M Workflow Insights environment has two Control-M/EM Distributed instances, uninstalling one of the Control-M/EM Distributed instances triggers the automatic uninstallation of the other Control-M/EM Distributed instance.