A Customizing Microsoft SCOM

XML Format of Microsoft SCOM Alerts

Example A–1 represents the format that the Microsoft SCOM web service expects for creating new alerts in Microsoft SCOM. Example A–2 represents the format that the Microsoft SCOM web service expects for updating alerts in Microsoft SCOM.

<iwaveaf:create xmlns:iwaveaf="http://iwavesoftware.com/services/   adapter-framework">
  <event>
    <summary></summary>
    <description></description>
    <severity></severity>
    <priority></priority>
    <extended-fields>
      <string-field name="CustomField1"></string-field>
      ...
      <string-field name="CustomField10"></string-field>
    </extended-fields>
  </event>
</iwaveaf:create>

<iwaveaf:update xmlns:iwaveaf="http://iwavesoftware.com/services/ adapter-framework">
  <event>
    <identifier></identifier>
    <status></status>
    <extended-fields>
      <string-field name="AlertHistory"></string-field>
      <string-field name="CustomField1"></string-field>
      …
      <string-field name="CustomField10"></string-field>
    </extended-fields>
  </event>
</iwaveaf:update>

Changing Default Port Numbers

In most cases, you can use the default port numbers that the Microsoft SCOM web service uses. However, if there are any conflicts with existing applications, you need to change the port numbers.

8080 is the default port number for HTTP communication, and 8443 is the default port for HTTPS communication. To change the port number, perform the steps in the appropriate subsection.

Changing the Default Custom Field

The SCOM Agent requires that a custom field be set aside for its exclusive use. By default, alerts that the SCOM Agent creates will have custom field 10 set to the Guid of the event that triggered the alert. If this presents a problem, perform the following steps to change the SCOM Agent to use a different custom field.

1. Change the OracleEnterpriseManager.Alert.Creator.xml management pack file to place the event Guid in a different custom field:

   1. On the system where the SCOM Agent is installed, navigate to the directory where the OracleEnterpriseManager.Alert.Creator.xml file is located.

   2. Open the file with a text editor and search for Custom10. You should find the following line in the file:

      <Custom10>$Data/EventOriginId$</Custom10>
      

   3. Change “$Data/EventOriginId$” to “$Data/Params/Param[20]$”.

   4. Locate the tag for the custom field that the SCOM Agent will use, and change the contents to “$Data/EventOriginId$”.

   5. Save the file and exit the editor.

2. Import the updated management pack into SCOM as described in Section 2.4.4, "Installing the Alert Creator Management Pack".

3. Change the SCOM Web Service configuration to search for the event Guid in a different custom field:

   1. On the system where the SCOM Web Service is installed, navigate to the adapters/conf directory in the SCOM Web Service installation directory.

   2. Open the framework.properties file with a text editor and search for the scom2007.connector.response.query property.

   3. Change CustomField10 in the search string to the custom field number the management pack is setting.

   4. Save the file and exit the editor.

4. Stop and start the SCOM Web Service.

   Refer to the appropriate section in Chapter 2 based on the platform where the SCOM Web Service is installed. For Unix platforms, see Running the Web Service on Unix. For Windows platforms, see Running the Web Service on Windows.

Changing SCOM API Connection Parameters

When installing the SCOM Agent, you must configure the connection parameters used for accessing the SCOM API. The installation includes the SCOMAgentConfig utility you can use to change the Agent configuration parameters.

Perform the following steps to change the connection parameters:

1. Open Windows Explorer on the system where the SCOM Agent is installed.

2. Navigate to the bin directory in the SCOM Agent installation directory.

3. Run the SCOMAgentConfig.exe utility. This action starts the SCOM Agent Configuration Tool.

4. Click Load. This action opens a directory navigation window.

5. Navigate to the SCOM Agent installation directory and open the SCOMAgent.cfg file.

6. Click the Management Groups tab and click Edit. This action displays the Edit Management Group window.

7. Change the desired information in the following fields listed, then click Update:

   Name Server Domain Username Password

8. Click Save to save the changes to the configuration file.

9. Click Exit to exit the utility.

10. Stop and restart the SCOM Agent in IIS.