CI attribute mappings between IMD and BMC CMDB form

This topic describes how CI attributes present in the component, and relationship dialogs in IMD are mapped to corresponding attributes in the CMDB form.

Note

  • You can access any BMC CMDB form by modifying the classNameSpace and formClassName placeholders in the following URL:

    http://<midTierServer>:<port>/arsys/forms/<ARServer>/<classNameSpace:formClassName>

    where,

    • <midTierServer> is the name of the web server where the BMC Remedy Mid Tier is installed
    • <port> is the port number of the web server where the BMC Remedy Mid Tier is installed. The default port is 8080
    • <ARServer> is the name of the Action Request server
    • classNameSpace is the namespace of the class to which the service model component belongs
    • formClassName is the name of the class to which the service model component belongs to
    For example, if you want to access the BMC.CORE:BMC_BaseRelationship form, the URL will take the following form:
    http://<midTierServer>:<port>/arsys/forms/<ARServer>/BMC.CORE:BMC.CORE:BMC_BaseRelationship
    To access another BMC CMDB form, for example, the BMC_STATUS_PROPAGATION form, the URL will take the following form:
    http://<midTierServer>:<port>/arsys/forms/<ARServer>/BMC.SIM:BMC_STATUS_PROPAGATION

  • For BMC CMDB version 19.02 and later, you can edit the component and relationship attributes in the CMDB Explorer. For more information, see Impact Model Designer capabilities available in BMC CMDB.

  • If you directly launch the form to search or edit CIs, ensure that the DatasetId in the form is set to BMC.ASSET. If you create a CI in a different dataset, ensure to run the reconciliation job to promote the changes to the production BMC.ASSET dataset. For more information, see Running a reconciliation job. Open link
  • To view a list of out-of-the-box sim-enabled classes, see OOB sim-enabled classes. To know more about how to sim-enable a class, see Managing classes.


CI attribute mappings for the Component dialog

The following section shows the CI attribute mappings between the different tabs in the Edit Component Properties dialog in IMD and the corresponding CMDB form applicable for that tab in IMD. 

    This tab provides general details about the component such as the component name, class to which the component belongs to, cell name, publish mode, and so on. The following illustration and table shows the CI attribute mappings between the General tab of the Edit Component Properties dialog in IMD and the BMC.CORE:BMC_BaseElement form.

    Attribute_Mapping_Component_General_Tab

    Attribute in IMD Attribute in the CMDB form Description
    Short Description ShortDescription

    It indicates the component description.

    It maps to the ShortDescription attribute in the BMC.CORE:BMC_BaseElement form.

    To access a sample BMC.CORE:BMC_BaseElement form, see Accessing a sample CMDB form.

    Name Name

    It indicates the component name.

    It maps to the Name attribute in the BMC.CORE:BMC_BaseElement form.

    To access a sample BMC.CORE:BMC_BaseElement form, see Accessing a sample CMDB form.

    Class NA It indicates the class to which the component belongs to.
    Cell

    HomeCell

    HomeCellAlias

    It indicates the cell name to which the component should be published. It maps to the HomeCell and HomeCellAlias attributes present in any of the Custom tabs of the BMC.CORE:BMC_BaseElement form. The values of the HomeCell and HomeCellAlias attributes should come from the Cell Name attribute of the PN:CellAliases form.

    To access a sample BMC.CORE:BMC_BaseElement and PN:CellAliases form, see Accessing a sample CMDB form.

    Owner Name OwnerName

    It indicates the name of the owner responsible for the CI.

    It maps to the OwnerName attribute present in the General tab of the BMC.CORE:BMC_BaseElement form.

    To access a sample BMC.CORE:BMC_BaseElement form, see Accessing a sample CMDB form.

    Owner Contact OwnerContact

    It indicates the contact details of the owner responsible for the CI.

    It maps to the OwnerContact attribute present in the General tab of the BMC.CORE:BMC_BaseElement form.

    To access a sample BMC.CORE:BMC_BaseElement form, see Accessing a sample CMDB form.

    Publish To BMC ProactiveNet Performance Manager (BPPM) PublishToSIM

    It indicates the publish mode of the component. This attribute has the following values:

    Value in IMD Value in CMDB form Description
    Inherit Implicit Select this mode if you want the CI to inherit the same mode of publication that is set for the consumers of the CI. In this case, even if one of the consumers of the CI is set to Yes and Propagate publish mode, the CI is also published. The Inherit publish mode is selected by default.
    Yes and Propagate yes - myself and my providers Select this mode if you want to publish not only the CI but also all the providers of the CI to the cell.
    Yes - Only Me yes - only myself Select this mode if you want to publish only the currently selected CI to the cell.
    No no - including my providers Select this mode if you do not want to publish the CI and the providers of the CI to the cell.


    It maps to the PublishToSIM attribute present in any of the Custom tabs of the BMC.CORE:BMC_BaseElement form.

    To access a sample BMC.CORE:BMC_BaseElement form, see Accessing a sample CMDB form.

    This tab provides details about the status computation method used to calculate status of the component and the alias used for the component. The following illustration and table shows the CI attribute mappings between the Status and Alias tab of the Edit Component Properties dialog in IMD and the BMC.CORE:BMC_BaseElement form.

    Attribute_Mapping_Component_Status_Alias_Tab

    Attribute in IMD Attribute in the CMDB form Description
    Status Computation ImpactComputationModel

    It indicates the computation method used to calculate status of the component. This attribute has the following out-of-the-box values:

    • SELF_PREFERRED
    • STANDARD
    • WEIGHTED_CLUSTER
    • CLUSTER
    • STANDARD_UNKNOWN

    Note: The Status Computation attribute is case-sensitive.

    The default value is STANDARD. It maps to the ImpactComputationModel attribute present in any of the Custom tabs of the BMC.CORE:BMC_BaseElement form. The value for this attribute should come from the model_name attribute present in any of the Custom tab s of the BMC.SIM:BMC_STATUS_COMPUTATION form.

    To access a sample BMC.CORE:BMC_BaseElement and BMC.SIM:BMC_STATUS_COMPUTATION form, see Accessing a sample CMDB form.

    Aliases ComponentAliases

    It indicates the alias name used for the component. It should be stored as a semicolon separated value.

    For example: compalias1;compalias2 where compalias1 and compalias2 are the two aliases.

    It maps to ComponentAliases attribute present in any of the Custom tabs of the BMC.CORE:BMC_BaseElement form.

    To access a sample BMC.CORE:BMC_BaseElement form, see Accessing a sample CMDB form.

    This tab provides the schedule and priority details associated with the component. The following illustration and table shows the CI attribute mappings between the Schedule and Priority tab of the Edit Component Properties dialog in IMD and the BMC.CORE:BMC_BaseElement form.

    Attribute_Mapping_Component_Schedule_Priority_Tab

    Attribute in IMD Attribute in the CMDB form Description
    Schedule ScheduleId

    It indicates the schedule associated with the CI. It maps to the ScheduleId attribute present in any of the Custom tabs of the BMC.CORE:BMC_BaseElement form. The value for this attribute should come from the ReconciliationIdentity attribute present in the General tab of the BMC.SIM:BMC_TIME_SCHEDULE form.

    To access a sample BMC.SIM:BMC_TIME_SCHEDULE form, see Accessing a sample CMDB form.

    Propagate Priority to Providers PriorityWatchDog

    Set the value of this attribute to Yes if you want to allow the selected components to propagate their self-priority to their causal components.

    Set the value of this attribute to No if you do not want to allow the selected components to propagate their self-priority to their causal components. The default value is No.

    Note:

    Ensure that you select this option for at least the top-level consumer CI in your service model.

    It maps to the PriorityWatchDog attribute present in any of the Custom tabs of the BMC.CORE:BMC_BaseElement form.

    To access a sample BMC.CORE:BMC_BaseElement, see Accessing a sample CMDB form.

    Self Priority function SelfPriorityFunction

    It indicates a dynamic priority that changes based on the status of the component, schedule status associated to the component, and the method used for self priority computation. This attribute takes the following values. The default value is BASE_PRIORITY.

    • BASE_PRIORITY
    • COST
    • WORST_SLA_STATE

    It maps to the SelfPriorityFunction attribute present in any of the Custom tabs of the BMC.CORE:BMC_BaseElement form.

    To access a sample BMC.CORE:BMC_BaseElement, see Accessing a sample CMDB form.

    Base Priority High Demand Timeframes Priority

    It indicates a base priority value for a component during a high demand timeframe (In Schedule period).

    This attribute takes values from PRIORITY_1 to PRIORITY_5, where PRIORITY_1 indicates the highest priority and PRIORITY_5 indicates the lowest priority. The default value is PRIORITY_5.

    It maps to the Priority attribute present in the General tab of the BMC.CORE:BMC_BaseElement form.

    To access a sample BMC.CORE:BMC_BaseElement, see Accessing a sample CMDB form.

    Base Priority Low Demand Timeframes PriorityOut

    It indicates a base priority value for a component during a low demand timeframe (Out of Schedule period).

    This attribute takes values from PRIORITY_1 to PRIORITY_5, where PRIORITY_1 indicates the highest priority and PRIORITY_5 indicates the lowest priority. The default value is PRIORITY_5.

    It maps to the PriorityOut attribute present in any of the Custom tabs of the BMC.CORE:BMC_BaseElement form.

    To access a sample BMC.CORE:BMC_BaseElement, see Accessing a sample CMDB form.

    Cost High Demand Timeframes ImpactCostPerSec

    It indicates the cost per second associated with the CI not being available for a high demand timeframe.

    It maps to the ImpactCostPerSec attribute present in any of the Custom tabs of the BMC.CORE:BMC_BaseElement form.

    To access a sample BMC.CORE:BMC_BaseElement, see Accessing a sample CMDB form.

    Cost Low Demand Timeframes ImpactCostPerSecOut

    It indicates the cost per second associated with the CI not being available for a low demand timeframe.

    It maps to the ImpactCostPerSecOut attribute present in any of the Custom tabs of the BMC.CORE:BMC_BaseElement form.

    To access a sample BMC.CORE:BMC_BaseElement, see Accessing a sample CMDB form.

    Cost Unit ImpactCostUnit

    It indicates the currency unit of the cost.

    It maps to 


    CI attribute mappings for the Relationship dialog

    The following illustration and table shows the CI attribute mappings between the Edit Relationship dialog in IMD and the BMC.CORE:BMC_BaseRelationship CMDB form. 

    Attribute_Mapping_Relationship_tab

    Attribute in IMDAttribute in the CMDB formDescription
    Short DescriptionShortDescription

    It indicates a short description of the relationship between the CIs.

    It maps to the ShortDescription attribute in the BMC.CORE:BMC_BaseRelationship form.

    To access a sample BMC.CORE:BMC_BaseRelationship form, see Accessing a sample CMDB form.

    Relationship Type NA

    It indicates the type of relationship between the CIs. This attribute is non-editable.

    Impacting RelationshipHasImpact

    It indicates whether the relationship is impacting or not. An impacting relationship is a relationship where the provider CI impacts the consumer CI. For an impact relationship, the HasImpact attribute is set to Yes and would be considered for publishing. For a non-impact relationship, the HasImpact attribute is set to No and is not considered for publishing. It is a selection field and can takes values as either Yes or No. The default value is No.

    It maps to the HasImpact attribute present in any of the Custom tabs of the BMC.CORE:BMC_BaseRelationship form.

    To access a sample BMC.CORE:BMC_BaseRelationship form, see Accessing a sample CMDB form.

    Impact Propagation StateState

    It indicates the impact propagation state between the provider and consumer CI. It is a selection field and can take values as either Active or Inactive. The default value is Active.

    It maps to the State attribute present in any of the Custom tabs of the BMC.CORE:BMC_BaseRelationship form.

    To access a sample BMC.CORE:BMC_BaseRelationship form, see Accessing a sample CMDB form.

    Impact Propagation MethodImpactPropagationModel

    It indicates the impact propagation method between the provider and consumer CI. It is a combo box and has the following out-of-the-box values. The default value is DIRECT. For more information on impact propagation models, see Advanced service modeling.

    • INCREASING
    • DIRECT
    • DECREASING
    • JUST_WARNING
    • JUST_INFO

    It maps to the ImpactPropagationModel attribute present in any of the Custom tabs of the BMC.CORE:BMC_BaseRelationship form. The value of the this attribute should come from the name attribute present in any of the Custom tabs of the BMC.SIM:BMC_STATUS_PROPAGATION form.

    Note: The ImpactPropagationModel attribute is case-sensitive.

    To access a sample BMC.CORE:BMC_BaseRelationship and BMC.SIM:BMC_STATUS_PROPAGATION form, see Accessing a sample CMDB form.

    Impact Propagation Status WeightImpactWeight

    It indicates a numeric value which is used during status computation of the component in case of the Weighted Cluster method. To know more about the Weighted Cluster method, see Status computation algorithms and Quorum algorithm examples. Valid values for this attribute range from 1 to 100. The default value is 100.

    It maps to ImpactWeight attribute present in any of the Custom tabs of the BMC.CORE:BMC_BaseRelationship form.

    To access a sample BMC.CORE:BMC_BaseRelationship form, see Accessing a sample CMDB form.

    Reverse ImpactImpactDirection

    It is used to change the impact direction between the CIs. It is a selection field. Valid values for this attribute are either Source-Destination or Destination-Source, where Source would be the provider CI and Destination would be the consumer CI.

    Note:
    Do not select any other values for this attribute apart from the preceding mentioned valid values.

    It maps to the ImpactDirection attribute present in any of the Custom tabs of the BMC.CORE:BMC_BaseRelationship form .

    To access a sample BMC.CORE:BMC_BaseRelationship form, see Accessing a sample CMDB form.




    Was this page helpful? Yes No Submitting... Thank you

    Comments