Precedence

Data published from BMC Atrium CMDB automatically overwrites Direct Feed data. Between Direct Publish and Direct Feed data, Direct Publish data has a higher precedence and hence overwrites Direct Feed data. Events that are attached to lower precedence CIs are automatically reattached to overwriting CIs of higher precedence.

Data overrides other data with a lower precedence if it meets one of the following conditions:

• When it has the same key slots
• In the case of a MC_SM_COMPONENT, when it has the same alias

Different system sources like pposter, BMC Performance Manager, and BMC Atrium CMDB must not create data with the same mc_udid.

Overriding rules

When data X, for example, has precedence pX with key slot values that collide with existing data Y with precedence pY, such that pY < pX, then Y is deleted; otherwise, the addition of X fails.

These key slot collision rules apply to Infrastructure Management data and relationships. (The keys of a relationships are the provider_id and consumer_id.) Do not modify key slots.

Data modification or deletion is allowed only when the publish environment ID of the requester matches the publish_env_id of the data. In addition to these rules, other operations are performed when overriding, modifying, or deleting CIs to ensure the uniqueness of each alias and to avoid (local) relationships with dangling ends.