BMC Application Diagnostics system architecture

The distributed architecture of BMC Application Diagnostics provides scalability and promotes strategies for high availability and disaster recovery. The product can stand alone or can be integrated with other products, such as BMC Real End User Experience Monitoring or BMC ProactiveNet.

BMC Application Diagnostics basic system architecture

The following figure illustrates the basic system architecture and where it integrates with BMC Real End User Experience Monitoring:

BMC Application Diagnostics basic system architecture

_{Click to expand image.}

AD architecture with APM Proxy.png

BMC Application Diagnostics system components

The BMC Application Diagnostics system consists of the following components, each of which is a virtual machine:

Component	Description
BMC Application Management Console	The Console hosts dashboards and system-management features, provides the interface to deep-dive business transaction data, and provides links to the optionally integrated BMC Real End User Experience Monitoring system. The Console enables you to monitor and diagnose multiple applications running on different application servers. To access the diagnostics data for applications, you click the Diagnostics tab. Every BMC Application Diagnostics system must have one AM Console component.
Application Diagnostics Agent	Each Diagnostics Agent is paired with a Diagnostics Collector. A Diagnostics Agent captures a sample of the transactions that have latency violations or errors. The captured data and the metrics data for the application server are sent to the Diagnostics Collector and stored in the MySQL database. The Diagnostics Agent is supported on several major application server platforms. The following agents are available: BMC Application Diagnostics Agent for Java—The Diagnostics Agent for Java runs on the application server Java virtual machine (JVM), and captures designated information about application transactions. The binaries for the Agent for Java can be used to manage multiple application servers that are installed on the same host. BMC recommends installing and matching multiple instances of the Diagnostics Agent on a one-to-one basis with different application server types. BMC Application Diagnostics Agent for .NET—The Diagnostics Agent for .NET consists of two components: Agent Core and Probe. Agent Core runs as a Windows service. The probe, a subcomponent of the BMC Application Diagnostics Agent for .NET, runs in the context of Internet Information Services (IIS) worker processes, and captures designated information about application transactions.
Application Diagnostics Server	The Diagnostics Server comprises a Diagnostics Portal, one or more Diagnostics Collectors, and (optional) one APM proxy.
Application Diagnostics Portal	The Diagnostics Portal manages Diagnostics Collectors, the APM proxy, and Diagnostics Agents. The Portal communicates with associated Diagnostics Collectors to gather the relevant data to be displayed in the Console.
Application Diagnostics Collector	The Diagnostics Collector receives data from one or more Diagnostics Agents. The Diagnostics Collector stores the information for the application that is monitored by the Diagnostics Agent. Each Diagnostics Collector has its own MySQL database, where all information is saved.
APM proxy	The APM proxy receives and processes end-user experience data and communicates with the Diagnostics Collectors. In the Console, you can examine end-user data through the User tier in the Application View or the User Transactions page.