Logical high-level application model
Complex software is often hierarchical in nature. For example, a web application may be composed of a database, a web server, and an application server. Although the BMC_SoftwareServer class is used to model the lowest level components of such applications, other classes exist to model the higher level parts. These classes are:
BMC_ApplicationBMC_ApplicationSystemBMC_ApplicationService
High-level application structure
A BMC_Application CI represents a high-level application that is important to the business. For example, a BMC_Application CI might represent the holiday bookings web application that is used internally in a business. The application is made up of a database and a web server, which are modeled as BMC_SoftwareServers. Software servers composing an application need not be modeled if it is not required for your environment.
Multi-level application structure
If more than two levels (BMC_SoftwareServer and BMC_Application) are needed, further levels of an application's structure are modeled by the BMC_ApplicationSystem class.
BMC_ApplicationSystem models parts of an application that are at a higher level than the BMC_SoftwareServer class, but lower level than the BMC_Application class.
The following diagram shows a multi-level application structure. Applications, such as Remedy Service Desk and Remedy Change are recognizable to users in business. Therefore, they belong to the BMC_Applications class. The applications are developed on top of the AR Server. The AR Server, in turn, relies on lower level components and is modeled as a BMC_ApplicationSystem. The lowest level components, modeled as BMC_SoftwareServers, are the BMC Remedy AR System Server and BMC Remedy AR System Mid Tier.
Software components running in an application server
The BMC_ApplicationService class is used to represent software components running in an application server. For example, a J2EE application is represented as an instance of BMC_ApplicationService class and not BMC_Application class.
The following diagram shows two J2EE WAR modules running on an Apache Tomcat application server.
The application server itself is modeled as a BMC_SoftwareServer.
An application represented by a BMC_Application CI can contain one or more application services. For example, in the following diagram, a claims application is represented that contains two application services.
Comments
In the last diagram the relationship between BMC_APPLICATION and BMC_APPLICATIONSERVICE is presented with a red arrow, which is representing a dependency relationship. The name of the relationship is presented as "APPLICATIONSYSTEMSERVICES". Are you sure that this is correct?
In our production environment the CIs and relationships provided by BMC Discovery are different. The relationship name is "APPLICATIONSYSTEMHIERARCHY" and the relationship class id is "BMC.CORE:BMC_COMPONENT" which should result in a green arrow from BMC_APPLICATION (source) to BMC_APPLICATIONSERVICE (destination), not a red one.
The "APPLICATIONSYSTEMSERVICES" is only used between BMC_SOFTWARESERVER (source) and BMC_APPLICATIONSERVICE (destination), where the class id is "BMC.CORE:BMC_APPLICATIONSYSTEMSER", which is correct in the diagram.
BTW: This is also a sub class of the component relationship class, but the impact is from source to destination, which is absolutely correct in this case. In most other cases the direction of the component relationship is the opposite direction of the impact.
Hello Thomas,
Thanks for your comment. This diagram has been corrected.
Regards,
Kanchana
Log in or register to comment.