Sources of service model objects

The cell can receive service model objects (components and relationships) from several sources as follows:

BMC Atrium CMDB by using BMC Impact Model Designer
ADDM after synching with BMC Atrium CMDB by using BMC Impact Model Designer
administration console
pposter and mposter CLI commands
Master Rule Language (MRL)
Third-party repository

Data that you send from any given environment must be updated and deleted in the context of that environment. You can determine the source of a selected or specified service model object in the cell in one of the following ways:

administration console–On the Services Editor tab, select a component and click the General subtab. The source of the object is displayed by the Master Repository property.
mquery command–The command returns the publish_env_id slot with the slot value PublishOriginID. PublishEnvID, where PublishOriginID is the source of the object (for example AtriumCMDB.PROD ).

The source of the service model data determines the method of delivery into the cell, as described in the following table.

How service model objects get to a cell

Source for service model objects	How objects are delivered to a cell	Delivery method name
BMC Atrium CMDB	Objects are discovered by using discovery tools, or you can create them by using BMC Impact Model Designer; they are reconciled by the BMC Atrium CMDB Reconciliation Engine and then automatically published to the cell by using the publishing server. For more information about the publishing server, see Publishing Server architecture.	Atrium Publish Feed
BAROC source file	You can create a BAROC source file of object data and send it to the cell by using the `pposter` CLI command, which publishes the data to the cell by using the publishing server. For more information about the publishing server, see Publishing Server architecture.	Direct Publish Feed
BAROC source file	You can create a BAROC source file of object data and send it to the cell by using the `mposter` CLI command.	sourceDirect Feed
MRL rule	You can create a rule that adds objects to the cell on receipt of a trigger event.	tooldirect feed
administration console	You can create service models by using the Administration Console of Infrastructure Management.	sourcedirect feed

The following table describes some of the advantages and disadvantages of the different sources for service model data.

Advantages and disadvantages of different object sources

Object source	Advantages	Disadvantages
BMC Atrium CMDB	Handles large, complex service models Accepts objects from discovery tools Sophisticated GUI to create, edit, and delete objects, and dynamic prioritization Data is protected from uncontrolled edits Customizable permissions are available	Complex to implement Time factor to discover or create, reconcile, and publish objects
BAROC file with the`pposter` CLI command	Easy to set up a simple service model quickly Managed by the publishing server, so data is protected from uncontrolled edits	Useful only for small, simple models BAROC file must be created to exact standards Requires knowledge of CLIs
MRL rule	Handles highly dynamic changes	Only practical for special circumstances Might not build complete model No primary copy in external data store
administration console	Validation of the service model is offloaded from the cell, preventing cell processing performance degradation

Sources of service model objects

Comments