Configure App Agent for Java in Mainframe Environments

In some environments JVMs have transient identity, such as when a single script spawns multiple JVMs.

For example, an environment may consist of WebSphere on IBM Mainframes, using a dynamic workload management feature that spawns new JVMs for an existing application server (called a servant). These JVMs are exact clones of an existing JVM, but each of them has a different process ID. Based on load, any number of additional JVMs may be created.

To name nodes automatically

The App Server Agent can automatically name the dynamically generated JVMs using the appdynamics.agent.reuse.nodeName property. See Reuse Node Name Property to enable re-use of node names and Auto Node Name Prefix Property to set the prefix used for automatically-named nodes. You specify these properties in your startup script, using the following format:

-Dappdynamics.agent.reuse.nodeName=true
-Dappdynamics.agent.reuse.nodeName.prefix=<node name prefix>

If you are using these properties, ensure that you have not specified the node name anywhere (controller-info.xml file or as a system property) in your JVMs start-up script.

The following illustration shows the sample configuration for ACME Bookstore. This configuration will create unique node names for every instance of the virtual machine starting up in the ACME Bookstore environment.

The name of a node is available for reuse if the node has been out of contact with the Controller for a period of time that exceeds the node retention setting. For more about historical nodes, node retention and deletion, see Remove Unused Nodes.

Learn More