A Connector Tips

This appendix provides various tips that might help you to resolve issues you may encounter while configuring or using the MOM Connector.

Enabling IP-based Authentication

The following procedure is only applicable if you have not already enabled IP-based authentication.

Open Inetmgr (Internet Information Services) in the system where the MOM server is running by doing the following:
1. In Windows, select Start, then Run. The Run pop-up window appears.
2. Type inetmgr, then click OK. The Internet Information Services (IIS) Manager window appears.
Expand the computer name (local computer), then expand the WebSites folder.
Select the MOM 2005 Connector Framework, then right-click and select Properties. The Framework Properties window appears.
Select Directory Security.
Set up the IP address as follows:
1. In the "IP address and domain name restrictions" section, click Edit. The IP Address and Domain Name Restrictions window appears.
2. Click Add. The Deny Access window appears.
3. Enter the IP address where Enterprise Manager is located, then click OK to return to the Framework Properties window.
Set up authentication and access control as follows:
1. In the "Authentication and access control" section, click Edit. The Authentication Methods window appears.
2. Click the Enable Anonymous Access check box to enable it.
3. Provide a user name and password that grant Administrator rights, then click OK to return to the Framework Properties window.
Click OK to save your settings and exit the Framework Properties window.
Restart the MOM server.

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.

For an 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.

Connector Configuration Fails

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

Resolution state is not already in use.
Connector name is unique.

MOM Connector Fails to Retrieve Alerts

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

Valid resolution state is correctly marked.
Connector is not accidentally disabled on the MOM server.
Enterprise Manager user name and password that you specified in the MOM Configuration page are valid.

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 a case mismatch.

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

Targets Added in the Same Transaction

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

Polling Interval

The value of the polling interval is in minutes. The minimum value is 5 minutes. If you specify a shorter polling interval, it defaults to 5 minutes.

Alerts per Polling

The connector can process alerts up to twenty times the value of the polling interval at an instance. For example, if the Schedule Interval is 5, 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.

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>), the connector can request up to 100 alerts at an instance. To optimize the network usage, Oracle recommends that you set the same maximum value for both the processing and the requesting capabilities.

Metric/Target Does Not Exist

Target

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

If the metric does not exist, 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, the alerts are discarded and a message is logged to the log file.