You can reference system properties from the command line, or in the agent configuration file to specify the node name, tier name, or other agent configuration properties dynamically.

For example, consider a Java application started with a script named startserver.sh. The script defines a system property as:

-Dserver.name=$1

The property server.name will get the value of the first argument passed when starting the script. For example, the following command to start the JVM would bind the server.name property to the value ecommerce01:

startserver.sh ecommerce01

You can use this value in your agent configuration by setting the -Dappdynamics.agent.nodeName property at startup:

-Dappdynamics.agent.nodeName=$server.name

Or, you can use the value in the controller-info.xml file, using this format:

${system_property_name}

For example:

<controller-info>
...
<node-name>${server.name}</node-name>
</controller-info>

Note that server.name is the name of a sample system property used here to identify the node. Use an appropriate system property that is available in your environment for the Java Agent node name.

To have tier names assigned dynamically, supply a dynamic value to the tier name property:

java -javaagent:<agent_home>/javaagent.jar -Dappdynamics.agent.tierName=$tierName -Dappdynamics.agent.nodeName=$nodeName

You can combine multiple system properties to name nodes or tiers. For example, in controller-info.xml, combine properties as:

${system_property_name_1}${system_property_name_2}

You can combine system properties with literals. In the following example "_" and "inventory" are literals.

${myhost.name}_${myserver.name}.inventory

You can use existing system properties for the Controller host and port settings as well; however, combining properties as shown here is not supported for those settings.