2 Installing the Connector

Preinstallation Requirements

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
  

  WARNING:

  This command upgrades other applications running under IIS to version 2.0.

• 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

  WARNING:

  Before proceeding, enabling ASP.NET 2.0 extensions may affect other applications that are running under IIS in an earlier version.

  To enable ASP.NET extensions, perform the following steps:

  1. Open the IIS Manager and expand the local computer in the left pane.

  2. Right-click on Web Service Extensions and select Allow all Web service extensions for a specific application …

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

  4. Click OK to enable the ASP.NET extensions.

Setting Up the Agent Account

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 "Ops Mgr Administrator Groups" below)

• Must be a member of an Ops Mgr role that has an Author profile (See "Ops Mgr user role for Oracle SCOM Agent" below)

Ops Mgr Administrator Groups

To determine the groups that are designated as an Ops Mgr Administrator, perform the following steps:

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

2. Right-click on Operations Manager Administrators and select Properties. The General tab lists the groups that have administrative permissions in the User Role members 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.

Ops Mgr user role for Oracle SCOM Agent

To add a new Ops Mgr 2007 user role for the Oracle SCOM Agent, perform the following steps:

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

2. Enter the name of the Oracle SCOM Agent in the User Role Name field.

3. Click Add to add a user role member. The Select Users or Groups pop-up window appears.

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

5. Click OK to add the Oracle SCOM Agent account as a user role member.

6. Click Next to go to the Approve targets page.

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

8. Click Next to go to the Approve groups page.

9. Select the groups that you want the Oracle SCOM Agent to access. You would generally want to use the default of all groups.

10. Click Next to go to the Approve tasks page.

11. Click Next to go to the Approve views page.

12. Click Next to go to the Summary page.

13. Click Create to create the Oracle SCOM Agent user role.

Installing the Agent

The SCOM Web Service uses the back-end Oracle SCOM Agent to access the SCOM API. The Oracle SCOM Agent must be installed on a Windows system that has connectivity to the SCOM Root Management Server (RMS). The Oracle SCOM Agent is preconfigured to interface with the SCOM Web Service and requires minimal configuration.

To install the Oracle SCOM Agent, perform the following steps:

1. Obtain a copy of the agent installation file from the Management Server host machine as specified in Exporting the Agent Installation File and put the SCOMAgent.zip installation file into the directory where you want to install the Oracle SCOM Agent.

2. Unzip the contents of the SCOMAgent.zip file to any directory.

   This creates the SCOMAgentInstaller.msi and the OracleEnterpriseManager.Alert.Creator.xml files in the designated directory.

3. Navigate to the directory and run the Oracle SCOM Agent installer by double-clicking on the SCOMAgentInstaller.msi file.

   This starts the installer and displays the Welcome to the Oracle SCOM Agent Setup Wizard page.

4. Click Next to display the Service Type page.

5. Select the type of service to be installed under IIS. The default and recommended service type is Web Site.

   This installs the service as a stand-alone web site. Selecting Virtual Directory installs the service as a Virtual Directory under an existing web site.

6. Click Next to display the Select Installation Folder page.

7. Enter the location to install the Agent or accept the default location of C:\iWaveSoftware\SCOMConnectorAgent.

8. Click Next to display the Oracle SCOM Agent Options page.

9. Enter the name to use when registering the connector in SCOM, or accept the default value of Oracle SCOM Agent.

10. Click Next to display the Confirm Installation page.

11. Click Next to display the SCOM Management Group Configuration page, and enter the information for the following required fields on the form:

    • Host name or IP address of the RMS server

    • Domain of the account to use when connecting to the SCOM API

    • User name of the account to use when connecting to the SCOM API

    • Password of the account to use when connecting to the SCOM API

    Note:

    The information for the account from Section 2.4.2, "Setting Up the Agent Account" should be entered in the Domain, Username, and Password fields.

12. Click Done to proceed. The window displayed next depends on the Service Type you selected in step 5 above.

    • If you selected Web Site:

      The Web Site Configuration window appears. This window contains the Web Site Name and Port Number fields, and both have default values. Accept the default values or change them to the desired values.

    • If you selected Virtual Directory:

      The Virtual Directory Configuration window appears. This window defines the name of the virtual directory to create and the web site within which it will be installed. Accept the default values or change them to the desired values.

13. For either window, click OK to proceed and display the Web Service Credentials window. This window defines the credentials to specify when testing the newly installed Oracle SCOM Agent.

14. Specify valid Windows account credentials and click OK.

    The installer now invokes the web service to verify that it is operational. A window pops up with the results of the test.

15. Close the window. The Installation Successful window appears. This window lists the URL of the Oracle SCOM Agent.

    Note the URL. You will need this whenever you install the SCOM Web Service.

16. Click OK to continue. The Installation Complete window appears.

17. Click Close to complete the Agent installation process.

Installing the Alert Creator Management Pack

A management pack file named OracleEnterpriseManager.Alert.Creator.xml is also included in the Agent installation zip file. This management pack is required to create alerts in SCOM. Follow the steps below to import the management pack into SCOM.

1. In the Administration pane of the OpsMgr console, select Administration, then Management Packs.

2. Right-click on Management Packs and select Import Management Pack… The Select Management Packs to Import window appears.

3. Navigate to the directory where the OracleEnterpriseManager.Alert.Creator.xml file is located.

4. Select the OracleEnterpriseManager.Alert.Creator.xml file and click Open. The Import Management Packs window appears.

   Note:

   Depending on the version of SCOM that you are running, you might 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 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

5. Click Import to import the management pack.

6. Click Close after the management pack has been imported.

The Agent is now configured to insert alerts into SCOM.

Starting and Stopping the Agent

The installer automatically starts the Agent. To stop the agent, open the IIS manager, select the web site where it was installed, then click Stop. To start, click Start.

Exporting the Agent Installation File

The agent installation file is included in the Self Update archive that was installed in Section 2.3, "Installing the Connector in Enterprise Manager". To extract the installation file, perform the following steps.

1. Determine the command required to export the agent installation file. To do this, perform the following steps:

   • From the Enterprise Manager console, click Setup.

   • Select Extensibility in the pane.

   • Select Self Update and then click Management Connector.

   • Click the SCOM connector name, then select Export from the Actions list.

   A popup window will appear with the command required to export the file.

2. Open a command window on the Operations Manager host machine and navigate to a temporary directory where the file can be copied.

3. Log into emcli using the following command. You will be asked to provide the password information for the sysman account.

   emcli login -username=sysman

4. Run the emcli export_update command from your system, changing <dirname> to the full path of the temporary directory.

   A zip file will be created. The file name will be comprised of the id value specified in the export_update command with a .zip extension.

5. Extract the agent installation file from the zip file using the following command:

   unzip *.zip archives/SCOMAgent.zip

Installing and Running the Microsoft SCOM Web Service on Unix

The following sections explain how to install and then subsequently run the Web Service.

Installing and Running the Microsoft SCOM Web Service on Windows

The following sections explain how to install and then subsequently run the Web Service.

net start iWaveAdapters

net stop iWaveAdapters

Exporting the Web Service Installation File

The web service installation file is included in the zip file that was extracted in section 2.4.6 "Exporting the Agent Installation File". To extract the installation file, perform the following steps.

1. Open a command window on the Operations Manager host machine and navigate to the temporary directory where the zip file was created.

2. Extract the web service installation file using the following command:

   unzip *.zip archives/SCOM_webservices_adapter.jar