This article describes how to configure the AppDynamics Java Agent multiple JVMs that reside on a single machine. The JVMs may serve the same or different tiers in the AppDynamics model.
In either case:
All of the common information should be configured using controller-info.xml.
All of the information unique to a JVM should be configured using the system properties (-D option) in the startup script.
Information in the startup scripts always overrides the information in the controller-info.xml file.
Any customizations to app-agent-config.xml and custom-activity-correlation.xml configuration will apply to all agents.
This scenario can generate a lot of logs and disk IO activity. You can edit the log configuration at <agent_home>/<version_number>/conf/logging/log4j.xml to control the maximum size of individual logs and the number of logs the agent retains for log rotation.
Configure the Agents for the Same Tier
For this case, you only need to differentiate the node names in the JVM startup script and use controller-info.xml for the other settings, as follows:
Configure the application and tier name in controller-info.xml.
Add the javaagent argument and system property for the node name to the batch file or startup script of each JVM.