BTM's architecture is based on a series of distributed components (Observers, Monitor Servers, and Central Servers) that constantly interact in order to capture, process, analyze, and present transactional data in a human-readable fashion.
The following diagram shows a high-level architecture view of BTM:
As can be appreciated from the above diagram, BTM consists of:
- Observers: They are basically agents that are deployed into the application server(s) that host the business application(s) that participate in a SOA transaction and therefore require monitoring. Observers can monitor several types of components and there are different types based upon the system or application that they monitor. For example, in the case of Weir & Bell Telecom, the following observers were used:
BTMObserver_Wls_10.3_JavaEE_*.zip: It is an observer for Java EE on WebLogic 10.3.x.BTMObserver_Wls_10.3_Soa11gR1_*.zip: It is an observer for Oracle SOA Suite on WebLogic 10.3.x.BTMObserver_Wls_10.3_Osb11gR1_*.zip: It is an observer for Oracle Service Bus 11gR1 on WebLogic 10.3.x.BTMObserver_Wls_10.3_FApps11gRUP1_*.zip: It is an observer for Oracle Fusion Applications.
- Monitors (btmMonitor.ear): They collect the data sent from the observers (such as performance data and measurements amongst others) and post processes it. A Monitor is basically an EAR archive that has to be deployed into an application server. For large volume configurations, a complex topology of multiple monitors can be configured (either as singletons or replicates) along with load balancers in order to achieve maximum performance and availability.
In production environments it is not recommended to deploy monitors into the same application server as the Central Servers. Doing so may result in performance issues.
- Central Servers (Sphere): All central servers are also EAR archives that are deployed into an application server. There are 3 types of central servers:
- Main Server (btmMain.ear): It contains all the central system services and user interface components, including the sphere. The Sphere is the component that manages the BTM environment.
- Performance Server (btmPerformanceServer.ear): It is responsible for gathering measurements from measurement sources (monitors) and performing time-based aggregation of data. It also provides a query interface to access the monitored data.
- Transaction Server (btmTransactionServer.ear): It is responsible for monitoring transaction instances. Configures the system to collect appropriate data and performs correlation of message data to form a single transaction instance.
Similar to the monitor servers, central servers should be deployed individually and into their own application servers.
Note
Further information on BTM is available in the section Associated Products of the OEM 12c Cloud Control documentation page at http://docs.oracle.com/cd/E24628_01/nav/assoproducts.htm.