When deploying AppDynamics, you may need to open ports in a network firewall or configure a load balancer to enable communication between the Controller and the rest of the AppDynamics platform.
For SaaS, you only need to adjust your infrastructure to accommodate the HTTPS port provided to you by AppDynamics. For an on-premises deployment, however, you may need to make additional adjustments based on the information here.
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 Name | Default | External? |
|---|
| Enterprise Console port | 9191 | Yes. The application uses port 9191 for all traffic. |
| SSH port | 22 | 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. If you have a requirement to configure the port, contact AppDynamics support. |
Database server port | 3388 | No |
| Default database port | 3377 | No |
Application server admin port | 4848 | No |
| Application server primary port (HTTP) | 8090 | |
| Application server SSL port (HTTPS) | 8181 | Yes |
| Events Service REST API port | 9080 | If 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 port | 9081 | If the Events Service and Controller are on different hosts, you need to configure the port in the firewall or load balancer. |
| Reporting service HTTP port | 8020 | No |
| Reporting service HTTPs port | 8021 | No |
| Fleet Management Service Port | 8030 | Yes, this port is required for the Agent Management.
Ensure that the Controller has at least one HTTP port enabled to communicate with the Fleet Management Service.
|
| EUM server port (HTTP) | 7001 | If 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) | 7002 | If 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.
Editing Controller Port Configurations
You can modify connection settings through the Enterprise Console UI. The Enterprise Console will automatically update all occurrences in the controller for you. You do not need to manually update all the files and manage the sequence to restart services. See Update Platform Configurations.
You can also edit the ports manually by editing configuration files used by the application server for the Controller domain. Updating the ports manually, however, will cause the Enterprise Console to have no visibility into the updates and cause health-check errors.
The following sections list the settings you need to modify to change a port.
Change the Primary Server Listening Port
- Log in to the Enterprise Console GUI.
- Navigate to Configurations > Controller Settings > Appserver Configurations.
- In the Basic tab, update Server Port.
- Click Save.
Change the Database Port
- Log in to the Enterprise Console GUI.
- Navigate to Configurations > Controller Settings > Database Configurations.
- Update the port values in DB Configuration Settings.
- Click Save.
Change the Fleet Management Port
- Log in to the Enterprise Console GUI.
- Navigate to Configurations > Controller Settings > Fleet Management Configurations.
- Update Fleet Management Service Port.
- Click Save.
