Testing and Troubleshooting

The schema files are stored in the following directory:

<OMi_HOME>/conf/opr/topology-sync/schemas

The files are:

package.xsd

Validates the package.xml file in each synchronization package.

containmentrelations.xsd

Validates the containmentrelations.xml file.

datadump.xsd

Validates synchronization data files that are created through enabling data dumps or used as input for the enrichment simulator.

mapping.xsd

Validates the following mapping files contained in the synchronization packages:

• Context mapping - contextmapping.xml

• Type mapping - typemapping.xml

• Attribute mapping - attributemapping.xml

• Relation mapping - relationmapping.xml

nodetypes.xsd

Validates the node type mapping file nodetypes.xml file in each synchronization package.

Each configuration file is automatically validated against the associated XSD file whenever it is read. If a file cannot be validated, an error message is written to the error log that describes the location of the error in the validated file.

With a modern XML editor, you can validate a file against a schema. Eclipse, for example, can validate an XML file against a schema, if the top level element of the document contains a reference to an XSD file. To enable validation, add the following attributes to the top level element of an XML file:

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="<path or URL to schema file>"

Replace <path or URL to schema file> with the respective path or URL to the schema file against which you want to validate. For example, for a contextmapping.xml file, add the following:

<?xml version="1.0" encoding="UTF-8"?>
<Mapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:noNamespaceSchemaLocation="<OMi_Home>/conf/opr/topology-sync/schemas/mapping.xsd">
...
</Mapping>  

A synchronization data dump contains the synchronized topology data in XML files using the data format as exposed to the XPath Expression matching in the mapping rules.

There are two separate dumps:

• The first is recorded following CI data normalization.

• The second is recorded following the processing of the mapping rules.

To activate the creation of synchronization data dumps:

1. Navigate to the OM Topology Synchronization settings in the Infrastructure Settings Manager:

   Administration > Setup and Maintenance > Infrastructure Settings

   Alternatively, click Infrastructure Settings.

   Operations Management - HPOM Topology Synchronization Settings > Dump data

2. Change the value of Dump data to true.

3. Start the topology synchronization in OM with the following command:

   • OM for Windows. Start the synchronization of topology data:

     1. In the console tree, select Tools > HP Operations Manager Tools.

     2. Right-click Synchronize Topology and select All Tasks > Launch Tool....

        The startInitialSync.bat tool is started and begins to send all the topology data to the target management servers.

   • OM for UNIX or Linux. Type the following command to start the synchronization of topology data:

     /opt/OV/bin/OpC/startInitialSync.sh

Here is an example extract from a data dump after mapping has been performed:

<CI>
  <OMId>Root</OMId>
  <OMType />
  <Caption>Root</Caption>
  <Node>false</Node>
  <Service>false</Service>
  <OMAttributes />
  <CMDBId />
  <CMDBAttributes />
  <CMDBType />
  <RootContainerId />
  <Children>
    <RelationType>container_f</RelationType>
    <CI>
      <Context>operations-agent</Context>
      <OMId>03a2f7b2-ec88-7539-0532-c5b07da188dd</OMId>
      <OMType>agent</OMType>
      <Caption>Operations-agent on met</Caption>
      <Node>false</Node>
      <Service>false</Service>
      <OMAttributes>
        <AgentId>03a2f7b2-ec88-7539-0532-c5b07da188dd</AgentId>
        <Name>met.example.example.com</Name>
      </OMAttributes>
      <CMDBType>hp_operations_agent</CMDBType>
      <RootContainerId>{8BB8864B-CEC9-4B26-BD4C-41F2C97C108E}</RootContainerId>
      <Dependencies>
        <RelationType>hosted_on</RelationType>
        <CI>
          <Context>VISPI</Context>
          <Context>nodegroups</Context>
          <OMId>{8BB8864B-CEC9-4B26-BD4C-41F2C97C108E}</OMId>
          <OMType>node</OMType>
          <Caption>met</Caption>
          <Node>true</Node>
          <Service>false</Service>
          <NodeGroupList>
            <NodeGroupID>OpenView_Windows2000</NodeGroupID>
            <NodeGroupID>Root_Nodes</NodeGroupID>
          </NodeGroupList>
          <MACAddressList />
          <OMAttributes>
            <AgentId>03a2f7b2-ec88-7539-0532-c5b07da188dd</AgentId>
            <CommType>HTTPS</CommType>
            <DiscoveryDomain>${DefaultDomain}</DiscoveryDomain>
            <Domain>example.example.com</Domain>
            <Name>met.example.example.com</Name>
            <OSType>Windows_32</OSType>
            <OSVersion>2000 (5.0)</OSVersion>
            <SystemType>x86/x64 Compatible</SystemType>
            <VirtualNodeType>0</VirtualNodeType>
          </OMAttributes>
          <CMDBId />
          <CMDBType>nt</CMDBType>
          <RootContainerId />
        </CI>
      </Dependencies>
    </CI>
  </Children>
</CI>

To view synchronization data dumps, navigate to the directory:

<OMi_HOME>/opr/tmp/datadump

The directory contains the following subdirectories:

• pre-enrichment

  Contains the synchronization data after the CI data structure has been normalized. The data reflects what has been loaded from OM to the RTSM.

• post-enrichment

  Contains the synchronization data after the mapping rules have been executed on the normalized data.

• ws-data

  Contains raw data which was read from the OM web service. For each OM node, node group, and service, there is an XML file called Caption_OMId.xml.

  Only in the case where writing to the RTSM failed, the XML file is written to the post-ucmbd directory.

To validate mapping rules, complete the following steps:

1. Compare file differences.

   Using a file comparison tool of your choice you can easily see what has been changed during enrichment.

2. Validate XPath expressions.

   You can validate XPath Expressions that are used in mapping rules by loading the normalized synchronization data dumps into an XML editor that supports XPath queries.

   Note An XML document must have a single root element (<ci>) in the data dumps. When running XPath queries in the mapping rules, this root element does not exist. For testing with dump files, when you create absolute expressions, prepend the expression /ci to your test expression.