Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Operations Manager i10.62

Develop > Populate the RTSM > Synchronization Packages > Configuring Topology Synchronization: ACME Example

Configuring Topology Synchronization: ACME Example

This section provides a walk-through of how to configure topology synchronization, using the fictitious “ACME” content area as an example.

The following graphic shows a service tree from OM discovery.

Configure type mapping file: typemapping.xml

Configure the type mapping file typemapping.xml to define the mapping between the service type definition of a service in OM and the type of a CI in the RTSM.

For the ACME example, the type mapping is defined in the following table.

OM Service Type	CI Type (CI Name)
`ACME_System`	`acme_system`
`ACME_Application_Server`	`acme_appserver`

Here is an example configuration of the type mapping file typemapping.xml for the ACME synchronization package, using the context ACME_Landscape. OM service elements of type ACME_System are mapped to CIs of type acme_system in the RTSM. OM service elements of type ACME_Application_Server are mapped to CIs of type acme_appserver in the RTSM.

<?xml version="1.0" encoding="UTF-8"?>
<Mapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../../schemas/mapping.xsd">
  <Rules Context="ACME_Landscape">
      <Rule name="Map ACME System">
          <Condition>
              <Equals>
                  <OMType />
                  <Value>ACME_System</Value> 
              </Equals>
          </Condition>
          <MapTo>
              <CMDBType>
                  <Value>acme_system</Value>
              </CMDBType>
          </MapTo>
      </Rule>
      <Rule name="Map ACME Application Server">
          <Condition>
              <Equals>
                  <OMType />
                  <Value>ACME_Application_Server</Value>
              </Equals>
          </Condition>
          <MapTo>
              <CMDBType>
                  <Value>acme_appserver</Value>
              </CMDBType>
          </MapTo>
      </Rule>
  </Rules>
</Mapping>

Configure attribute mapping file: attributemapping.xml

Configure the attribute mapping file attributemapping.xml to define the mapping between the attributes of a service in OM and the attributes of a CI in the RTSM.

For the ACME example, the following table shows which OM service attributes are mapped to which CI attributes in the RTSM.

Service Type	Service Attribute Name	CI Type	CI Attribute Name
`ACME_System`	`Caption`	`ALL`	`display_label`
`ACME_Application_Server`	`OMId`	`ALL`	`data_name`

Here is an excerpt of the corresponding configuration of the attribute mapping file attributemapping.xml for the ACME synchronization package. This shows two attribute mappings:

For the OM service elements of type ACME_system, the OM service attribute Caption is mapped to the CI attribute display_label in the RTSM.
For the OM service elements of type ACME_Application_Server, the OM service attribute OMId is mapped to the CI attribute data_name in the RTSM.

<?xml version="1.0" encoding="UTF-8"?>
<Mapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../../schemas/mapping.xsd">
  <Rules Context="ACME_Landscape">
      <Rule name="Map ACME System attributes">
          <Condition>
              <Equals>
                  <OMType />
                  <Value>ACME_System</Value>
              </Equals>
          </Condition>
          <MapTo>
              <CMDBAttribute>
                  <Name>display_label</Name>
                  <SetValue>
                      <Caption />
                  </SetValue>
              </CMDBAttribute>
          </MapTo>
      </Rule>
      <Rule name="Map ACME Application Server attributes">
          <Condition>
              <Equals>
                  <OMType />
                  <Value>ACME_Application_Server</Value>
              </Equals>
          </Condition>
          <MapTo>
              <CMDBAttribute>
                  <Name>data_name</Name>
                  <SetValue>
                      <OMId />
                  </SetValue>
              </CMDBAttribute>
          </MapTo>
      </Rule>
  </Rules>
</Mapping>

Configure relation mapping file: relationmapping.xml

Configure the relation mapping file relationmapping.xml to define the CI relationships created in the RTSM between specified OM services.

Here is an example configuration of the relation mapping file relationmapping.xml for the ACME synchronization package. This shows the creation of the following relations:

The root_container CI attribute of CIs with the OM service type ACME_Application_Server is set to the host. Additionally, a container_f relation is created implicitly between the host and the CI.
A composition relation container_f between OM service elements of type ACME_System and ACME_Application_Server.

<?xml version="1.0" encoding="UTF-8"?>
<Mapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:noNamespaceSchemaLocation="../../../schemas/mapping.xsd">
  <Rules Context="ACME_Landscape">
      <Rule name="Create relation ACME Application Server to node">
          <Condition>
              <StartsWith>
                  <OMType />
                  <Value>ACME_Application_Server</Value>
              </StartsWith>
          </Condition>
          <MapTo>
              <RootContainer>
                  <DependencyCI relationType="hosted_on">
                      <True />
                  </DependencyCI>
              </RootContainer>
          </MapTo>
      </Rule>	
      <Rule name="Create relation between ACME Application Server and ACME System">
          <Condition>
              <And>
                  <Equals>
                      <OMType />
                      <Value>ACME_Application_Server</Value>
                  </Equals>
                  <Equals>
                      <AncestorCI relationType="container_f">
                          <Equals>
                              <OMType/>
                              <Value>ACME_System</Value>
                          </Equals>
                      </AncestorCI>
                        <ParentCI/>
                  </Equals>
              </And>
          </Condition>
          <MapTo>
              <RelationFrom> 
                  <From>
                    <AncestorCI relationType="container_f">
                          <Equals>
                              <OMType/>
                              <Value>ACME_System</Value>
                          </Equals>
                      </AncestorCI>
                  </From>
                  <Type>member</Type>
              </RelationFrom>
          </MapTo>
      </Rule>
  </Rules>
</Mapping>

Send Help Center feedback