Platform Component Ports

The following ports are open in a platform deployment. The "external" column indicates whether connections to the port occur entirely within the Controller host or from outside the host, and therefore may require firewall or load balancer configuration changes.

Port NameDefaultExternal?
Enterprise Console port9191Yes. The application uses port 9191 for all traffic.
SSH port22

The port needs to be open between the Enterprise Console and the remote hosts it manages. This is for Unix only and is not configurable.

Database server port

3388

No
Default database port3377No

Application server admin port

4848

No
Application server primary port (HTTP)8090

Yes

Application server SSL port (HTTPS)8181Yes
Events Service REST API port9080If the Events Service and Controller are on different hosts, you need to configure the port in the firewall or load balancer.
Events Service REST API admin port9081If the Events Service and Controller are on different hosts, you need to configure the port in the firewall or load balancer.
Reporting service HTTP port8020No
Reporting service HTTPs port8021No
Fleet Management Service Port8030

Yes, this port is required for the Agent Management.

Note: Ensure that the Controller has at least one HTTP port enabled to communicate with the Fleet Management Service.
EUM server port (HTTP)7001If EUM and the Controller are on different hosts, you need to configure the port in the firewall or load balancer.
EUM server SSL port (HTTPS)7002If EUM and the Controller are on different hosts, you need to configure the port in the firewall or load balancer.

At installation time, you can enter different ports manually. After installation, you can change the port settings by either reinstalling the Controller or by editing the port configuration as defined on the Enterprise Console Configurations page or in the underlying GlassFish application server, as described in the following sections.