The following table describes the default ports that are used by Workflow Insights for both Windows and Linux.
NOTE: The ports must be open for all hosts in the Workflow Insights environment, including Control-M/EM Primary and Control-M/EM Distributed servers.
If you cannot open any of these ports, you must define custom ports in the designated screen of the Workflow Insights installation. The Workflow Insights installation is described in Installing Control-M Workflow Insights on Windows or Installing Control-M Workflow Insights on Linux.
Port Name |
Default Port |
Set during installation of |
Port Purpose |
|---|---|---|---|
KAFKA_PORT |
19092 |
Control-M/EM Primary |
Determines the Kafka server port used for micro-service communications. |
ZOOKEEPER_LE_PORT |
3888 |
Control-M/EM Primary |
Determines the Kafka cluster port via which the primary host is chosen. |
ZOOKEEPER_FOLLOWERS_PORT |
2888 |
Control-M/EM Primary |
Determines the Kafka cluster port via which the Kafka Follower nodes communicate with the Leader node. |
ZOOKEEPER_CLIENT_PORT |
12181 |
Control-M/EM Primary |
Determines the Kafka port used for Zookeeper communication. |
ELASTIC_TRANSPORT_PORT |
19200 |
Control-M/EM Distributed 1st Workflow Insights Activation |
Determines the Elastic cluster port used for communication between Elastic client and server based on http/https. |
ELASTIC_HTTP_PORT |
19300 |
Control-M/EM Distributed 1st Workflow Insights Activation |
Determines the Elastic cluster port used for communication between the Elasticsearch nodes. |
KIBANA_PORT |
15061 |
Control-M/EM Distributed 1st Workflow Insights Activation |
Determines the Control-M WEB and Kibana port used for communication between Kibana client and server, based on http/https. |
WORKFLOW INSIGHT Service API PORT |
DYNAMIC |
Post-installation step |
Determines the CONTROL-M WEB API port used for API requests |
For more information see:
Parent Topic |