This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
All versions of Control-M/Enterprise Manager All versions of Control-M/Server for UNIX and Microsoft Windows All versions of Control-M/Agent for UNIX and Microsoft Windows
- What TCP/IP ports are used by Control-M?
- What ports need to be opened in firewall for Control-M communication?
- What are the ports used between Control-M/EM Server, Control-M/EM Clients, Control-M/Server and Control-M/Agent?
- What TCP/IP ports that need to be opened in the firewall and used by Control-M/Enterprise Manager, Control-M/Server and Control-M/Agent?
1a. Ports between CONTROL-M/EM clients and CONTROL-M/EM servers version 9.0.18 and higherAll communication between Control-M/EM clients and -server is through the Control-M/EM web server.
Therefore, the only port(s) that need to be opened in the firewall are the http port (default 18080), and/or the https port (default 8443).
1b. Ports between CONTROL-M/EM clients and CONTROL-M/EM servers up to version 9.0.00
These ports need to be opened for incoming traffic and allow bi-direction communication on these session
|Parameter||Default||Need to open in Firewall||Description|
|CORBA Naming Service||13075||Yes||This is the Communications port used by the Control-M/EM client to communicate with the Control-M/EM CORBA server|
|Control-M/EM GUI Server||Random/Range||Yes||This is the Communications port used to perform all user-initiated functionality for Control-M/EM clients (GUI, Desktop and CLI utilities)|
|Control-M/EM Global Alerts Server||Random/Range||Yes||This is the Communications port used to identify, maintain and distribute Control-M alerts to Control-M/EM GUIs|
|Control-M Configuration Server||Random/Range||Yes||This is the Communications port used by the CCM GUI to communicate with the Control-M Configuration Manager Server|
|Control-M/Forecast||Random/Range||Yes||This Communications port is needed for Control-M/Desktop client to connect to Control-M/Forecast Server when performing a 'Forecast' action on a job that uses Calendars|
|BMC Batch Impact Manager Server||Random/Range||Yes||This Communications port is needed by Control-M/EM GUI client to connect to BIM when performing an 'add/edit BIM/Forecast Rules' action|
|Control-M Self-Service||Random/Range||Yes||Used by Self-Service client|
|Control-M Archived Server||Random/Range||Yes||Used by Self-Service client and EM client|
C. The tomcat web server port is used by the V9 Workload Automation Client to verify the latest version of the Client, for end user deployment, and On-line Help. The port is configured in ./etc/emweb/tomcat/conf/server.xml file
2. Ports between Control-M/EM Server, Control-M/Server and their respective databases
in v9 with HA enabled using ProgreSQL the primary and the secondary machine need to be able to initiate a Database connection from one machine to the other. (See HaWithPG diagram attached)
It is used for the communication between the two Control-M/Server CA (Configuration Agent) processes only.
3. Ports between Control-M/Server and Control-M/Agent
|Agent to Server Port||7005||Communication port from the Agent to Server. This will have to be open as incoming to Control-M/Server|
|Server to Agent Port||7006||Communication port from the Server to Agent .This will have to be open as incoming to Control-M/Agent|
B. If 'persistent connection' is used, then only the Server to Agent Port will have to be open in the firewall
NOTE: Please refer to resolution KM-000010055291 for additional information about ports used by Control-M products
NOTE: Control-M HA configuration requires additional ports and configuration, please see 000105462.
Customers viewing this solution may find value in the following self-help Connect with Control-M video.