17 Configuring Microsoft Operations Management Connector

Microsoft Operations Management Connector enables Oracle Enterprise Manager to retrieve alerts from Microsoft Operations Manager (MOM). The retrieved alerts are stored in the Enterprise Manager repository and displayed through the Enterprise Manager console.

This chapter provides the following information on setting up and configuring MOM Connector:

17.1 Introduction to MOM Connector

MOM Connector retrieves data through Web Services on HTTP and HTTPS protocols. The retrieval is done through a polling mechanism. The polling interval is user-definable. The polling interval cannot be shorter than 5 minutes. If an interval shorter than 5 minutes is defined, then it defaults to 5 minutes.

The default target_type defined in Enterprise Manager is mom_managed_host. The retrieved alerts are stored in the default target instance generic_mom_managed_host. You can create more target instances based on your requirements. See "Configuring the MOM Connector".

17.2 Installing MOM Connector

MOM Connector is installed as part of the Enterprise Manager base installation. After you install Enterprise Manager, you should see the MOM Connector listed on the Management Connectors page.

See Also:

Enterprise Manager Grid Control Installation and Basic Configuration Guide available at: http://www.oracle.com/technology/documentation/oem.html

17.3 Prerequisites

Before using MOM Connector, ensure that the following pre-requisites are met:

  • Microsoft Operations Manager 2005 is installed

  • MOM Connector framework Web services are enabled during the installation of MOM 2005

  • Internet Information Services (IIS) 6.0 or higher is deployed on the Windows server that hosts MOM

    See Also:

    MOM 2005 Product Documentation at the following URL: http://www.microsoft.com/mom/techinfo/productdoc/default.mspx

17.4 Configuring the MOM Connector

  1. From the Enterprise Manager console, click Setup.

  2. Click Management Connectors link in the left pane.

    The Management Connector Setup page appears. For the MOM Connector row, the Configured column should be blank (Figure 17-1).


    A check mark in the Configured column indicates that the Connector is already configured.
  3. Click the Configure icon for the MOM Connector.

    The General tab of the Configure Management Connector page appears.

  4. Provide the required settings. See "General Settings" for details (Figure 17-2).

  5. Click OK.

  6. (Optional) Go to the Targets tab and specify the details for creating additional target instances. See "Additional Target Instances" for details.

  7. Click OK.

    The Management Connector Setup page reappears.

    The MOM Connector row should have a check mark in the Configured column.

    Figure 17-1 Management Connectors Page

    Surrounding text describes Figure 17-1 .

    Figure 17-2 Configure Management Connector Page

    Surrounding text describes Figure 17-2 .

17.4.1 General Settings

This section provides the communication details required for configuring the connector.

  • MOM Registered Connector Name — Specify the connector name that you want to register with MOM. This is the name that MOM administrator identifies for marking alerts to Enterprise Manager. Ensure that the name you provide is unique in MOM.

  • Resolution State — Specify a value between 1 and 255. Make sure that you do not specify a value already in use including the standard values such as 85 or 255.

    The default value for MOM Connector is 218.

  • Protocol — Select either HTTP or HTTPS based on the protocol MOM Web services are running on.

  • Server — Enter the IP address or the DNS name of the MOM server.

  • Port — Enter the port number used by the MOM Web server. The default is 1271.

    In the case of HTTPS connection, you must change the port to the HTTPS port enabled in MOM.

  • Service Name — Enter the MOM Web service name. The default is ConnectorServiceV2.asmx. In most cases, you need not change this.

  • Polling Interval — Enter the time interval between event collections.

  • Enterprise Manager Username — Enter the username to be used to insert alerts, for example, SYSMAN. The user must have full privilege on the target of type MOM Managed Host.

    Administrator privileges are recommended, for instance you should be a super user such as SYSMAN.

  • Enterprise Manager Password — Enter a password for the username you specified.

17.4.2 Additional Target Instances

When you deploy or install a MOM Connector, a default target instance generic_mom_managed_host is created. In addition, you can create specific target instances.

Alert gets assigned to the respective targets based on the computer name in MOM. If the name specified under Computer column in the MOM Operator console matches the target name you specify in the Target Name column in the section "Targets Managed by External System", then the alert will be assigned to that target.

If the target does not exist, then the alert will be assigned to the default target instance.

In the Configure Management Connector page, click the Targets tab to create specific target instances. Figure 17-3 shows the Configure Management Connector Target page.

Default Connector Target

The default target instance holds external alerts that are not associated with any particular Enterprise Manager target. Oracle recommends that you do not remove this default connector target when you create additional targets.

If the default target is removed accidentally, you can recreate it by clicking the Enable button in the Targets tab of the Configure Management Connector page.

If the default target is removed, for alerts that cannot be mapped to any target, error messages are logged in the file emoms.log.

Targets Managed by External System

(Optional) In this section, you can create target instances and allow external alerts to be associated with those target instances.

To add a new target,

  1. Specify the target name in the Target Name column.

  2. In the MOM HOSTNAME column, specify the fully qualified hostname (hostname along with the domain name, for example smp-mpi2.us.oracle.com) of the target.

  3. Click OK.


If you want to create more target instances, then click Add Rows to add additional rows and then specify the target information. To remove a target, check the Select check box corresponding to the target, click Remove, then click OK.

Figure 17-3 Configure Management Connector Target Page

Surrounding text describes Figure 17-3 . Response Status of Targets

The response status of generic_mom_managed_host asserts whether the MOM server is running. Immediately after registration, the status shows Pending.

After you configure the MOM Connector and the first event collection job is run (within a polling interval), the status shows either Up or Down. The response status of individual targets represent whether the host (represented by that target) is up or down.When the target is created, Enterprise Manager pings the host. If the server is reachable, the status is marked Up. Subsequently, if Enterprise Manager receives any alerts (indicating that the host is down), then it marks the target as Down.

If the target is down, then alert retrieval is interrupted until the target is up again.


In Enterprise Manager, the response status of targets managed by MOM might not be definitive and can be used only for reference purposes. For accurate information of its managed entities, use MOM.

17.5 Enabling SSL Connection for HTTPS

Follow the steps provided in this section if you choose HTTPS as the protocol to establish a connection between MOM and Enterprise Manager.

17.5.1 Generating a Certificate Request File

Generate a certificate request file from the MOM server by doing the following:

  1. On the Windows task bar, go to Start, then click Run.

  2. Type inetmgr in the Open field.

    The Internet Information Services (IIS) Manager screen appears.

  3. In the left pane, navigate to Web Sites and select the Microsoft Operations Manager 2005 connector framework.

  4. Right-click and select Properties.

    The Microsoft Operations Manager 2005 Connector Framework Properties dialog box appears.

  5. In the Directory Security tab, go to the Secure Communications section and click Server Certificate.

  6. Using the wizard, create a new certificate.


    When you specify details for certificate generation, do not use abbreviated forms for city and state names as the wizard does not recognize abbreviations. For example, CA is not accepted for California.
  7. At the completion of the wizard, a text file, certreq.txt is generated.

  8. Send this request file to the Certificate authority, for example VeriSign.

17.5.2 Using the Certificate from the Certificate Authority

After processing your request, the certificate authority sends you the certificate. After you receive the certificate, do the following:

  1. Paste the content in to a text file.

    The content looks like the following:

    -----END CERTIFICATE-----
  2. Save the file as cert.cer.

  3. On the Windows task bar, go to Start, then click Run.

  4. Type inetmgr in the Open field.

    The Internet Information Services (IIS) Manager screen appears.

  5. In the left panel, navigate to Web Sites and select the Microsoft Operations Manager 2005 connector framework.

  6. Right-click and select Properties.

    The Microsoft Operations Manager 2005 Connector Framework Properties dialog box appears.

  7. In the Directory Security tab, go to the Secure Communications section, and click Server Certificate.

    Add the certificate file to the server.

17.5.3 Adding Signed Certificates to Wallet Manager


Oracle Wallet Manager is available at $ORACLE_HOME/bin on OMS. See Oracle Application Server Administrator's Guide for details.
  1. Create a wallet using orapki utility by using the following command:

    orapki wallet create -wallet client -auto_login


    orapki is available at $ORACLE_HOME/bin on OMS.
  2. Add the trusted certificate to the wallet by using the following command:

    orapki wallet add -wallet client -trusted_cert -cert verisignCert.cer

  3. To view the content of the wallet, run the following command:

    orapki wallet display -wallet client

    Ensure that a file named ewallet.p12 is available.

  4. In the Oracle Wallet Manager, open the client certificate ewallet.p12.

  5. Go to Select Trusted Certificates and select Operations on the main menu.

  6. Select Export All Trusted Certificates.

  7. Save the file as certdb.txt.

  8. Place the certdb.txt in the connector home root directory ($OMS_HOME/sysman/connector).

    If the file certdb.txt already exists in the connector home root directory, then open the file and add the contents in your certdb.txt to the existing content.

Now this file can be used by the Java SSL for communication between Enterprise Manager and MOM server in HTTP mode.

See Also:

For information on creating wallet, see "Creating and Viewing Oracle Wallets with orapki" in the Oracle Database Advanced Security Administrator's Guide, 10g Release 2 (10.2).

17.6 MOM Connector Tips

This section provides various tips that might help you in resolving issues you encounter while configuring or using the MOM Connector.

17.6.1 Recommended Protocol

Oracle recommends that you use HTTPS as the protocol for the communication between Enterprise Manager and MOM.

Use HTTP only if a secure connection is not required and the data can be transferred in clear text between the two systems.

In the case of HTTPS connection, you need to change the port to the HTTPS port enabled in MOM. Because Enterprise Manager polls data from MOM to Enterprise Manager, this means configuring MOM in HTTPS mode.

17.6.2 Connector Configuration Fails

If the connector configuration fails, then ensure the following in the MOM Administrator Console:

  • Resolution state is not already in use

  • Connector name is unique

17.6.3 MOM Connector Fails to Retrieve Alerts

Ensure the following if Enterprise Manager fails to retrieve alerts although MOM server is marked for forwarding alerts:

  • Valid resolution state is correctly marked

  • Connector is not accidentally disabled on MOM server

  • Enterprise Manager username and password that you specified in the MOM Configuration page are valid.

17.6.4 Alert Logging to Additional Target Instance Fails

Even if you define additional target instances, alerts are logged to the default target instance if the target name has characters with case mis-match.

The target name is case-sensitive and therefore should match the case of the target name in the Enterprise Manager.

17.6.5 Adding Targets in the Same Transaction

You cannot delete and add the same target in the same transaction.

17.6.6 Polling Interval

The value of polling interval is in minutes. The minimum value is 5 minutes. If you specify a shorter polling interval, then it will default to 5 minutes.

17.6.7 Alerts per Polling

Processing Capability

Connector can process alerts up to twenty times the value of the polling interval at an instance.

For example, if Schedule Interval is 5, then the maximum number of alerts retrieved is 100 (20*5). This is also the default value.This number need not be the same as the maximum number of alerts the connector is capable of requesting from MOM.

Modifying the Processing Capability

The maximum number of alerts the connector is capable of requesting from MOM depends on the number you specify in the files generic_request_newalerts.xml and generic_request_updatedalerts.xml.

For example, if you have specified 100 (<maxCount>100</maxCount>), then the Connector can request up to 100 alerts at an instance.

To optimize the network usage, Oracle recommends that you set the maximum value for both the processing and the requesting capabilities as the same.

17.6.8 Metric/Target Does Not Exist


If target does not exist, then the alert is assigned to generic_mom_managed_host.


If the metric does not exist, then Enterprise Manager creates one.

Generic MOM Target

If the alert does not match any target and the generic MOM target (generic_mom_managed_host) does not exist, then the alerts are discarded and a message is logged to the log file.