Control-M Workflow Insights installation requires multiple component installations and configurations across several computers. Due to the large number of metrics that Workflow Insights gathers and processes, the installation requires more CPU, disk space, different kernel parameters settings, and specific port configurations than a typical Control-M installation. Therefore, it is crucial that you review the architecture and requirements before you install (see Setting Up the Workflow Insights Environment).
The installation includes one Control-M/EM primary host and at least two dedicated Control-M/EM Distributed hosts, to avoid performance impact on the Control-M/EM primary.
Note: Workflow Insights only supports one Control-M/EM distributed node down at any one time. If more than one distributed node is down, Workflow Insights cannot function.
After Workflow Insights is installed, the following services are included in the Control-M/EM Distributed computers and appear in the CCM:
Elasticsearch: A third-party search engine based on the Lucene library that is used in Workflow Insights to gather information and perform queries. This service is also included in the Control-M/EM Primary.
Kibana: A third-party data visualization dashboard software for Elasticsearch that is used in Workflow Insights, which displays the collected data in the dashboards.
Workflow Insights: A service that manages and maintains data in Elasticsearch, sends new data to the Elasticsearch, orders backups, and creates and updates indexes.
The demands of the above services require that before Workflow Insights installation you must prepare the hosts used in the installation, as follows:
System Requirements: The Elasticsearch process requires significant memory, CPU, and disk space, which require the Control-M/EM servers to meet certain requirements.
System Settings: The Elasticsearch process requires non-default kernel settings for Linux installations and paging settings for Windows installations before installing the Control-M/EM Primary or Control-M/EM Distributed instances.
Open Ports: The required ports for Elasticsearch, Kafka, Zookeeper, and Kibana must be opened in the firewall for both the Control-M/EM Primary and Control-M/EM Distributed instances. If the required ports are not open during installation, you might need to change the ports.
If you are upgrading the primary to 9.0.20.200 the additional ports that Kafka requires are automatically defined. You cannot define custom ports during the upgrade.
If you install the default Workflow Insights installation option, you cannot assume that the default ports are defined. If a port is busy, the installation automatically selects the next available port.
If your Workflow Insights environment includes a Secondary Control-M/EM host for High Availability, you must open the same ports in the Secondary Control-M/EM host as are open in the Control-M/EM primary host.