Skip Headers
Oracle® Enterprise Manager Installation and Configuration Guide for Microsoft Systems Center Operations Manager Connector
Release 1.0.5.2.0

E14736-08
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

3 Configuring the Connector

This chapter provides procedures to configure the two sub-pages of the main Configure Management Connector page, then explains how to perform other tasks to complete the configuration process.

This chapter discusses the following topics:

Configuring the General Page

To configure the General page:

  1. From the Management Connectors page, select the SCOM Connector and click the Configure icon. By default, the General sub-page of the Configure Management Connector page appears, as shown in Figure 3–1.

    Figure 3-1 SCOM Connector General Settings

    Shows Configure Management Connector page with example input
  2. Update the URLs for each of the Web Service End Point operations as described below.

    Operation Descriptions

    The SCOM connector uses the following operations (web methods) to exchange data with the SCOM Web Service.

    • getNewAlerts — Creates alerts in Oracle Enterprise Manager based on alerts that originate in Microsoft SCOM. Oracle Enterprise Manager uses this operation when polling for alerts in Microsoft SCOM.

    • getUpdatedAlerts — Updates alerts in Oracle Enterprise Manager based on alerts that originate from Microsoft SCOM. Oracle Enterprise Manager uses this operation when polling for alerts from Microsoft SCOM.

    • acknowledgeAlerts — Acknowledges the alerts after Oracle Enterprise Manager has processed them. Oracle Enterprise Manager uses this operation when polling for alerts in Microsoft SCOM.

    • createAlert — Generates alerts in Microsoft SCOM based on alerts that originate in Oracle Enterprise Manager. Oracle Enterprise Manager invokes this operation when it forwards a new alert to SCOM.

    • updateAlert — Updates alerts in Microsoft SCOM based on alerts that originate in Oracle Enterprise Manager. Oracle Enterprise Manager invokes this operation when it forwards an updated alert to SCOM.

    • setup — Registers the SCOM Agent with the SCOM RMS. This causes the SCOM Agent to appear as a product connector at the SCOM console. Oracle Enterprise Manager invokes this operation when the connector is configured.

    • cleanup — Deregisters the SCOM Agent from the SCOM server. This causes the SCOM Agent to no longer appear as a product connector at the SCOM console. Oracle Enterprise Manager invokes this operation when the connector is deleted.

    URL Types

    The connector uses three different URLs for operations. One URL polls data out of Microsoft SCOM (getNewAlerts, getUpdatedAlerts and acknowledgeAlerts), and defaults to the following value:

        http://[Hostname]:8080/services/AcquisitionService
    

    Another URL pushes data into Microsoft SCOM (createAlert and updateAlert), and defaults to the following value:

        http://[Hostname]:8080/services/SCOM2007/EventService
    

    This URL is used for registration of the SCOM Agent with Microsoft SCOM (setup and cleanup), and defaults to the following value:

        http://[Hostname]:8080/services/SCOM2007/SCOMService
    

    You need to make the following changes to each of the default URLs:

    • Replace [Hostname] in the URL with the hostname or IP address of the system where the SCOM Web Service is installed.

    • If necessary, change the port to the port on which the web services are running. For example, the default port for HTTP is 8080 and the default port for HTTPS is 8443.

    • If the SCOM Web Service was configured to use the HTTPS protocol, change http to https at the beginning of each web service URL.

    If you are using HTTPS as the protocol, you must also include the SCOM web service certificate in Oracle Wallet Manager as described in Section 2.3.3, "Adding Signed Certificates to Enterprise Manager".

  3. Enter the user name and password you specified when you installed the SCOM web service, which is discussed in steps 9 and 10 of Section 2.3.1.1, "Installing the Web Service on Unix", and steps 9 and 10 of Section 2.3.2.1, "Installing the Web Service on Windows".

  4. Enter the user name and password of the Oracle Enterprise Manager account.

  5. Optionally enter a polling interval to specify how often Oracle Enterprise Manager should poll the Microsoft SCOM web service for new or updated alerts to process. The poll interval defaults to 5 minutes if not specified.

  6. Click OK to save your configuration changes.

Configuring the Targets Page

Whenever a Microsoft SCOM alert is translated into an Oracle Enterprise Manager alert, the Microsoft SCOM alert host name determines the target-type instance associated with the alert in Oracle Enterprise Manager. If a target instance that matches the alert host name is not found, the default target instance of generic_scom_managed_host is used for the alert.

To add proxy targets in Oracle Enterprise Manager:

  1. From the Configure Management Connector page, click the Targets link to display the Targets page, as shown in Figure 3–2.

    Figure 3-2 SCOM Connector Target Settings

    Shows Targets tab of Configure Management Connector page
  2. Provide a target name. The Target Name field is set to the host name specified in the SCOM alert and must exactly match the name.

  3. Provide the SCOM host name in the SCOM HOST NAME field. This field must be set to the same value as the Target Name field.

  4. Repeat this process for as many target instances as desired.

  5. Click OK to save your configuration changes.

Adding a Subscription in SCOM

If you want to forward SCOM alerts to Enterprise Manager, you must add a subscription in SCOM to forward alerts to the SCOM Agent.

Perform the following steps to add a subscription in SCOM.

  1. In the Administration pane of the SCOM console, select Administration, then Notification, then Product Connectors. The SCOM Agent should be listed as a product connector.

  2. Right-click on the SCOM Agent and select Properties from the list of options to display the SCOM Agent – Product Connector Properties window.

  3. Click Add in the Subscriptions section to display the Product Connector Subscription Wizard window.

  4. Enter a subscription name and an optional description, then click Next.

  5. Select the groups that you want alerts to be forwarded from, then click Next.

  6. Select the targets for which you want alerts, then click Next.

  7. Specify the alert filtering criteria, then click Create.

SCOM should now be ready to forward alerts to the SCOM Agent.

Testing the Microsoft SCOM Connector

Perform the following steps to test the connector:

  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 SCOM Connector.

  5. Click on the General tab.

  6. Select and copy the URL specified for the createAlert or updateAlert operation.

  7. Open an internet browser on the system where the Oracle Enterprise Manager server is installed.

  8. In the address window, enter the URL that was copied in step 6 above. Add ?wsdl to the end of the URL. The URL should appear similar to the following example:

    http://[Hostname]:8080/services/SCOM2007/EventService?wsdl
    

    [Hostname] is the actual host name or IP address where the SCOM web service is installed.

    If the WSDL is loaded, this confirms that the connector is configured correctly for sending alert information to SCOM.

  9. At the Oracle Enterprise Manager console, select and copy the URL specified for the getNewAlerts, getUpdatedAlerts, or the acknowledgeAlerts operation. They should all be set to the same URL.

  10. Open an internet browser on the system where the Oracle Enterprise Manager server is installed.

  11. In the address window, enter the URL that you copied in step 9 above. Add ?wsdl to the end of the URL. The URL should be similar to the following example:

    http://[Hostname]:8080/services/AcquisitionService?wsdl
    

    [Hostname] is the actual host name or IP address where the SCOM web service is installed.

    If the WSDL is loaded, this confirms that the connector is configured correctly for polling alert information from SCOM.

  12. Select and copy the URL specified for the setup or cleanup operation.

  13. Open an internet browser on the system where the Oracle Enterprise Manager server is installed.

  14. In the address window, enter the URL that was copied in step 12 above. Add ?wsdl to the end of the URL. The URL should appear similar to the following example:

    http://[Hostname]:8080/services/SCOM2007/SCOMService?wsdl
    

    [Hostname] is the actual host name or IP address where the SCOM web service is installed.

    If the WSDL is loaded, this confirms that the connector is configured correctly for registering in SCOM.

Sending Oracle Enterprise Manager Alerts to Microsoft SCOM

Alerts generated or updated in Oracle Enterprise Manager are not transferred to SCOM unless you create notification rules to invoke the Microsoft SCOM notification method. A notification rule identifies the conditions that must be met before the notification method is invoked.

The following sections provide procedures that explain how to create and update notification rules.

Creating Notification Rules

The following procedure explains how to create a new notification rule to invoke the SCOM notification method.

  1. Click the Preferences link in the upper right corner of the Oracle Enterprise Manager console. The General page appears.

  2. Click the Notification Rules link on the left side of the window. The Notification Rules page appears and displays a list of all defined notification rules.

  3. Click Create to create a new notification rule.

  4. From the General sub-page, enter a name for the notification rule and an optional description.

    Select the target type and whether you want it to apply to all targets of that type or a specific instance. If you indicate that you want a specific instance, you need to click Add and select the desired target instance.

  5. Click the Availability link, then select the availability states for which you would like to receive notifications. Each state you select invokes the notification method whenever it is reached.

  6. Click the Metrics link. If you want to trigger the notification method based on metric violations, click Add and select the metrics and states for which you want to invoke the notification method, then click Continue.

  7. Click the Actions link. In the Advanced Notification Methods section, click the check box next to the SCOM Connector to assign the SCOM notification method to the notification rule.

  8. Click OK to complete the setup.

Updating Notification Rules

The following procedure explains how to update an existing notification rule to invoke the SCOM notification method.

  1. Click the Preferences link in the upper right corner of the Oracle Enterprise Manager console. The General page appears.

  2. Click the Notification Rules link on the left side of the window. The Notification Rules page appears and displays a list of all defined notification rules.

  3. Click on the radio button next to the notification rule you want to update, and click Edit to update the notification rule.

  4. Click the Actions link. In the Advanced Notification Methods section, click on the check box next to the SCOM Connector to assign the SCOM notification method to the notification rule.

  5. Click OK to complete the update.

Viewing Oracle Enterprise Manager Alerts

Whenever an alert is created in Microsoft SCOM from an alert that originates in Oracle Enterprise Manager, a link is provided in the alert text. To view the Oracle Enterprise Manager alert that triggered the alert, copy the URL to a web browser. You will be asked to log in to Oracle Enterprise Manager. After logging in, the Oracle Enterprise Manager alert information is displayed.

Sending Microsoft SCOM Alerts to Oracle Enterprise Manager

No special setup is required in Oracle Enterprise Manager to retrieve alert information from SCOM. Oracle Enterprise Manager automatically starts polling the SCOM web service after the connector has been configured.

SCOM does not automatically send new and updated alerts to the SCOM web service. You must define a subscription in SCOM to forward alerts to the SCOM Web Service. See Adding a Subscription in SCOM on page 3-4 for steps to add a subscription.

Generating Test Alerts in Microsoft SCOM

This section provides information for configuring SCOM to generate test alerts. If you already have a method of generating test alerts in SCOM, you can skip this section.

You need to perform the following tasks to generate a test alert in SCOM:

Adding a Rule in SCOM that Generates a Test Alert

  1. In the Authoring pane of the OpsMgr console, select Authoring, then Management Pack Objects, then Rules.

  2. Right-click on Rules and select Create a new rule… to display the The Create Rule Wizard window.

  3. In the "Select the type of rule to create" pane, select Alert Generating Rules, then Event Based, then NT Event Log (Alert), then click Next.

  4. Enter the Rule Name (this can be anything), select a rule target of Windows Server, then click Next.

  5. Make sure the Log name is set to Application, then click Next.

  6. Right-click on the And group and select Delete.

  7. Click Insert.

  8. Click the button in the expression that was inserted. A pop-up window should now appear.

  9. Click on the Select from a list of common event properties radio button, select EventSource from the list under the radio button, then click OK.

  10. Click on the Operator field and select Equals.

  11. Click on the Value field, enter WSH, then click Next.

  12. Enter the information that the alert is to generate. The generated information must meet the criteria specified in the subscription for the SCOM Agent.

  13. Click Create to create the rule.

Creating a VBScript File to Add an Error to the Application Log

  1. At the RMS system, create or identify the directory where the script will be located.

  2. Open a new document in a text editor.

  3. Copy the following VBScript commands into the new document:

    set objShell = CreateObject("WScript.Shell")
    objShell.LogEvent 1, "Test alert generated by VBScript"
    
  4. Save the file as createTestAlert.vbs in the directory from step 1 above.

Running the File

Now run the file to create a test alert. You should create a new test alert every time you run the script.