Centralized Service Model
Infrastructure Management monitors multiple components (configuration items) that comprise parts of a service model. Infrastructure Management also displays the status of the configuration items (CIs) and identifies the root cause of the service being impacted. In environments that use large service models, the need arises to distribute different components of the model across various Infrastructure Management Servers but at the same time also allow operators to view the complete model and its status from a single user interface (Central Console).
Service models that enable users to have, from the Central Server Console, a centralized view of the models present on different child servers are called centralized service models. The aggregated view presented by centralized service models is as shown in the following diagram:
- A single service model physically located on multiple Infrastructure Management Servers (Child Servers)
- Multiple service models physically located on different Child Servers and depicting unrelated services
The above architecture diagram represents a centralized service model. The service model is defined in Infrastructure Management server 4. The Infrastructure Management servers 1,2, and 3 will send the events associated with any of the CIs that are part of the service model defined in Infrastructure Management Server 4. Infrastructure Management servers 1,2,3, and 5 push the events to the Presentation Server. The Infrastructure Management server 4 sends the service model to the TrueSight Presentation Server. Infrastructure Management Server 4 doesn't send the events to the TrueSight Presentation Server.
You can view the service model both in the Infrastructure Management server 4, and in the TrueSight console in the Presentation Server.
- In the TrueSight Presentation Server, you can see the impacted CIs of the service model, but cannot view the associated events. To view the event details, cross launch from the TrueSight console to the Infrastructure Management server operator console.
- The Infrastructure Management Server 4 operates optimally if its event count doesn't exceed 350K per day in a large environment.