Download page Plan the Machine Agent Configuration.
Plan the Machine Agent Configuration
AppDynamics provides multiple ways to configure the Machine Agent. As part of planning your installation, determine which options work best in your environment:
- System properties
- Environment variables
See Configure the Machine Agent
Collect Configuration Information
Determine your configuration requirements and collect the necessary information. See Machine Agent Configuration Properties
|Determine your installation scenario|
For new installations, see Machine Agent Installation Scenarios
For upgrades, see Upgrade the Machine Agent
Location of the startup script
You add startup arguments and system properties in the startup script.
|Memory and CPU||See Machine Agent Requirements and Supported Environments|
|Connecting the agent to the Controller||You need to know the Controller host, Controller port, and account access key where you want your metrics to be reported. The account access key is generated at the Controller installation time and is located on the AppDynamics Administration Console.|
|(Optional) SSL Communications|
If you plan to use SSL to communicate with the Controller, see Enable SSL for Machine Agent
If you plan to connect to the Controller using a proxy server, you need to know the Proxy host, Proxy port, and the path to the Proxy Password file.
|Multi-tenant mode or SaaS Installations|
In addition to the Account Access property, use the Account Name property to configure multi-tenant mode or SaaS account Information. This information is provided in the Welcome email from the AppDynamics Support Team. You can also locate this information in the <controller_home>
|Deploying from a common directory||See Deploy Multiple Machine Agents From a Common Directory|
|Extension considerations||If you plan to use a number of extensions in your environment, see the "Extension Considerations" section in Machine Agent Requirements and Supported Environments|
|Enabling Server Availability and Service Availability Monitoring||Server Availability requires a separate license. See Enable Server Visibility|