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.
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.
Infrastructure Management deployment with BMC Atrium CMDB
1 Comment
John Clitheroe
Is this page (and many others that refer to a TSIM Central server) getting changed soon? I understand that the Central server is no longer valid for Infrastructure Management because it breaks the flow of policies to lower level TSIM servers.