1 Installing and Configuring the Microsoft Operations Manager Connector

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 the MOM administrator identifies for marking alerts to Enterprise Manager. This should be a unique name you set up within Enterprise Manager that identifies this connector.

  MOM Registered Connector Name is the connector name that appears in MOM as the name for the resolution state you specified when configuring the MOM Connector. For example, if you specify Microsoft Operations Manager Connector in this field and 218 as the Resolution State, you can see a resolution state called Microsoft Operations Manager Connector in MOM (when right-clicking on an alert and selecting the Set Resolution State menu). You can see that this resolution state corresponds to 218 in MOM from the administrator's console.

• 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 the MOM Connector is 218.

  To verify whether a value is currently being used, go the the MOM server's Administrator Console. On the left panel, find Microsoft Operations Manager, then select Administration, Global Settings, and then select Alert Resolution State on the right panel. Right-click this and select Properties. This displays a table with the first two columns named Resolution State, which is a string, and ID, which is a number from 0 to 255.

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

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

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

  For an 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. The polling interval should not be shorter than 5 minutes. If you define an interval shorter than 5 minutes, it defaults to 5 minutes.

• Enterprise Manager Username — Enter the user name to be used to insert alerts; for example, SYSMAN. The user must have full privileges 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 user name you specified.

Creating 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.

An alert is 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 (Optional)", the alert is assigned to this target. If the target does not exist, the alert is assigned to the default target instance.

In the Configure Management Connector page, click the Targets tab to create specific target instances. Figure 1-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 optionally create target instances and associate external alerts with these 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.

Figure 1-3 Configure Management Connector Target Page

Response Status of Targets

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

After you configure the MOM Connector and the first event collection job runs (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), it marks the target as Down.

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

Prerequisites

To send alerts, MOM needs to support the following:

• "createEvent" and "updateEvent" literal-document style Web services, as described in the section "Providing Deployment Descriptor Mappings" in the Oracle Enterprise Manager Connectors Integration Guide.

• IP-based or SOAP header-based authentication. For more information, see the "Building a Help Desk Connector" chapter in the Oracle Enterprise Manager Connectors Integration Guide.

Configuring Rules to Send Alerts

You need to configure rules for sending out alerts through the MOM connector as follows:

1. From the Grid Control console, click Preferences in the upper right corner. The General Preferences page appears.

2. In the menu at the left, click My Rules. The My Notification Rules page appears.

3. Select a rule, then click Edit. The Edit Notification Rule page appears.

4. Select the Methods sub-tab. The E-mail Notification page appears.

5. Select the Microsoft Operations Manager Connector advanced notification method, then click OK.

6. Repeat this process for each rule you want to set.

Migrating from 10.2.0.3 to 10.2.0.4

If you have already configured the MOM Connector in version 10.2.0.3 and want to upgrade to version 10.2.0.4, do the following to enable bi-directional capability:

1. From the Grid Control console, click Setup in the upper right corner. The Overview of Setup page appears.

2. In the menu at the left, click Management Connectors. The Management Connectors page appears.

3. Select Microsoft Operations Manager Connector, then click the Configure icon. The Configure Management Connector page for MOM appears.

4. Click OK. No other action is needed to enable bi-directional capability.

Prerequisites

MOM needs to support the following literal-document style Web services:

• "getNewAlerts"

• "getUpdatedAlerts"

• "acknowledgeAlerts"

• "updateAlerts"

Forwarding Alerts to Enterprise Manager

You can forward MOM alerts to Enterprise Manager automatically or manually as follows:

• Automatically forward alerts by specifying the connector resolution state in the event rules and alert rules.

• Manually forward any existing MOM event to Enterprise Manager by changing the resolution state of the alert.

Refer to the Microsoft Operations Manager guide for more details.

Figure 1–4 shows alerts in the Operator Console of Microsoft Operations Manager. The first alert has a Resolution State set to MOM Connector, which indicates that the alert is waiting to be forwarded to Enterprise Manager. When the polling job picks up the alert and forwards it to Enterprise Manager, the alert's resolution state returns to its original state.

Figure 1-4 Alert Forwarded to Enterprise Manager

How Enterprise Manager Responds

After the alerts have been forwarded to Enterprise Manager, they are associated with the appropriate targets, depending on the mapping option(s) you select. The MOM Connector keeps track of all the events forwarded from MOM, and automatically updates information in Enterprise Manager after changes in MOM occur. This ensures that the two systems are always synchronized, providing you with timely information about your Microsoft environment.

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.

   Note:

   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.

   When the wizard completes, a certreq.txt text file is generated.

7. Send this request file to the Certificate authority, such as VeriSign.

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 into a text file.

   The content looks like the following:

   -----BEGIN CERTIFICATE-----
   MIICdzCCAV8CAQAwDQYJKoZIhvcNAQEEBQAwITELMAkGA1UEBhMCVVMxEjAQBgNVBAMMCXJvb3Rf
   dGVzdDAeFw0wNjExMTAxMDI5MzJaFw0xNjExMDcxMDI5MzJaMGYxCzAJBgNVBAYTAlVTMQ4wDAYD
   VQQIEwVUZXhhczEPMA0GA1UEBxMGRGFsbGFzMQ8wDQYDVQQKEwZvcmFjbGUxCzAJBgNVBAsTAkVN
   MRgwFgYDVQQDEw9zbXAtbXBpMi1vcmFwa2kwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAOch
   GIHp6MFW78OQw/mSdU0xfVq5u9pgqndnTqoh4aGFg1bTZD6/Azf3Nn8ibtKVJmGp3PLa3xP/gk7S
   tjZ/9sM4bvnw0Y4U9xsj0BiDG4JBo35uXAUxDHLReh8F4x45Wtv/SxvE0tjNnESlBMYynLip7P9l
   fSzcGKjSViyFW9M9AgMBAAEwDQYJKoZIhvcNAQEEBQADggEBAIktFTvDs7ULf0PclYXsJPeK4vFq
   7HZ86omktA9lYS+oA6SaudwDGY5yxcl9O2s78o+EK9e8Wz4wM4dmUg4aSuHVHWs75W86uh7gpEFo
   wssH9mtcxkqIbdPVwQoeAUTVOifNaujfXtgClvlvOjkfzvvD7SieRjD9mP2rJ2pRWUbv7xR7oJmt
   RXp6t22a+MKMQQR8ofAZV/WxFJcgmBR/JxLA28X+jnzmIH/yqHK/b6Agwwy7PgbJrwPI7WQ/busm
   6ASeV8ZgSfAkJ83nWz4NICnH5Y8Dyu8vDtERsOQ8z/WttrBDEmcGikkO9P+o2Y9w1pEJQhh4bKtD
   PyO9YLmlrLM=
   -----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.

8. Add the certificate file to the server.

Adding Signed Certificates to Wallet Manager

1. Create a wallet using the orapki utility by entering the following command:

   orapki wallet create -wallet client -auto_login

   Note:

   orapki is available at $ORACLE_HOME/bin on OMS.

2. Add the trusted certificate to the wallet by entering the following command:

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

3. To view the content of the wallet, enter 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, open the file and add the contents in your certdb.txt file to the existing content.

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