Parameter mapping feature of the BMC Atrium CMDB adapter

The BMC Atrium Orchestrator adapter for BMC Atrium CMDB provides a parameter-mapping feature for enum value and time value data types for the following classes:

CI classes with mapped parameters

BMC_Document

  • BMC_Equipment
  • BMC_Person
  • BMC_ProtocolEndpoint
  • BMC_ConnectivityCollection
  • BMC_Organization
  • BMC_Role
  • BMC_UserCommunity
  • BMC_Account
  • BMC_Activity
  • BMC_BusinessService
  • BMC_DataBase
  • BMC_PhysicalLocation
  • BMC_AdminDomain
  • BMC_ApplicationSystem
  • BMC_Cluster
  • BMC_ComputerSystem
  • BMC_HardwareSystemComponent
  • BMC_LogicalSystemComponent
  • BMC_ApplicationService

Relationship classes with mapped parameters

BMC_Component

  • BMC_Dependency
  • BMC_MemberofCollection
  • BMC_ElementLocation

With this mapping feature, users provide values as displayed through the user interface (UI) in BMC Atrium CMDB, rather than the actual numeric values held in the database. parameter values are mapped by the adapter as needed, to translate between the UI value and the database value.

Users can also interface with classes for which the mapped parameter feature is not available. When executing requests against these classes, the numeric database value must be used.

Examples of values to be used with both mapped and unmapped classes are provided for each data type, enum value and time value, in the following sections.

Enum Value parameter mapping

Values with a data type of 'enum value' are displayed as text in the UI but are stored as numeric values in the database. For example, the value on screen can be 'High' or 'Low' while the value in the data record is '10' or '20'. The following samples show how the values would be used for a class with mapped parameters and for a class for which the mapped parameters feature is not available.

The following figure shows the value for Confidentiality field for class with parameter mapping.

Value for Confidentiality field for class with parameter mapping

 <element>
  <name>Confidentiality</name>
  <value>
<enum-value>High</enum-value>
  </value>
</element>


The following figure shows the value for Confidentiality field for class without parameter mapping

Value for Confidentiality field for class without parameter mapping

Time Value parameter mapping

Values with a data type of time value are displayed in a standard date/time format in the UI but are stored as numeric values, in epoch time format, in the database. For example, the value on screen can be '03/30/2007 02:58:46 PM' while the value in the data record is '1175246926000'. The following samples show how the values would be used for a class with mapped parameters and for a class for which the mapped parameters feature is not available.

The following figure shows the value for Create Date field for class with parameter mapping.

Value for Create Date field for class with parameter mapping

 <element>
  <name>CreateDate</name>
  <value>
<time-value>03/30/2007 02:58:46 PM</time-value>
  </value>
</element>


The following figure shows the value for Create Date field for class without parameter mapping.

Value for Create Date field for class without parameter mapping

 <element>
  <name>CreateDate</name>
  <value>
<time-value>1175246926000</time-value>
  </value>
</element>


<element>
  <name>Confidentiality</name>
  <value>
<enum-value>10</enum-value>
  </value>
</element>

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

Comments