It communicates with the Machine Agent.

It communicates with the Events Service.

It communicates with the AppDynamics Controller.

It communicates with the EUM Collector.

Should have eight or more CPU cores.

Should have identical hardware specifications.

Should be on the same local network.

Should be installed using the same user account.

Should be running the same operating system version.

to provide redundancy for the single-node

to use the embedded Events Service along with the single-node cluster

to allow for deployment growth in the events cluster

to hide the events server’s real name

If the agent is moved to a new location during the upgrade, the AppDynamics Controller must be reconfigured to reference the new location of the agent.

Controller-info.xml is the only file that needs to be migrated from the previous agent to the new agent.

After the Database Agent is upgraded, the AppDynamics Controller must be restarted.

The Database Agent must be stopped and restarted during the upgrade.

All data collectors created from the previous agent must be migrated to the new agent.

Vendor-supplied enterprise application that uses JMS

Custom TCP concurrent server

Pre-packaged WCF application

Customer proprietary SOAP application