Mapping File Elements

<integration>. The root element of the XML file. This element has no attributes.

<info>. The source and target data repositories being used, for example:

<info>
<source name="Atrium"  versions="7.6" vendor="BMC" />
<target name="UCMDB" versions="9.0" vendor="HP" />
</info>

<targetcis>. The element that encapsulates the mapping for all CI types.

<targetrelations>. The element that encapsulates the mapping for all relationship types.

<source_ci_type>. The element that defines a CI type of the source data repository, for example:

<source_ci_type name="BMC_ComputerSystem" nameSpace="BMC.CORE" query="" mode="update_else_insert">

• Attribute: name. Defines the name of the source CI type.

• Attribute: namespace. Defines the namespace in the Atrium system that the CI type is associated with.

• Attribute: query. Allows applying an additional filter to the query result.

  For example, query="'DatasetId'=&quot;BMC.ASSET&quot; AND 'AssetLifecycleStatus'!=8".

• Attribute: mode. Defines the mode of the update in the target data repository. The possible values are: update, insert, and update_else_insert.

<target_ci_type>. The element that defines the target CIT, for example:

<target_ci_type name="unix">

• Attribute: name. Defines the name of the target CIT.

<targetprimarykey>. The element that defines a list of all primary keys of the target CIT, for example:

<targetprimarykey>
     <pkey>host_key</pkey>
</targetprimarykey>

<target_attribute>. The element that defines an attribute mapping from the source CI type to the target CI type attribute. Attribute mapping can be of the following types:

• Constant. This type enables setting a constant value on the target attribute:

  <target_attribute name="data_note" datatype="string" length="127">
  <map type="constant" value="ATRIUM DATA" />
  </target_attribute>

• Direct. This type enables setting a direct value of a source data repository attribute on the target data repository:

  <target_attribute name="name" datatype="string">
  <map type="direct" source_attribute="Name" />
  </target_attribute>

• Compound String. This type enables the use of the above mapping types together to form more complex values for the target attribute, for example:

  <target_attribute name="Bunch_O_Data" datatype="char" length="510" option="uppercase">
  <map type="compoundstring">
      <source_attribute name="name"/>
      <constant value="_UNIX_Server, IP="/>
      <childattr name="ip_address" source_attribute="ip_address" aggregation="csv"/>
      <constant value=", CPU="/>
      <childattr name="cpu" source_attribute="display_label" aggregation="csv"/>
  </map>
  </target_attribute>

<link>. The element that defines a relationship mapping from the source data repository to a target data repository, for example:

<link source_link_type="composition"
    target_link_type="BMC_HostedSystemComponents"
    source_ci_type_end1="unix"
    source_ci_type_end2="cpu"
    role1="Source"
    role2="Destination    "
    mode="update_else_insert">
        <target_ci_type_end1 name="BMC_ComputerSystem" 
         superclass="BMC_System" /> 
        <target_ci_type_end2 name="BMC_Processor" 
         superclass="BMC_SystemComponent" /> 
... Relationship attribute mapping elements similar to the CI type attribute mapping elements ...
</link>