On this page:
Configurations are important since they let you customize your installations. The Enterprise Console enables you to configure these settings via GUI and CLI. However, note that there is limited support for updating service configurations through the CLI. Therefore, it is recommended that you use the GUI for updating configurations, especially for multi-line values.
Configuration settings on the Enterprise Console are separated into three categories: Platform, Controller, and Events Service Settings.
The Platform configuration allows you to update platform description in the UI. Updating the Platform path is only allowed in the CLI.
The Controller Settings pages allows you to tune your controller. You can configure settings such as database configurations, JVM options, listeners, and thread pools, for both single or high availability controllers.
The AppServer Configurations page under Controller Settings allows you to edit most of the domain.xml configurations. You can also change the ports and update the controller from a smaller to a higher profile. The configurations include:
Profile: Demo, small, medium, large, or extra large
You can change the Controller profile from a smaller profile to a larger one. Before doing so, ensure that the host machine meets the requirements for the profile size you want to use.
This process is not reversible, and you cannot move from a larger to a smaller profile size. If you tune the Controller heap settings or database configuration settings, even to be greater than the recommended settings for the new profile, those settings will be preserved. Otherwise, the AppDynamics recommended settings are applied.
To increase the Controller profile size, navigate to AppServer Configurations by choosing the platform, Configurations, Controller Settings, and Appserver Configurations. At the top of the page, select a new profile, then click Save.
Alternatively, you can also use the CLI to increase the Controller profile size to meet increased demand:
For more information, see Controller System Requirements.
- External URL (HA only): This is the deep link URL.
- Internal Virtual IP Address (HA only)
- Ports: Server Port: 8090; Admin Port: 4848; SSL Port: 8181; IIOP Port: 3700; JMS Port: 7676
To change the Controller ports, navigate to AppServer Configurations by choosing the platform, Configurations, Controller Settings, and Appserver Configurations. Near the top of the page, specify new ports and scroll down to click Save. This will restart the Controller. Note that the new ports should be available.
- JVM Options: You can update the JVM options via this page without having to use the modifyJvmOptions utility or any other external scripts.
- Domain Http Services
- Domain Protocols
Domain Network Listeners
Disabling the HTTPS listener is not allowed.
- Domain Transports
- Domain Thread Pools
DB Controller User Password
Alternatively, you can also use the CLI to change your password:
For MySQL DB:
For Aurora DB:
- Advanced configurations
- NUMA Controller Configuration: This setting is preserved upon upgrades.
- NUMA Database Configuration: This setting is preserved upon upgrades.
The Database Configuration page allows you to edit your MySQL settings. This is helpful since you do not have to tweak the configuration file on the database host. The configurations include:
DB Configuration Settings
Data Directory: (New in 4.4.2) You can change the datadir path and database port via this page.
Certain configurations such as the MySQL root directory are not allowed to be changed via the Enterprise Console.
DB Root Password
The Enterprise Console does not allow you to change the MySQL root password. However, if you change the MySQL root password for the Controller, you should update the database root password in the Database Configurations page so that the Enterprise Console is aware of the new password.
Reports Service Configurations
The Reports Service Configurations page allows you update the reports service ports:
- Reporting Service HTTP Port: 8020
- Reporting Service HTTPS Port: 8021
Events Service Settings
The Events Service configurations are read-only. See Administer the Events Service to learn how you can manage your Events Service. You can see the following configurations:
- Profile: This value is either Dev or Prod.
- Installation Directory
- Data Directory
- Elastic Search Port: 9200
- REST API Port: 9080
- REST API Admin Port: 9081
- Unicast Port: 9300
Update Controller Configurations
You can update Controller configurations such as the deep link URL, JVM options, and network listeners.
Update the Deep Link URL
To update the deep link URL:
Run the following command on the Enterprise Console host:
server-protocolis http or https.
Update JVM Options
To update JVM options and network listeners:
List all of the Controller configurations from the Enterprise Console:
controller-configs.conf, and copy all JVM options. Then paste them into a separate file, and edit the desired parameters.
Run the following command on the Enterprise Console host:
Retaining Configuration Changes
The Enterprise Console recognizes and retains many common customizations to the domain.xml, db.cnf, and other configuration files, but is not guaranteed to retain them all. If you have made manual configuration changes to the files, verify the configuration after updating.
You can also remove the Controller from the Enterprise Console and rediscover it to preserve the configuration changes:
On the Controller page, click on Remove Controller, or run the following command on the Enterprise Console host:
removeBinaries=falsethen the Enterprise Console forgets the Controller without impacting or uninstalling the Controller.
Discover the Controller by using the Discover & Upgrade feature as if you were upgrading the Controller using the Enterprise Console, or run the following command on the Enterprise Console host:
You must specify and provide the full path to the existing Controller directory.