Trading Business Service Example
Figure 1 shows the summary of a recorded and defined Trading Business Service. This summary view is the default view within CA APM and designed for a Level 1 Application Triager. The user does not know much about Java, EJBs, MQ or web services, and how to hide the smallest building blocks (Software Components) away from the user. While hidden, Software Components are crucial to the actual creation of the diagram; are used to generate the dependencies and then zoomed out one level up.
apmdevops106
From 10.7 SP3 and later, Trading Business Service is no longer available in CA APM. This page is for reference purposes only.
Figure 1 shows the summary of a recorded and defined Trading Business Service. This summary view is the default view within CA APM and designed for a Level 1 Application Triager. The user does not know much about Java, EJBs, MQ or web services, and how to hide the smallest building blocks (Software Components) away from the user. While hidden, Software Components are crucial to the actual creation of the diagram; are used to generate the dependencies and then zoomed out one level up.
Figure 1. Trading Business Service Summary
In the figure 1, you can see all available Business Transactions that belong to the Trading Business Service: Balances, Transaction Summary, Login, Options Trading, and Place Order. In addition, you can see several Applications: Reporting Service, Authentication Service, Trade Service, Order Engine, Reporting Engine and Authentication Engine internally are named as “Frontends”.
The figure also displays several “Backend” systems: They are various systems that cannot have an agent on them, but detect them and help the Triager to make informed choices. CA APM also detects several database instances.
All these backend systems are represented as Software Components of various types (Database and web service). The Business Service: Customer Records, Order Records, and Report Records use three different database instances.
In this particular case you can see the red dot on top of Authentication Engine. The dot indicates a detected problem which can be either an alert or performance degradation. The Triager passes this problem to the Level 2 Application Support person responsible for the Authentication Engine.