1 Configuring Oracle Enterprise Manager Grid Control

The following chapter discusses the procedures required to configure Oracle Enterprise Manager Grid Control for use with Ops Center.

Register the Connector and Templates

You must extract and register the connector then register following webservice templates with Oracle Enterprise Manager Grid Control:

Incoming transform template for get new alerts
Outgoing transform template for get new alerts
Incoming transform template for get updated alerts
Outgoing transform template for get updated alerts
Generic outgoing template for update alerts
Outgoing transform template for get updated alerts

Note:

For environments with multiple Oracle Management Servers, the emctl extract_jar command must be run on all OMS instances (Step 1). The registration steps (2-6) may be run once from any of the Oracle Management Servers.

To register the Ops Center Connector and templates, or re-register a previously removed connector, follow these steps:

Run the following emctl command to extract the Ops Center Connector descriptors, templates and transform files from the connector .jar

The command extracts the connector files to the $ORACLE_HOME/sysman/connector/Ops_Center_Connector/ folder.

Note:
The emctl commands which follow will be run by the user who owns the oracle installation (generally oracle). Before you begin, verify that the $ORACLE_HOME/bin directory is in this user's PATH variable.

Command syntax for extract_jar:

% emctl extract_jar connector [-jar <jarfile>] [-ctname <connectorName>]

In the following command example the connector .jar is referenced from the current working directory:

% emctl extract_jar connector -jar ./OpsCenterConnector_1.0.jar -cname 'Ops Center Connector'
Register the Connector

Command syntax for register_connector:

% emctl register_connector connector [-dd <connectorType.xml>] [-cs <connect string>] [-s <server>] [-p <port>] [-sn <database sn>] [-repos_user <repos username>] [-repos_pwd <repos password>]

Note:
The remaining Seven emctl connector registration examples will prompt you for connection string information and sysman credentials. For many environments the connect string will have the following format: //localhost:1521/emrep

An example which interactively prompts for connect string, user and password is seen below:

% emctl register_connector connector -dd ${ORACLE_HOME}/sysman/connector/Ops_Center_Connector/OpsCenterConnector.xml
Register the incoming and outgoing transform templates for the get new alerts webservice method:

Command syntax for register_template (next six registration commands):

% emctl register_template connector [-t <template.xml>] [-cs <connect string>] [-s <server>] [-p <port>] [-sn <database sn>] [-repos_user <repos username>] [-repos_pwd <repos password>] [-ctname <connectorTypeName>] [-cname <connectorName>] [-iname <internalName>] [-tname <templateName>] [-ttype <templateType>] [-d <description>]

% emctl register_template connector -t $OMS_HOME/sysman/connector/Ops_Center_Connector/getNewAlerts_response.xsl -ctname 'Ops Center Connector' -cname 'Ops Center Connector' -tname 'Get New Alerts Response' -iname getNewAlerts -ttype 1 -d 'this transforms the get new alerts response'

% emctl register_template connector -t $OMS_HOME/sysman/connector/Ops_Center_Connector/getNewAlerts_request.xsl -ctname 'Ops Center Connector' -cname 'Ops Center Connector' -tname 'Get New Alerts' -iname getNewAlerts -ttype 2 -d 'this transforms the generic get new alerts request'
Register the incoming and outgoing templates for get updated alerts:

% emctl register_template connector -t $OMS_HOME/sysman/connector/Ops_Center_Connector/getUpdatedAlerts_response.xsl -ctname 'Ops Center Connector' -cname 'Ops Center Connector' -tname 'Get Updated Alerts Response' -iname getUpdatedAlerts -ttype 1 -d 'this transforms the get updated alerts response'

% emctl register_template connector -t $OMS_HOME/sysman/connector/Ops_Center_Connector/getUpdatedAlerts_request.xsl -ctname 'Ops Center Connector' -cname 'Ops Center Connector' -tname 'Get Updated Alerts' -iname getUpdatedAlerts -ttype 2 -d 'this transforms the generic get updated alerts request'
Register the generic outgoing template for update alerts

% emctl register_template connector -t $OMS_HOME/sysman/connector/Ops_Center_Connector/updateAlerts_request.xml -ctname 'Ops Center Connector' -cname 'Ops Center Connector' -tname 'Update Alerts' -iname 'updatedAlerts' -ttype 3 -d 'this is the generic template for Update Alerts'
Register the outgoing template for update alerts:

% emctl register_template connector -t $OMS_HOME/sysman/connector/Ops_Center_Connector/updateAlerts_request.xsl -ctname 'Ops Center Connector' -cname 'Ops Center Connector' -tname 'Update Alerts' -iname 'updatedAlerts' -ttype 2 -d 'this transforms the updateAlerts request'

Update the certdb.txt File

Append $OMS_HOME/sysman/connector/certdb.txt file with the contents of the web service certificate file that you captured earlier. See Capture the Web Service Certificate File.

Note:

If you have a multi-OMS environment, update the certdb.txt file on each OMS.

To update the certdb.txt file, as root, navigate to the following directory:

# ${OMS_HOME}/sysman/connector

If there is a certdb.txt file, paste the text of the exported certificate file into the certdb.txt file.
If there is not a certdb.txt file, open a text editor and use the exported certificate file to create a file.

Configuring the Oracle Enterprise Manager Grid Control Connector

When you access the Enterprise Manager console as a Super Administrator, the Ops Center Connector is displayed in the Management Connector Setup page as shown in Step 2.

As an Enterprise Manager Super Administration, click Setup in the upper right corner of the Enterprise Manager console.
Click the Management Connectors link in the left pane. The Management Connectors page appears. For the Ops Center Connector row, the Configured column should be blank, as shown below.

Note:
A check mark in the Configured column indicates that the Connector is already configured.

Figure 1-1 Management Connectors Page
Click the Configure icon for the Ops Center Connector. The General tab of the Configure Management Connector page appears as seen below.

Figure 1-2 General Tab of Configure Management Connector
Provide the following required settings. See General Settings for details. You must choose HTTPS as the protocol to establish a connection between Ops Center and Enterprise Manager.
1. Replace the [Hostname], including the brackets, in each of the three endpoint URLs with the Ops Center Enterprise Controller host name or IP address. The following is an example of a valid Web Service End Point
  
  https://myhostname:443/soap/NotificationBridge
2. Add the Ops Center and Oracle Enterprise Manager credentials:
  
  Ops Center – The Ops Center user created for connector use and the associated password
  
  Oracle Enterprise Manager – The Oracle Enterprise Manager sysman user and the associated password
3. Enter a polling time of at least five (5) minutes
4. Click OK to save the configuration
Optional: Go to the Targets tab and specify the details for creating additional target instances. See Managing and Creating Targets for details.
Click OK.

The Management Connectors page reappears. The Ops Center Connector row contains a check mark in the Configured column

Figure 1-3 Management Connectors Page With Configured Column Checked

General Settings

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

Web Service End Points — Web Service End Point (URL) for each of the three Operations (getNewAlerts, getNewAlerts and updateAlerts). Only the host name will be updated for your environment.
Ops Center Username — Ops Center user created for connector use.
Ops Center Password — The above users password.
Enterprise Manager Username — Enter the user name to be used to insert alerts; for example, SYSMAN. The user must have full privileges on the Ops Center Managed Host target. 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.
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.

Default Connector Target

When you register the connector, a default connector target named generic_ops_center_managed_host is created. This default connector target is displayed in the Grid Control Console as Ops Center Managed Host. It is associated with any alerts received from Ops Center which cannot be matched to any other Enterprise Manager targets.

Note:

Do not remove the default generic_ops_center_managed_host connector target. If the default target is removed, alerts which cannot be mapped to any other target will generate an error message, which is logged in the eocs.log file.

Managing and Creating Targets

In addition to the default connector target, you can create new Ops Center Managed Host targets. These targets can receive alerts from associated connectors.

This section discusses the following topics:

Connector Target Alert Association (Alert Routing)
Create Connector Targets (Optional)
Response Status of Targets

Connector Target Alert Association (Alert Routing)

The alerts created by the Ops Center Management Connector can be associated with either Enterprise Manager Grid Control Hosts or Ops Center Managed Hosts. Matching Grid Control Hosts have the highest precedence. If both a matching Ops Center Managed Host and a Grid Control Host alert is associated with the Enterprise Manager host, and if no matching target of either type exists, the alert is associated with the default connector target generic_ops_center_managed_host.

Note:

Enterprise Manager Grid Control patch 9153712 is required for routing Ops Center Alerts to Grid Control Hosts.

An alert is assigned to respective targets based on the asset name in Ops Center which generated the alert. If you have assets managed only in Ops Center, connector targets may optionally be created to avoid generated alerts being associated with the default connector host. The Ops Center Management Connector also supports routing alerts to a specially named connector target, ops_center_server. To keep alerts about the Ops Center Server and Connectivity issues from being associated with the default target, generic_ops_center_managed_host, create a connector target named ops_center_server.

Create Connector Targets (Optional)

In the Configure Management Connector page, click the Targets tab to create specific target instances.

You can optionally create additional Ops Center Managed Host and associate external alerts with these target instances.

To add a new target, follow these steps:

As an Enterprise Manager Super Administration, click Setup in the upper right corner of the Enterprise Manager console.
Click the Management Connectors link in the left pane.

The Management Connectors page appears.
Click the Configure icon for the Ops Center Connector.

The General tab of the Configure Management Connector page appears.
Specify the target name you would like to use for the created Ops Center Managed Host
In the HOSTNAME column, specify the asset name of the Ops Center target from which you would like to receive alerts.
Click OK.

Note:

If you want to create more target instances, 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.

Response Status of Targets

In Enterprise Manager, the response status of targets typically indicates whether an application is running. However, the response status will always be Pending for targets managed by Ops Center. For current detailed information of managed assets, use the Ops Center user interface.

Uninstalling the Ops Center Connector

To uninstall the Ops Center Connector from Oracle Enterprise Manager:

Select the Ops Center Connector in the Management Connectors page.
Click Delete. If you remove this connector at some point and then want to subsequently re-register it, see Register the Connector and Templates.

To remove the Notification Bridge from Ops Center:

As root, log in to the Enterprise Controller.

Use the pkgrm command to remove the notification package.

# pkgrm  ./SUNWxvmoc-notification-ws.pkg SUNWxvmoc-notification-ws

Stop and restart the Enterprise Controller.
```
# satadm stop -w
# satadm start -w
```