Setting Up the Workflow Insights Environment

This procedure describes how to set up the Workflow Insights environment.

Before you begin

• Verify your Control-M/EM computers meet the requirements, as described in Control-M Workflow Insights System Requirements.
• Verify your Linux Control-M/EM computers have the proper Kernel settings, as described in Linux Kernel Parameters.
• If you first updated the version and then set the Linux kernel parameters, you must restart the Control-M/EM Configuration Agent.
• Verify the required ports are open, as described in Workflow Insights Ports.
• Verify the Control-M Self Service is installed on the Control-M/EM Primary, as described in Control-M Self Service installation.

To setup the Workflow Insights Environment:

1. Install or upgrade the Control-M/EM Primary to version 9.0.20.200 or higher, as described in Control-M/Enterprise Manager installation.
2. Install at least two dedicated Control-M/EM Distributed instances, as described in Control-M/Enterprise Manager installation.
3. install Control-M Workflow Insights on Windows on a Control-M/EM Distributed instance, as described in Installing Control-M Workflow Insights on Windows and Installing Control-M Workflow Insights on Linux.

   You must do the installations one at a time.

4. Define the Workflow Insight backups, as described in Defining Workflow Insights Backups.
5. Define the Workflow Insights configuration, as described in Configuring Workflow Insights.

   NOTE: 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.

   The Workflow Insights Environment is set up.