This topic describes the different components that you deploy for the BMC Application Diagnostics environment.
The server-side of BMC Application Diagnostics is comprised of the following components:
APM Proxy
Required when using browser instrumentation to monitor the end-user experience, the Application Diagnostics environment requires one instance of the APM Proxy, and you cannot install it on the computer where the Application Diagnostics Portal is installed.
You can install the Diagnostics Server components on one computer, for a small environment, or you can deploy several Diagnostics Collector components over separate computers.
For information about planning for and implementing Active EUEM so that you can collect end-user metrics through browser instrumentation, see the following topics:
To create a PDF that describes how to implement this use case, click here. The PDF export begins when you click the link and requires 30-60 seconds to complete.
You create new MySQL databases during BMC Application Diagnostics Server installation. The databases are installed locally on the Diagnostics Portal and Collector host or hosts. These are the only databases that the Diagnostics Server uses.
After you install the BMC Application Diagnostic Server, you must install Diagnostics Agents on each application server that you want to monitor. The Diagnostics Agent monitors and collects information required for each application. Each Diagnostics Agent is paired with a Diagnostics Collector and sends captured information to the Collector.
BMC Application Diagnostics system architecture
Sizing the Application Diagnostics Server components