Where to Configure Database Agent Properties
You can configure agent properties in the following locations:
- The controller-info.xml file located in the <db_agent_home>/conf directory
- The system properties (-D options) section in the JVM start-up script:
java -D<db_agent_system_properties> -jar <db_agent_home>/db-agent.jar
You can only configure agent properties related to naming agents or designating them as backup partners on the command line or in the JVM start-up script. However, you can specify the Controller/Agent connection details in the controller-info.xml file.
The system properties override the settings in the controller-info.xml file. System properties are case-sensitive.
Example Database Agent controller-info.xml File
<?xml version="1.0" encoding="UTF-8"?>
<controller-info>
<controller-host>192.10.10.10</controller-host>
<controller-port>8090</controller-port>
<account-access-key>165e65645-95c1-40e3-9576-6a1424de9625</account-access-key>
<!-- The following attribute enables or disables SSL communications between the agent and the Controller.-->
<controller-ssl-enabled>false</controller-ssl-enabled>
<!-- The following account-related parameters are necessary only for SaaS installations-->
<!--account-name></account-name-->
</controller-info>
Example Startup Configuration Using System Properties
A bash example. Note that the system properties are case-sensitive.
-Dappdynamics.controller.hostName=192.168.1.20 -Dappdynamics.controller.port=8090
Database Agent Properties
This section describes the Database Agent configuration properties, including their controller-info-xml elements and their system property options.
Required System Properties
Path to the Agent jar File
Description: Provides the absolute path to sqlijdbc_auth.dll.
System Property: -jar
Value: <db_agent_home>db-agent-jar
Type: If <db_agent_name> contains spaces, you must enclose the entire name in double quotes (" ") on Windows and single quotes (' ') on Linux .
Required: Yes
Example: -jar="D:\AppDynamics\Database Agent\db-agent.jar"
Path to the Java Library
Description: Provides the absolute path to sqlijdbc_auth.dll.
System Property: -Djava.library.path
Value:
- For 64-bit systems: <agent_home>\auth\x64
- For 32-bit systems: <agent_home>\auth\x32
Type: If <db_agent_name> contains spaces, you must enclose the entire name in double quotes (" ") on Windows and single quotes (' ') on Linux.
Required: Recommended. Required for SQL Server Windows Authentication on Windows 64-bit systems.
Example: -Djava.library.path="D:\AppDynamics\Database Agent\auth\x64"
Optional System Properties
Disable Retry on Auth Failure
Description: Stops retrying to establish JDBC connection when JDBC authentication fails.
System Property: -Dretry.on.auth.failure=false
Default: The system property is set to true.
Type: String
Supported Locales for Parsing Numbers
Description: Specifies which locale to use for parsing numbers. See Java 7 Supported Locales or Java 8 Supported Locales for valid values. Use the values for the Java version that you are running in your environment.
System Property: -Ddbagent.language
Default: The system property is set to en-US or en_US.
Type: String
Agent-Controller Communication Properties
Controller Host Property
Description: This is the host name or the IP address of the AppDynamics Controller, e.g. 192.168.1.22 or myhost or myhost.abc.com. This is the same host that you use to access the AppDynamics Controller UI.
Element in controller-info.xml: <controller-host>
System Property: -Dappdynamics.controller.hostName
Type: String
Default: None
Required: Yes
Controller Port Property
Description: This is the HTTP(S) port of the AppDynamics Controller. This is the same port that you use to access the AppDynamics browser-based user interface. If the Controller SSL Enabled property is set to true, specify the HTTPS port of the Controller; otherwise specify the HTTP port. See Controller SSL Enabled Property.
Element in controller-info.xml: <controller-port>
System Property: -Dappdynamics.controller.port
Type: Positive Integer
Default: For on premises installations, port 8090 for HTTP and port 8181 for HTTPS are the default ports the Controller listens to.
For the SaaS Controller Service, port 80 for HTTP and port 443 for HTTPS are the default ports the Controller listens to.
Required: Yes
Account Access Key Property
Description: This is the account access key used to authenticate with the Controller.
Element in controller-info.xml: <account-access-key>
System Property: -Dappdynamics.agent.accountAccessKey
Type: String
Default: None
Required: Yes. Prior to version 4.1, this property was required only for SaaS and multi-tenant Controllers. The account access key property is now required to authenticate all agent to Controller communications.
Example: -Dappdynamics.agent.accountAccessKey=165e65645-95c1-40e3-9576-6a1424de9625
Multiple Agent Environment Properties
The following properties are useful when you are configuring your system to include more than one Database Agent.
Database Agent Name Property
Description: This property uniquely identifies the Database Agent to the Controller.
System Property: -Ddbagent.name=<db_agent_name>
Type: ASCII string, including spaces. If <agent_name> contains spaces, you must enclose the entire name in double quotes (" ").
Default: Default Database Agent
Required: Required when you have more than one Database Agent reporting to the Controller.
You may want to run multiple Database Agents under the following conditions:
- When you have databases spread across multiple networks, and one machine cannot access all the databases on all the networks. In this case you can have a uniquely named Database Agent in each network that monitors the databases only visible on that network.
- If you have multiple SQL Server instances that each require different credentials, and you want to connect to them via Windows Authentication. When using Windows Authentication, the Database Agent will use the credentials of the currently logged in user.
- When you want one or more agents to back up a primary agent. The database agent names for your backup agents must match the database agent name of your primary agent. The last agent you launch will be the primary agent.
Example: -Ddbagent.name="Scarborough Network Database Agent"
Multi-Tenant Mode Properties
If the AppDynamics Controller is running in multi-tenant mode or if you are using the AppDynamics SaaS Controller, specify the account name and account access key for this agent to authenticate with the Controller.
If the Controller is running in single-tenant mode (the default) there is no need to configure these values.
Account Name Property
Description: This is the account name used to authenticate with the Controller.
If you are using the AppDynamics SaaS Controller, the Account Name is in the Welcome email AppDynamics sent to you.
Element in controller-info.xml: <account-name>
System Property: -Dappdynamics.agent.accountName
Type: String
Default: None
Required:
Yes for AppDynamics SaaS Controller and other multi-tenant users
No for single-tenant users.
Proxy Properties for the Controller
These properties route data to the Controller through a proxy.
Proxy Host Property
Description: This is the proxy host name or IP address.
Element in controller-info.xml: Not applicable
System Property: -Dappdynamics.http.proxyHost
Type: String
Default: None
Required No
Proxy Port Property
Description: This is the proxy HTTP(S) port.
Element in controller-info.xml: Not applicable
System Property: -Dappdynamics.http.proxyPort
Type: Positive Integer
Default: None
Required: No
Other Properties
Controller SSL Enabled Property
Description: This property specifies whether the agent should use SSL (HTTPS) to connect to the Controller. If SSL Enabled is true, set the Controller Port property to the HTTPS port of the Controller. See Controller Port Property.
Element in controller-info.xml: <controller-ssl-enabled>
System Property: -Dappdynamics.controller.ssl.enabled
Type: Boolean
Default: False
Required: No
Disable Sybase sp_sysmon execution
Description: This property specifies whether the agent should disable Sybase. You may want to disable Sybase monitoring with Database Visibility if you are already using other tools to monitor Sybase. Refer to Sybase Database Permissions for information on configuring Sybase permissions.
If an agent is run with the -Ddbagent.disable.sybase.ase.system.monitoring flag, Database Visibility will stop executing sp_sysmon for sybase databases. As a result, the following metrics might not show reliable data:
- Calls per Minute (KPI)
- All metrics under Server Statistic in the Metric Browser
- The Load value on the Sybase dashboard
Element in controller-info.xml: Not applicable
System Property: -Ddbagent.disable.sybase.ase.system.monitoring
Type: Boolean
Default: False
Required: No