Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Distributed service model

A service model that is distributed across two or more Infrastructure Management Servers is called a distributed service model. When the number of CIs in a service model exceeds the maximum limit of CIs allowed in a single server, it is possible to distribute the model across multiple Infrastructure Management Servers. When creating a distributed service model, relationships must not span back and forth frequently across multiple servers (cells). An inappropriate model might deteriorate the performance of Infrastructure Management. The number of relationships spanning across multiple Infrastructure Management Servers must be kept to a minimum. A model must be present completely on a single Infrastructure Management Server as much as possible. For information about sizing the Infrastructure Management environment, see Sizing-charts-and-guidelines-for-event-and-impact-management.

Best practice

BMC recommends using a discrete model over a distributed service model. Distributed service models must be created only in scenarios where it is not possible to have the complete service model on a single Infrastructure Management Server.

Infrastructure Management Server with a single service impact management cell

  • Each Infrastructure Management Server hosts parts of the service model or distinct service models.

  • The impact management cells communicate with one another.

  • Service models on the Infrastructure Management Servers display CIs from one Infrastructure Management Server.

  • The Central Server displays all CIs across Infrastructure Management Servers.

Multiple Infrastructure Management Servers with service impact management cells

  • The Central Server hosts the service model(s) with CIs physically residing on the Infrastructure Management Servers.

  • The Infrastructure Management Servers are linked with the Central Server through Infrastructure Management Web Services. For information on how to configure a Central Server, see Configuring-a-Central-Server.

distributed_service_model.png

Cross-launching to the Infrastructure Management Server and viewing the details in the Notebook pane

From the Events view or the Graph view in the operator console, you can cross launch to a Child Server from the distributed service model as shown in the following figure. For information about cross-launching, see Use-cases-for-centralized-service-models.

cross_launch_distributed_service_model.png

The Notebook pane seamlessly displays details of the remote CIs. The Related CIs pane allows you to identity causal CIs and launch to the respective Infrastructure Management Server.

related_cis.png

Related topics

Infrastructure-Management-deployment-with-BMC-Atrium-CMDB

Creating-discrete-and-distributed-service-models

Use-cases-for-centralized-service-models

 

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