This topic discusses BMC recommendations to be followed when creating discrete and distributed service models and details about how to set up a model for optimal performance. This topic also provides guidelines on how events must be managed in a multiple BMC ProactiveNet Server environment, so as to gain maximum business value without impacting performance.
Using the recommendations in this topic, you can create a service model in a way that presents a correct picture of your business services and also presents an accurate estimate of optimal performance.
For details about discrete and distributed service models, see the BMC ProactiveNet Service Modeling and Publishing Guide.
For reasons of scalability or modularity, there is a need to distribute different configuration items (CIs) of a service model across various BMC ProactiveNet Servers. However, at the same time, operators must be allowed to view the complete service model and its status from a single view (called the central view).
To create discrete and distributed service models, BMC recommends the same hardware and software configuration as that required by the BMC ProactiveNet Central Server and BMC ProactiveNet Child Server. For information about the configuration, see BMC ProactiveNet Server installation requirements.
You can create two types of service models:
A service model that is present entirely on a single BMC ProactiveNet Server is referred to as a discrete service model. BMC recommends that you deploy discrete service models for optimized performance and scalability. The number of CIs in a discrete service model is limited to the maximum number of CIs supported by BMC ProactiveNet version 9.0. If the number of CIs in a service model is within the limit of a single server, then the service model must be present on a single BMC ProactiveNet Server.
A service model that is distributed across two or more BMC ProactiveNet Servers is referred to as a distributed service model. When the number of CIs in a service model exceeds the maximum limit of CIs allowed for a single BMC ProactiveNet Server, then you can distribute the service model across multiple BMC ProactiveNet Servers.
When creating a distributed service model, ensure that the relationships do not criss-cross frequently across multiple BMC ProactiveNet Servers (BMC ProactiveNet Cells). Otherwise, the service model might deteriorate the performance of impact computation. For optimal performance of the BMC ProactiveNet Server, a distributed service model must cross the boundaries of impact management (BMC ProactiveNet Server Cell) minimally (ideally, only once or twice).
BMC recommends using discrete service models over distributed service models. Distributed service models must be created only in scenarios where it is not possible to have the complete service model on a single BMC ProactiveNet Server.
Example of a Distributed Service Model:
Central Server --No Cis
Child Server1 – vm-w28-rds829 – 4 Cis for Distributed Service model
Child Server2 – vw-pun-sms-qa05 – 2 Cis for Distributed Service model
It is mandatory that the metadata of the BMC ProactiveNet Cell be consistent across all the BMC ProactiveNet Servers. If you are using BMC Atrium CMDB, you can export the class definitions from BMC Atrium CMDB, using the
pclassinfo CLI command. Place the BAROC file that contains the class definitions at installationDirectory/pw/server/etc/cellName/kb/classes.
- pclassinfo -x -o mc_sm_object.baroc
For more information about
pclassinfo, see the BMC ProactiveNet Command Line Interface Reference Guide.
If the metadata of the BMC ProactiveNet Cell is not the same across all BMC ProactiveNet Servers, it might result in undetermined behavior in the BMC ProactiveNet UI. For example, not all classes may be populated in the search drop-down list, icons may not be displayed for the various CIs, and so on.
BMC recommends adhering to the following guidelines when configuring the CI settings:
Enterprise=Tin the pserver.conf file in BMC ProactiveNet Server. These two settings are mandatory to set up discrete or distributed service models.
For detailed information about these settings, see the BMC ProactiveNet Service Modeling and Publishing Guide.
This section contains BMC recommendations for setting up the environment to create discrete and distributed service models.