Each monitored JVM must have a unique combination of tier and node name in Splunk AppDynamics. Naming the components in the wizard varies between the self-service trial edition of Splunk AppDynamics and the non-trial edition:

• For the self-service Pro Trial edition of Splunk AppDynamics Pro, the wizard names the application and tier for you using the format described in the following section. You can always change the names later.
• For a non-trial edition, you name the application and tier in the wizard, while the wizard generates the node name.

For self-service trials of Splunk AppDynamics Pro, the getting started wizard uses the following naming scheme to identify agents:

• Node name: < app_server_type >@< hostname >:< port > For example: JBoss@appserver1.example.com:8080
• Tier name: MyTier
• Application name: MyApp

The port number in the node name ensures that each node has a unique name if there is more than one app server on the same machine.

If the application server listens on multiple ports, the node name uses the lowest of the port numbers. Notice that the lowest port number may not be the primary port for the host. For instance, if a server listens for client requests at 8080 but listens for shutdown requests on port 8005, the node will be named with the 8005 port.

The Controller identifies distinct tiers based on traffic flow between nodes. All tiers belong to a single business application, MyApp.