Architecture


This section describes the following architectural elements:

BMC Application Diagnostics components

BMC Application Diagnostics comprises the following components.

BMC Application Diagnostics Server

The BMC Application Diagnostics Server comprises of the BMC Application Diagnostics Portal and the BMC Application Diagnostics Collector

BMC Application Diagnostics Portal

The BMC Application Diagnostics Portal is the main component for managing both BMC Application Diagnostics Collectors and BMC Application Diagnostics Agents.

Each BMC Application Diagnostics Portal supports up to 1000 BMC Application Diagnostics Agents. The agents are divided between BMC Application Diagnostics Collectors (usually, up to 5), allowing 200 agents per BMC Application Diagnostics Collector.

BMC Application Diagnostics Collector

The BMC Application Diagnostics Collector communicates with one or more BMC Application Diagnostics Agents. It is used to store the information on the application that is monitored by the BMC Application Diagnostics Agent. Each Collector has its own MySQL database where all information is saved. You can install and define up to 5 BMC Application Diagnostics Collectors per BMC Application Diagnostics Portal.

BMC Application Diagnostics Agent

The BMC Application Diagnostics Agent monitors and collects information required for each application.

Each BMC Application Diagnostics Agent is paired with a BMC Application Diagnostics Collector. The BMC Application Diagnostics Agent sends captured information to the BMC Application Diagnostics Collector.

BMC Application Diagnostics Agent for Java

The BMC Application Diagnostics Agent for Java runs on the application server Java virtual machine (JVM), and captures interesting information on application transactions. The  Agent for Java runs only on application servers running Java 1.5 and later. The binaries for BMC Application Diagnostics Agent for Java can be used to manage multiple application servers that are installed on the same host. BMC recommendeds that multiple instances of the Agent be installed and matched on a one-to-one basis with different application server types.

The BMC Application Diagnostics Agent for Java supports major application server platforms, including the following:

  • IBM Websphere
  • Oracle Weblogic
  • Red Hat JBoss
  • Apache Tomcat

BMC Application Diagnostics Agent for .NET

The BMC Application Diagnostics Agent for .NET consists of two components: Agent Core and Probe. The 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 interesting information on application transactions.

The BMC Application Diagnostics Agent for .NET supports the following application server platforms:

  • IIS 6.0
  • IIS 7.0
  • IIS 7.5

BMC Application Performance Management Console

The BMC Application Performance Management Console serves as the graphical user interface for accessing BMC Application Diagnostics captured information. The BMC Application Performance Management 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.

BMC Application Diagnostics and BMC Real End User Experience Monitoring

BMC Real End User Experience Monitoring and BMC Application Diagnostics are licensed add-ons of BMC Application Performance Management. They both connect to the BMC Application Performance Management Console with browser software.

BMC Real End User Experience Monitoring captures data about the end user experience. It monitors applications and the interactions between applications and end users.

BMC Application Diagnostics monitors and identifies performance issues in these applications. BMC Application Diagnostics complements BMC Real End User Experience Monitoring by providing visibility of performance issues occurring behind the web server. BMC Application Diagnostics helps administrators isolate and detect issues in applications and provides a common application diagnostics platform.

BMC Application Diagnostics and event integration

BMC Application Diagnostics provides several options to sending event information to integrated technologies and external applications. The following kinds of events can be sent:

  • Application events, such as crossing a latency threshold and percentage of errors
  • Application server events, such as JMX metrics, thread pools, and connection pools
  • System health events, such as issues with BMC Application Diagnostics agents, collectors or the portal

The agent sends events to the server, and the portal sends the events to the active integrations. The following integrations are supported:

  • BMC ProactiveNet
  • SNMP
  • SMTP
  • Syslog
  • CSV

BMC Application Diagnostics operational flow

Once the BMC Application Diagnostics Agent has been installed on the application server, a sample of the transactions with latency violations or errors on that application server are captured. This captured data, and the metrics data for the application server, is sent to the BMC Application Diagnostics Collector and stored in the MySQL database.

The BMC Application Diagnostics Portal manages the BMC Application Diagnostics Collectors and Agents, and communicates with its managed collectors to pull the relevant data for display in the BMC Application Performance Management Console.

BMC Application Diagnostics and BMC Application Performance Management data flow

ADOPS Architecture with NET.png

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*