AppDynamics Application Intelligence Platform

3.8.x Documentation

PDFs

Videos

Release Notes

AppDynamics Inc.

Skip to end of metadata
Go to start of metadata

When deploying AppDynamics, whether using an on-premise or SaaS Controller, you will likely need to open ports in a network firewall or configure a load balancer to enable communication between the Controller and App Agents and client browsers. 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.

This topic lists the ports used by the Controller. 

Controller Ports

By default the Controller uses the following ports for internal communication among its components:  

Port Name

Default

Application server primary port (HTTP)

8090

Application server primary port (HTTPS)

8181

Database server port

3388

Application server admin port

4848

Application server JMS port

7676

Application server IIOP port

3700

At installation time, the install wizard may suggest other port numbers if the default ports are used on the target system, or 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 in the underlying GlassFish application server, as described here. 

Reinstalling the Controller with New Port Settings

Use the reinstall procedure if you want to modify connection settings without editing configuration files.

To reinstall the Controller with new port settings

  1. Shut down the Controller. For instructions see Start or Stop the Controller.
  2. Create a complete backup of the Controller installation directory and all of its sub-directories.
  3. Re-install the Controller in the same installation directory as your original Controller and choose the new port settings while running the installer. For instructions see Install the Controller on Linux or Install the Controller on Windows.

(warning) Even though the versions are the same, this step is handled as an upgrade by the Controller installer.

Editing Controller Port Configurations

If reinstalling the Controller is not convenient, you can edit the ports manually by editing configuration files used by the application server for the Controller domain.

The following sections list the settings you need to modify to change a port. After making manual edits to configuration files, you will need to restart the Controller to have your changes take effect.

To change the primary server listening port:

  1. In the Controller home directory, navigate to the appserver/glassfish/domains/domain1/config/ directory. 
  2. Open domain.xml for editing. 
  3. Change the port number as it appears in these locations:
    • The value of the network-listener element with the attribute id="http-listener-1" for the primary listening port, or http-listener-2 for the secure listening port to the new port setting.
    • The JVM argument values for the Controller HTTP port and Controller services port under the config element named server-config.
  4. For each deployed agent, navigate to proxy/conf in the agent home directory and change the controller-port value in controller-info.xml. 
  5. Change the serverPort or sslPort number in the Controller home directory: .install4j/response.varfile. This ensures that the new port number will not be overwritten upon upgrade.

To change the database port:

  1. Under the Controller home directory, edit the file appserver/glassfish/domains/domain1/config/domain.xml to change the database listening port where it appears under the jdbc-connection-pool element named controller_mysql_pool. It appears as the value of the property named portNumber.
  2. Edit the file appserver/glassfish/domains/domain1/imq/instances/imqbroker/props/config.properties to change the "imp.persist.jdbc.mysql.property.url" variable so that it includes the new port number. This variable is the JDBC connection string. 
  3. In db/db.cnf, set the "port=" variable to your new port setting.
  4. In the bin/controller.bat (.sh), change the "DB_PORT" variable to your new port setting.
  5. Edit .install4j/response.varfile to change the databasePort value to the new port. This ensures that the new port number will not be overwritten in a future Controller upgrade.

To change the Glassfish admin listening port:

  1. In appserver/glassfish/domains/domain1/config/domain.xml, change the port attribute value of the http-listener element to the new port. This is the element with an id attribute value of "admin-listener".
  2. Also in the Controller home directory, change the adminPort value in .install4j/response.varfile. This ensures that the new port number will not be overwritten in a future Controller upgrade.

To change the JMS port:

  1. In appserver/glassfish/domains/domain1/config/domain.xml, change the port attribute value for the jms-host element with the name attribute of default_JMS_host.
  2. Change the jmsPort value in .install4j/response.varfile. This ensures that the new port number will not be overwritten in a future Controller upgrade.

To change the IIOP listening port:

  1. In appserver/glassfish/domains/domain1/config/domain.xml, edit the port attribute value of the iiop-listener element with an id attribute of orb-listener-1.
  2. Change the iiopPort value in <controller_home>/.install4j/response.varfile. This ensures that the new port number will not be overwritten in a future Controller upgrade.