4 Changing Default Configurations

XML Format of HP Operations Manager Messages

Example 4–1 represents the format that the HP Operations Manager web service expects for creating new messages in HP Operations Manager. 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>
 
        <summary></summary>
 
        <urgency></urgency>
 
        <resolvedBy></resolvedBy>
 
        <identifier></identifier>
 
        <group>
          <name></name>
        </group>
 
        <object>
          <displayName></displayName>
        </object>
 
        <source>
          <computerName></computerName>
        </source>
 
        <extended-fields>
          <!-- OMU Application -->
          <string-field name="application">
            <xsl:value-of select="a:TargetType"/>
          </string-field>
          <!-- Do not add CMA data -->
          <string-field name="ovo_ts_field">NONE</string-field>
          <!-- Own the event after it is created -->
          <string-field name="own">true</string-field>
        </extended-fields>

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

The following procedure provides the steps required for changing a mapping. Following this procedure below, an example is provided to more fully illustrate the procedure.

1. Study the default mapping and determine the changes you want to make.

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 HP Operations Manager messages and Oracle Enterprise Manager alerts.

5. Save your changes.

6. Rerun the register command for the template that was modified to pick up the changes. See Section 2.5, "Registering Templates" for details.

Example of Changing a Mapping

By default, the Application field in the HP Operations Manager message is set to the Oracle Enterprise Manager target type, and no CMA fields are defined. The example procedure below shows how to change the value assigned to the Application field to a different value. The example also shows how to add a CMA field.

The changes made to the default mapping are as follows:

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

• A new CMA field named TargetType is added to contain the TargetType associated with the Oracle Enterprise Manager alert.

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

2. Make a back-up 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 Extended Fields section to reflect the new mapping.

   • Before Changes

     The code below shows the Extended Fields section in the file before the changes.

     <extended-fields>
       <!-- OMU Application -->
       <string-field name="application">
         <xsl:value-of select="a:TargetType"/>
       </string-field>
       <!-- Do not add CMA data -->
       <string-field name="ovo_ts_field">NONE</string-field>
       <!-- Own the event after it is created -->
       <string-field name="own">true</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 italics.

     <extended-fields>
       <!-- OMU Application -->
       <string-field name="application">Oracle Enterprise Manager</string-field>
       <!-- Do not add CMA data -->
       <string-field name="ovo_ts_field">NONE</string-field>
       <!-- Own the event after it is created -->
       <string-field name="own">true</string-field>
       <string-field name="TargetType">
         <xsl:value-of select="a:TargetType"/>
       </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.

8. Run the following register command for the template that was modified to enable OMS to pick up the changes:

   emctl register_template connector -t 
   $OMS_HOME/sysman/connector/HP_OMU_Connector/createEvent_request.xsl 
   -repos_pwd testPass -ctname "HP OMU Connector" -cname "HP OMU Connector" 
   -tname "Create Event Request" -iname "createEvent" -ttype 2 -d "This is the 
   request xsl file for createEvent method"
   

Changing the Agent Listener Port (9007)

9007 is the default port number used for communication between the HP Operations Manager Agent and the HP Operations Manager web service. To change this port number, perform the following steps at the HP Operations Manager server system.

Replace <OMUA_INSTALL> with the directory where the HP Operations Manager Agent is installed.

1. Open a command prompt window and change the working directory to:

   <OMUA_INSTALL>/ovo-agent/scripts
   

2. Enter the following command to stop the HP Operations Manager Agent. You will be prompted for the credentials to stop the Oracle OMU Agent.

   ./stop.sh
   

   Note:

   You must specify the user name and password for the account that is authorized to stop the Oracle OMU Agent. See Section 2.2, "Installing and Running the Oracle Agent for HP Operations Manager" for information about the account that is authorized to stop the Oracle OMU Agent.

3. Make a back-up copy of the following file:

   <OMUA_INSTALL>/ovo-agent/conf/ovooper.txt
   

4. Open the file above in a text editor.

5. Search for the line containing the ListenPort=string.

6. Change 9007 to the new port number.

7. Save the file and exit.

8. Enter the following command to start the HP Operations Manager Agent.

   ./start.sh
   

   The Oracle OMU Agent will pick up the configuration changes and use the new port number.

Perform the following steps at the system where the HP Operations Manager web services are installed. Replace <OMUWS_INSTALL> with the directory where the HP Operations Manager web service is installed.

1. Open a command prompt window and change the working directory to:

   <OMUWS_INSTALL>/adapters/conf
   

2. Make a back-up copy of the framework.properties file.

3. Open the framework.properties file in a text editor.

4. Search for the line containing the hpovou.xmlagent property. Change the port number from 9007 to the new port number.

5. Save the file and exit.

6. Restart the web service as instructed in Section 2.3.1.2, "Running the Web Service on Unix" and Section 2.3.2.3, "Running the Web Service on Windows".

Changing the Agent Shutdown Ports (9008, 9009)

The OMU Agent has two components that you must shut down whenever the Agent is stopped. The default port numbers these components use are 9008 and 9009. To change these port numbers, perform the following steps at the HP Operations Manager server system.

Replace <OMUA_INSTALL> with the directory where the HP Operations Manager Agent is installed as follows:

1. Open a command prompt window and change the working directory to:

   <OMUA_INSTALL>/ovo-agent/scripts
   

2. Enter the following command to stop the HP Operations Manager Agent. You will be prompted for the credentials to stop the Oracle OMU Agent.

   ./stop.sh
   

   You must specify the user name and password for the account that is authorized to stop the Oracle OMU Agent. See Section 2.2, "Installing and Running the Oracle Agent for HP Operations Manager" for information about the account that is authorized to stop the Oracle OMU Agent.

3. Make a back-up copy of the ovooper.txt file, then open the file in a text editor.

4. Search for the line containing the ShutdownPort= string.

5. Change the default port number from 9008 to the new port number.

6. Save the file and exit.

7. If the ovoacq.txt file exits, perform the following steps. Otherwise skip to step 8.

   1. Make a back-up copy of the ovoacq.txt file, then open the file in a text editor.

   2. Search for the line containing the ShutdownPort= string.

   3. Change the default port number from 9009 to the new port number.

   4. Save the file and exit.

8. Enter the following command to start the HP Operations Manager Agent:

   ./start.sh
   

   The Oracle OMU Agent will pick up the configuration changes and use the new port numbers.

9. Change the working directory to the scripts directory by entering the following command:

   cd ../scripts
   

10. Make a back-up of the stop.sh script file, then open the file in a text editor.

11. Change the SEND_SHUTDOWN_PORT and RCV_SHUTDOWN_PORT variables from 9008/9009 to the new port numbers.

12. Save the file and exit.

Changing the Web Service Port (8080)

The OMU web service uses port 8080 as the default port for communication when the web service is configured at installation to use HTTP (no SSL). To change the port number to a different value, perform the following steps on the system where the Oracle OMU Agent is installed.

Replace <OMUA_INSTALL> with the directory where the HP Operations Manager Agent is installed.

1. Open a command prompt window and change the working directory to:

   <OMUA_INSTALL>/ovo-agent/conf

2. Verify that the ovoacq.txt file exits. If the file exists, perform the following steps. If it does not exist, skip to the next procedure that begins with "Open a command prompt window ..."

   1. Make a back-up copy of the ovoacq.txt file, then open the file in a text editor.

   2. Search for the line containing the URL= string.

   3. Change the default port number from 8080 to the new port number.

   4. Save the file and exit.

   5. Change the working directory to the scripts directory by entering the following command:

      cd ../scripts
      

   6. Stop the Agent by entering the following command:

      ./stop.sh
      

      Note:

      You must specify the user name and password for the account that is authorized to stop the Oracle OMU Agent. See Section 2.2, "Installing and Running the Oracle Agent for HP Operations Manager" for information about the account that is authorized to stop the Oracle OMU Agent.

   7. Start the Agent by entering the following command:

      ./start.sh
      

Perform the following steps at the system where the HP Operations Manager web services are installed. Replace <OMUWS_INSTALL> with the directory where the HP OMU web services are installed.

1. Open a command prompt window and change the working directory to:

   <OMUWS_INSTALL>/adapters/conf
   

2. Make a back-up copy of the framework.properties file, then open the file with a text editor.

3. Replace all references to the old port number with the new port number, then save the file.

4. Restart the web service as instructed in Section 2.3.1.2, "Running the Web Service on Unix" and Section 2.3.2.3, "Running the Web Service on Windows".

Perform the following steps to change the URL the OMU connector is using:

1. Log in to the Oracle Enterprise Manager console by entering a user name with a 'Super Administrator' role, entering the appropriate password, then clicking Login.

2. Click the Setup link at the top right part of the window. The Overview of Setup page appears.

3. Click the Management Connectors link on the left side of the window. The Management Connectors page appears, which shows the installed connectors.

4. Click on the Configure icon associated with the HP OMU Connector. This invokes edit mode, enabling you to configure the connector.

5. Change the URLs listed in the Web Service End Points section to use the new port number.

6. Click OK to save your changes.

Changing the Web Service Port (8443)

Contact Oracle support for assistance in switching the default SSL port 8443 to a different port.