Configure App Agent for Java on Multiple JVMs on the Same Machine that Serves the Same Tier

This topic describes how to configure the App Agent for Java for multiple JVMs that are located on a single machine and are serving the same tier.

For example, ACME Bookstore has a physical server with five JVMs installed on it. All of these JVMs are used for the Inventory Services.

For such cases, follow these rules:

All of the information unique to a JVM should be configured using the system properties in the start-up script.

Information in the startup scripts always overrides the information in the controller-info.xml file.

1. Provide the application and tier name in the controller-info.xml file.

2. Add the javaagent argument and system property (-D option) for the node name to the batch file or startup script of each JVM.

java -javaagent:<Agent-Installation-Directory>/javaagent.jar -Dappdynamics.agent.nodeName=$nodeName

Separate the system properties with a white space character.

The following illustration displays how this configuration is applied to the ACME Bookstore.

The application and tier names can also be configured using the system properties. See App Agent for Java Configuration Properties.

Some application server management consoles allow you to specify start-up arguments using a web interface. See Java Server-Specific Installation Settings.