The Microsoft Systems Center Operations Manager (SCOM) 2007 Connector (version 12.1.0.2.0) integrates Oracle Enterprise Manager with Microsoft SCOM 2007 (including R2) through web services. Using this connector you can create, update or close alerts on SCOM system for any event generated in Enterprise manager, which ensures an active synchronization between SCOM and Enterprise Manager. Events in Enterprise Manager are equivalent to alerts in the SCOM system.
There are two types of SCOM connectors available. You must determine which connector you want to use based on the version of SCOM being used in your environment:
The SCOM pre R2 Connector supports the RTM and SP1 versions of SCOM 2007.
The SCOM R2 Connector supports SCOM 2007 R2.
The SCOM 2007 connectors in the Enterprise Manager store are available on the Self Update page for downloading provided the My Oracle Support Preferred Credentials are configured. See Installing the Connector in Enterprise Manager for instructions.
The following topics are presented:
The connector supports the following versions of Oracle Enterprise Manager and Microsoft SCOM:
Oracle Enterprise Manager Cloud Control 12c Release 1.
Microsoft Systems Center Operations Manager version 2007 (including R2).
You can install the SCOM Agent on Microsoft Windows (2000, 2003, and 2008) platform.
The base Enterprise Manager version number for the Microsoft Systems Center Operations Manager Connector Release 12.1.0.2.0 is Enterprise Manager 12c Release 1 (12.1.0.1) and higher versions.
You can install the Oracle SCOM Agent on Microsoft Windows (2000, 2003, and 2008) platform.
The SCOM 2007 and SCOM 2007 R2 connectors require additional customization for full functionality. In addition to the install directions for SCOM 2012 in this user guide, perform the following steps to complete the installation for SCOM 2007 connector instances:
The following requirements apply to the system where the Oracle SCOM Agent is installed:
.NET framework 2.0 is installed.
.NET framework 3.0 is installed.
ASP.NET 2.0 is installed. After .NET framework 2.0 is installed, enter the following command to install ASP.NET 2.0:
%SystemRoot%\Microsoft.NET\Framework\v2.0.xxxxx\aspnet_regiis -i
Internet Information Services (IIS) 5.0 or higher is installed.
Operations Manager 2007 Console is installed.
ASP.NET 2.0 extensions are enabled in IIS.
To enable ASP.NET extensions, perform the following steps:
Open the IIS Manager and expand the local computer in the left pane.
Right-click on Web Service Extensions and select Allow all Web service extensions for a specific application.
Select ASP.NET v2.0.0xxxxx from the pull-down list, where xxxxx is the version of the .NET framework 2.0 that is installed.
Click OK to enable the ASP.NET extensions.
Before installing the Oracle SCOM Agent, you need to set up an account for the Oracle SCOM Agent to access the SCOM API. The account must satisfy the following requirements:
Must be a domain account.
Must be used exclusively by the Oracle SCOM Agent.
Must have local administrator permissions.
Must be a member of a group designated as an Ops Mgr Administrator (See Determine Ops Mgr Administrator Groups below).
Must be a member of an Ops Mgr role that has an Author profile (See Add Ops Mgr User Role for Oracle SCOM Agent below).
To determine the groups that are designated as an Ops Mgr Administrator, perform the following steps:
In the Administration pane of the Ops Mgr 2007 console, select Administration, then Security, then User Roles. The User Roles should be displayed in the center pane.
Right-click on Operations Manager Administrators and select Properties. The General tab lists the groups that have administrative permissions in the User Role member's window. The account the Agent uses must be a member of one of the groups listed here, or you need to add one of its groups to this list.
To add a new Ops Mgr 2007 user role for the Oracle SCOM Agent, perform the following steps:
In the Administration pane of the Ops Mgr 2007 console, select Administration, then Security, then User Roles. Right-click on User Roles and select New User Role, then Author. The Create User Role wizard window appears.
Enter the name of the Oracle SCOM Agent in the User Role Name field.
Click Add to add a user role member. The Select Users or Groups pop-up window appears.
Enter the domain user account information in the Enter the object names to select dialog box. Since this is a domain user account, you need to specify the account as <DOMAIN>\<username>, where <DOMAIN> is the Windows domain where the account was created, and <username> is the user name of the account set up for the Oracle SCOM Agent.
Click OK to add the Oracle SCOM Agent account as a user role member.
Click Next to go to the Approve Targets page.
Select the targets that you want the Oracle SCOM Agent to access. These are the target types for the events that the Oracle SCOM Agent will handle. Typically, you would use the default "All targets are automatically approved, including targets in Management Packs imported in the future."
Click Next to go to the Approve Groups page.
Select the groups that you want the Oracle SCOM Agent to access. You would generally want to use the default of All Groups.
Click Next to go to the Approve Tasks page.
Click Next to go to the Approve Views page.
Click Next to go to the Summary page.
Click Create to create the Oracle SCOM Agent user role.
A management pack file named OracleEnterpriseManager.Alert.Creator.xml is also included in the Agent/Notification installation zip files. This management pack is required to create alerts in SCOM. Follow the steps below to import the management pack into SCOM.
In the Administration pane of the Operations Manager console, select Administration, then Management Packs.
Right-click on Management Packs and select Import Management Packs… The Select Management Packs to Import window appears.
Navigate to the directory where the OracleEnterpriseManager.Alert.Creator.xml file is located.
Select the OracleEnterpriseManager.Alert.Creator.xml file and click Open. The Import Management Packs window appears.
Known Issue for SCOM 2007:
Depending on the version of SCOM 2007 that you are running, you may see the following error when you attempt to open the management pack:OracleEnterpriseManager Alert Creator The OracleEnterpriseManager Alert Creator Management Pack will fail to import because it depends on the following Management Packs: System.Library version 6.0.6278.0 Microsoft.SystemCenter.Library version 6.0.6278.0 System.Health.Library version 6.0.6278.0 Microsoft.Windows.Library version 6.0.6278.0 Please add them to the list by clicking on the Add... button and searching in your machine.
If you see this error, you need to use a text editor to change the four management packs referenced in the References section of the management pack file. The version number information must be updated to match the version numbers used in your system.
The References section that you need to edit should look like this:
<References>
<Reference Alias="System">
<ID>System.Library</ID>
<Version>6.0.6278.0</Version>
<PublicKeyToken>1a2b3c4d5e5f</PublicKeyToken>
</Reference>
<Reference Alias="SCLibrary">
<ID>Microsoft.SystemCenter.Library</ID>
<Version>6.0.6278.0</Version>
<PublicKeyToken>6f5e4d3c2b1a</PublicKeyToken>
</Reference>
<Reference Alias="Health">
<ID>System.Health.Library</ID>
<Version>6.0.6278.0</Version>
<PublicKeyToken>123abc456def</PublicKeyToken>
</Reference>
<Reference Alias="Windows">
<ID>Microsoft.Windows.Library</ID>
<Version>6.0.6278.0</Version>
<PublicKeyToken>11aa22bb33cc44dd</PublicKeyToken>
</Reference>
</References>
Click Import to import the management pack.
Click Close after the management pack has been imported.
The Agent is now configured to insert alerts into SCOM.
This section identifies the default mappings for the createEvent and the updateEvent operations that are specific to the SCOM 2007 connectors. Table E-1 lists the XSL files that perform the mappings for the SCOM 2007 connector and provides a summary of each.
Table E-1 XSL Files that Perform SCOM 2007 Mappings
| File | Description |
|---|---|
|
|
Transforms the Oracle Enterprise Manager event data to the Microsoft SCOM 2007 alert format for the |
|
|
Transforms the Oracle Enterprise Manager event data to the Microsoft SCOM 2007 alert format for the |
|
|
Transforms the Oracle Enterprise Manager event data to the Microsoft SCOM 2007 alert format for the |
The following sections provide details about the default templates:
The Oracle Enterprise Manager Connector Framework invokes the createEvent operation whenever an event is generated in Oracle Enterprise Manager and a rule is configured to invoke a SCOM 2007 connector. The appropriate create template is invoked during the process to transform the data from Oracle Enterprise Manager format to SCOM alert format. Table E-2 lists the default field mappings between the Microsoft SCOM alert and the Oracle Enterprise Manager event for createEvent operations.
Table E-2 Create Event 2007 Template Mappings
| SCOM Field Name | Required | Value |
|---|---|---|
|
Name |
Yes |
Set to the event |
|
Description |
Yes |
Set to the formatted contents of the event as specified in Formatted Enterprise Manager Description Contents. |
|
Priority |
Yes |
Set the priority based on the event priority. See Priority Mapping for details. |
|
Severity |
Yes |
Set the severity based on the event severity. See Severity Mapping for details. |
The Oracle Enterprise Manager Connector Framework invokes the updateEvent operation whenever an event is generated in Oracle Enterprise Manager and a rule is configured to invoke the SCOM connector.
The updateEvent_request.xsl template is invoked during the process to transform the data from Oracle Enterprise Manager format to SCOM alert format. Table E-3 lists the default field mappings between the Microsoft SCOM alert and the Oracle Enterprise Manager event.
Table E-3 Update Event 2007 Template Mappings
| SCOM Field Name | Required | Value |
|---|---|---|
|
ID |
Yes |
Set to the event |
|
Resolution State |
Yes |
Set to 255 (Closed) if the event severity is Clear. Otherwise, set to 0 (New). |
|
Alert History |
No |
Set to "Oracle Enterprise Manager cleared alert" if the event severity is Clear.Set to "Oracle Enterprise Manager changed alert severity to warning" if the event severity is Warning.Set to "Oracle Enterprise Manager changed alert severity to critical" if the event severity is Critical.Not set for other severity values. |