4 Changing Default Configurations

XML Format of IBM TEC Events

Example 4–1 represents the format that the IBM TEC web service expects for creating new events in IBM TEC. The format for update requests is the same, except the root node would be "update" instead of "create."

<iwaveaf:create xmlns:iwaveaf="http://iwavesoftware.com/services/  adapter-framework">
  <event>
    <description></description>
    <status></status>
    <severity></severity>
    <repeatCount></repeatCount>
    <createDate></createDate>
    <eventClass>
      <name>OracleEnterpriseManager</name>
    </eventClass>
    <group>
      <name>PrimaryServer</name>
    </group>
    <object>
      <computerName></computerName>
      <displayName></displayName>
    </object>
    <source>
      <computerName></computerName>
      <name>OracleEnterpriseManager</name>
    </source>
    <extended-fields>
      <string-field name="ext_id"></string-field>
      <string-field name="sub_source">OracleEnterpriseManager</string-field>
    </extended-fields>
  </event>
</iwaveaf:create>

XML Format of Oracle Enterprise Manager Alerts

Example 4–2 shows the format that the Oracle Enterprise Manager Connector Framework provides when an alert is created or updated in Oracle Enterprise Manager.

<EMEvent>
  <EventGuid/>
  <ExternalEventId/>
  <ViolationId/>
  <TargetType/>
  <TargetName/>
  <MetricName/>
  <MetricColumn/>
  <KeyValues/>
  <Message/>
  <Severity/>
  <SeverityCode/>
  <CollectionTime/>
  <EventPageURL/>
  <EMUser/>
  <NotificationRuleName/>
  <TargetHost/>
  <TargetTimezone/>
  <Property>
    <Name/>
    <Value/>
  </Property>
</EMEvent>

Table 4–2 provides a description of the fields shown in Example 4–2.

Changing a Mapping

This section explains how to customize the mapping between Enterprise Manager and the IBM TEC web service. The procedure provides the steps required for changing a mapping. Following this procedure, an example is provided that shows how to change the mapping of the target type and target name fields.

1. Study the default mapping and determine the changes you want to make. See Appendix A for details about the default mappings and the files that define the mapping for the different Enterprise Manager operations.

2. Create a back-up copy of the XSL file you want to change.

3. Open the XSL file in a text editor or in an XSLT editor.

4. Change the file to map the fields as determined in step 1. You might need to study the information in Section 4.1.1 and Section 4.1.2. These sections describe the data formats of the IBM TEC events and Oracle Enterprise Manager alerts.

5. Save your changes.

The files are now ready for integration. You do not need to stop and start OMS. The changes will automatically be picked up.

Example of Changing a Mapping

By default, the origin slot in the IBM TEC event is set to the Oracle Enterprise Manager target type, and the sub_origin slot is set to the target name. The following example shows how to change the value where the target type and name information is placed in TEC. In this example, the target_type and target_name slots were added to the class definition to contain this information.

The changes made to the default mapping are as follows:

• The origin slot is modified to use a hard-coded value of Oracle Enterprise Manager.

• The sub_origin slot is not set to any value.

• The new target_type slot is set to the Oracle Enterprise Manager target type.

• The new target_name slot is set to the Oracle Enterprise Manager target name.

1. Make a back-up copy of the createEvent_request.xsl file and name it default_createEvent_request.xsl.

2. Make a backup copy of the updateEvent_request.xsl file and name it default_updateEvent_request.xsl.

3. Open the createEvent_request.xsl file in your text editor.

4. Change the appropriate sections to reflect the new mapping.

   • Before Changes

     The code below shows the impacted sections in the file before the changes.

     <source>  <!-- TEC slot = source -->  <name>OracleEnterpriseManager</name>  <!-- TEC slot = origin -->  <computerName>    <xsl:value-of select="a:TargetType"/>  </computerName></source>…<extended-fields>  <!-- TEC fields that are not mapped to the common object model -->  <string-field name="action_flag">CREATE</string-field>  <string-field name="ext_id">    <xsl:value-of select="a:EventGuid"/>  </string-field>  <string-field name="sub_source">OracleEnterpriseManager</string-field>  <string-field name="sub_origin">    <xsl:value-of select="a:TargetName"/>  </string-field></extended-fields>
     

   • After Changes

     The code below shows the Extended Fields section in the file after the changes. The changes are shown in bold.

     <source>
       <!-- TEC slot = source -->
       <name>OracleEnterpriseManager</name>
       <!-- TEC slot = origin -->
       <computerName>Oracle Enterprise Manager</computerName>
     </source>
     …
     <extended-fields>
       <!-- TEC fields that are not mapped to the common object model -->
       <string-field name="action_flag">CREATE</string-field>
       <string-field name="ext_id">
         <xsl:value-of select="a:EventGuid"/>
       </string-field>
       <string-field name="sub_source">OracleEnterpriseManager</string-field>
       <string-field name="target_type">
         <xsl:value-of select="a:TargetType"/>
       </string-field>
       <string-field name="target_name">
         <xsl:value-of select="a:TargetName"/>
       </string-field>
     </extended-fields>
     

5. Save your changes after making the updates.

6. Open the updateEvent_request.xsl file and make the same changes. In this case, you cannot just cut and paste the Extended Fields section, because there are some differences between the create and update translations. You will need to edit them separately.

7. Save your changes after making the updates.