This chapter provides information to assist in troubleshooting integration issues with IBM Netcool/OMNIbus. The chapter focuses on troubleshooting issues in the web service front-end and the back-end Agent.
This chapter discusses the following topics:
In order to troubleshoot integration issues, you must adjust the Oracle Enterprise Manager logging options to capture additional information.
To enable debug logging information:
Edit the emomslogging.properties file using a text editor. The location of the file depends on the Enterprise Manager version:
Enterprise Manager version 11.1.0.1
<ORACLE_HOME>/oms11g/sysman/config
Set the parameters as follows:
log4j.appender.emlogAppender.Threshold = DEBUG log4j.rootCategory=DEBUG, emlogAppender, emtrcAppender
After setting the debug logging parameters, restart OMS by opening a command window, changing the working directory to <ORACLE_HOME>/oms10g/bin, and issuing the following commands:
emctl stop oms emctl start oms
To identify and configure the connector to use the correct URL for Netcool/OMNIbus Web Service operations:
Open a command terminal on the system where the Netcool/OMNIbus web service is installed.
Change the working directory to the adapters/log directory in the Netcool/OMNIbus web service installation directory.
Open the framework.log file in a text editor.
Go to the bottom of the file and search backwards for the string Setting the server's publish address to be. Continue searching backwards until the URL that contains AcquisitionService is found. The URL listed there is the URL that should be specified for the getNewAlerts, getUpdatedAlerts, and acknowledgeAlerts operations.
Go to the bottom of the file and search backwards for the string Setting the server's publish address to be. Continue searching backwards until the URL that contains EventService is found. The URL listed here is the URL that should be specified for the createEvent and updateEvent operations.
Log in to the Oracle Enterprise Manager console by entering a user name with a "Super Administrator" role, entering the appropriate password, then clicking Login.
Click the Setup link at the top right part of the window. The Overview of Setup page appears.
Click the Management Connectors link on the left side of the window. The Management Connectors page appears, which shows the installed connectors.
Click on the Configure icon associated with the Netcool/OMNIbus Connector. This invokes edit mode, enabling you to configure the connector.
Verify that the URL identified in step 4 is specified for the getNewAlerts, getUpdatedAlerts, and acknowledgeAlerts operations. The URL from the log file will specify a host name of localhost. The URL specified for the different operations must specify the IP address or host name of the system where the web service is installed as the host name instead of localhost.
Verify that the URL identified in step 5 is specified for the createEvent and updateEvent operations.
If any of the operations are incorrect, change to the correct URL and click OK.
You might encounter issues involved in generating or updating events in Netcool/OMNIbus from alerts that have originated in Oracle Enterprise Manager or vice versa. The following sections provide diagnostic information to resolve these problems:
Netcool/OMNIbus can generate or update events from alerts that have originated in Oracle Enterprise Manager. Perform the following diagnostic steps if Netcool/OMNIbus events are not being generated or updated as expected:
Verify that a notification rule is set up for the condition that triggered the alert. Perform the following steps to verify that it is set up correctly:
Open an Oracle Enterprise Manager console window and log in.
Click Setup in the upper right corner of the Oracle Enterprise Manager console.
Click Notification Methods on the left side of the window.
Locate the Netcool/OMNIbus Connector in the table near the bottom of the window and click on it to list and note the notification rules that use this method.
Click Preferences in the upper right corner.
Click Notification Rules on the left side of the window. This displays a list of all defined notification methods.
Examine the details for the rules listed in step d above and verify that at least one rule matches the conditions that triggered the alert.
If you did not find at least one rule, you need to modify an existing notification rule or add a new one to invoke the Netcool/OMNIbus notification method.
Determine the error that Oracle Enterprise Manager has reported:
Navigate to the page that displays the alert information that should have triggered the new event in Netcool/OMNIbus.
For example, if the Memory Utilization % metric was set up to invoke the Netcool/OMNIbus Connector method, you would perform the following steps to access the page that displays alert information. This example assumes that the generated alert was critical.
1.) Click the Alerts tab.
2.) Click the Critical sub-tab.
3.) Click the Memory Utilization % alert.
Click on the details and look for any error events.
After the alert is generated, it initially indicates that the method will be invoked, but no error events appear. The Enterprise Manager Connector Framework makes several attempts to transfer the alert information to the Netcool/OMNIbus web service. After all attempts have failed, an error event is usually added to the details for the alert. If there are no errors after several minutes, it is likely that no error events will be added to the log.
If there is no error information in the alert details, you need to examine the log file for errors. Perform the following steps to locate errors in the log file:
1.) Open the emoms.trc file in a text editor.
The location of the file depends on the Enterprise Manager version.
Enterprise Manager version 11.1.0.1
<EM_INSTANCE_BASE>/em/<OMS_NAME>/sysman/log/
Where <EM_INSTANCE_BASE> is the OMS Instance Base directory. By default, the OMS Instance Base directory is gc_inst, which is present under the parent directory of the Oracle Middleware Home.
2.) Go to the bottom of the file and search backwards for this string:
ERROR core.EMEventConnectorServiceImpl createEvent
The error event is contained in the Exception information.
Diagnose the problem based on the error event. See Resolving Alerts from Oracle Enterprise Manager for information on troubleshooting common error events.
Oracle Enterprise Manager can generate or update alerts resulting from events that have originated in Netcool/OMNIbus. Perform the following diagnostic steps if Oracle Enterprise Manager alerts are not being generated or updated as expected.
Open the $OMS_HOME/sysman/log/emoms.trc file in a text editor. The location of the file depends on the Enterprise Manager version:
Enterprise Manager version 11.1.0.1
<EM_INSTANCE_BASE>/em/<OMS_NAME>/sysman/log/
Where <EM_INSTANCE_BASE> is the OMS Instance Base directory. By default, the OMS Instance Base directory is gc_inst, which is present under the parent directory of the Oracle Middleware Home
Go to the bottom of the file and search backwards for getNewAlerts().
Any instances you find are immediately followed by exception information that identifies the cause of the failure.
See Resolving Events from Netcool/OMNIbus for the error event you found in the log file. Each event entry explains the cause of the problem and the steps required to correct the problem.
This section provides cause and solution information on troubleshooting common alert messages. Find the error message in Table 5-1 that matches your alert message, then refer to the corresponding section(s) indicated under Possible Cause for instructions to diagnose and correct the problem.
Table 5-1 Enterprise Manager Alert Messages
| Alert Message | Possible Cause | Applicable Versions |
|---|---|---|
|
The server sent HTTP status code 403: Forbidden |
11.1.0.1 |
|
|
javax.net.ssl.SSLKeyException: [Security:090477]Certificate chain received from IWAVETEC39A - 10.2.1.141 was not trusted causing SSL handshake failure. |
11.1.0.1 |
|
|
HTTP transport error: java.net.SocketException: Socket Closed |
Netcool/OMNIbus Web Service Is Down, Invalid IP Address or Port Number |
11.1.0.1 |
|
HTTP transport error: java.net.UnknownHostException: <hostname> |
11.1.0.1 |
|
|
The server sent HTTP status code 404: Not Found |
11.1.0.1 |
|
|
javax.xml.ws.soap.SOAPFaultException: Attempt to insert the event into Netcool/OMNIbus failed |
11.1.0.1 |
|
|
javax.xml.ws.soap.SOAPFaultException: Timeout occurred waiting for synchronous response from Netcool/OMNIbus after inserting an event |
11.1.0.1 |
|
|
com.iwave.operations.OperationsException.OperationsException: Attempt to insert the event into the master probe failed |
Probe is not Running or Invalid Port Specified in the Configuration |
11.1.0.1 |
The user name or password for accessing the Netcool/OMNIbus web service is incorrect.
Log in to the Oracle Enterprise Manager console by entering a user name with a "Super Administrator" role, entering the appropriate password, then clicking Login.
Click the Setup link at the top right corner of the window. The Overview of Setup page appears.
Click the Management Connectors link on the left side of the window. The Management Connectors page appears, which shows the installed connectors.
Click on the Configure icon associated with the Netcool/OMNIbus Connector.
Click the General tab.
Correct the Netcool/OMNIbus Web Service Username and Netcool/OMNIbus Web Service Password fields, then click OK.
The SSL handshake between the Oracle Enterprise Manager Connector Framework and the Netcool/OMNIbus web service failed. This failure occurs because Oracle Enterprise Manager is not configured correctly with the SSL certificate for the Netcool/OMNIbus web service. The SSL certificate the Netcool/OMNIbus web service uses must be imported into the certificate store. The certificate is either missing from the certificate store or does not match the SSL certificate provided by the Netcool/OMNIbus web service.
Import the SSL certificate from the Netcool/OMNIbus web service into the certificate store. See Adding Signed Certificates to Enterprise Manager for details on setting up Oracle Enterprise Manager with the Netcool/OMNIbus SSL certificate.
The Netcool/OMNIbus web service is down.
Perform the following steps to check the status of the web service and start it if necessary.
If the Netcool/OMNIbus web service is installed on a Unix system:
Open a command terminal on the system where the Netcool/OMNIbus web service is installed.
Change the working directory to the adapters/bin directory in the Netcool/OMNIbus web service installation directory.
Enter the following command:
./service.sh status
If the command indicates that the service is not running, enter the following command:
./service.sh start
If the Netcool/OMNIbus web service is installed on a Windows system:
Open a command terminal on the system where the Netcool/OMNIbus web service is installed.
Change the working directory to the adapters/log directory in the Netcool/OMNIbus web service installation directory.
Open the framework.log file in a text editor.
Go to the bottom of the file and search backwards for the string iWave Adapter Framework. If the last occurrence found is iWave Adapter Framework Started, this indicates that the web service is started.
If the web service is not started, start the web service based on how the web service is installed.
If it is installed as a standalone application, change the working directory to the adapters/bin directory and run the startAdapters.bat command file.
If it is installed as a Windows service, enter the net start iWaveAdapters command.
The system does not recognize the host name specified in the URL.
To address this issue:
Coordinate with the system administrator to change the system configuration to recognize the host name.
Specify the IP address in the URL instead of the host name. To do this, perform the following steps:
Determine the IP address of the system where the Netcool/OMNIbus web service is installed.
Log in to the Oracle Enterprise Manager console by entering a user name with a "Super Administrator" role, entering the appropriate password, then clicking Login.
Click the Setup link at the top right part of the window. The Overview of Setup page appears.
Click the Management Connectors link on the left side of the window. The Management Connectors page appears, which shows the installed connectors.
Click on the Configure icon associated with the IBM Netcool/OMNIbus Connector. This invokes edit mode, enabling you to configure the connector.
Change the host name to the IP address in the URL specified for the createEvent and updateEvent operations.
Click OK.
The IP address or port number specified in the URL is invalid, or the network is down.
Verify that the hostname/IP address configured for the connector is correct:
Log in to the Oracle Enterprise Manager console by entering a user name with a "Super Administrator" role, entering the appropriate password, then clicking Login.
Click the Setup link at the top right part of the window. The Overview of Setup page appears.
Click the Management Connectors link on the left side of the window. The Management Connectors page appears, which shows the installed connectors.
Click on the Configure icon associated with the Netcool/OMNIbus Connector. This invokes edit mode, enabling you to configure the connector.
Verify that the hostname/IP address and port number specified in the URL for the createEvent and updateEvent operations are correct.
If the hostname/IP address and port number are incorrect, provide the correct values and click OK.
If the URLs specify a host name, make sure that the host name resolves to the correct IP address. To determine the IP address of the host name, issue the ping <hostname> command, where <hostname> is the actual host name. This lists the IP address that was resolved for the host name. If this is incorrect, the system administrator needs to investigate why it is incorrect.
If the hostname/IP address appears to be correct, try to ping the system where the Netcool/OMNIbus web service is installed using the hostname/IP address. If the ping fails, the system administrator needs to investigate why there is no connectivity.
The web service received the request and rejected it because there was a problem. This likely indicates that an invalid path was specified in the URL.
To determine the reason for the failure, examine the HTML document listed with the Exception information in the emoms.trc log file.
The location of this file for Enterprise Manager version 11.1.0.1 is:
<EM_INSTANCE_BASE>/em/<OMS_NAME>/sysman/log/
Where <EM_INSTANCE_BASE> is the OMS Instance Base directory. By default, the OMS Instance Base directory is gc_inst, which is present under the parent directory of the Oracle Middleware Home.
The HTML document provides error information that indicates the reason why it was rejected. The error information may be difficult to spot because the HTML tag delimiters are encoded. If the error information specifies HTTP Error: 404, this indicates that the path in the URL is incorrect. To test the URL the connector is using:
Log in to the Oracle Enterprise Manager console by entering a user name with a "Super Administrator" role, entering the appropriate password, then clicking Login.
Click the Setup link at the top right part of the window. The Overview of Setup page appears.
Click the Management Connectors link on the left side of the window. The Management Connectors page appears, which shows the installed connectors.
Click on the Configure icon associated with the Netcool/OMNIbus Connector.
Click the General tab.
Select and copy the URL specified for the createEvent operation.
Open an internet browser on the system where the Oracle Enterprise Manager server is installed.
In the address window, enter the URL that was copied in step 6 above. Add ?wsdl to the end of the URL. The URL should appear similar to the following example:
http://[Hostname]:8080/services/omnibus/EventService?wsdl
Where [Hostname] is the actual host name or IP address where the Netcool/OMNIbus web service is installed.
If the WSDL is loaded, this confirms that the URL is correct. If it fails to load, there is a problem with the URL. Perform the steps specified in Using the Correct URL for Netcool/OMNIbus Web Service Operations to configure the connector to use the correct URL.
The web service could not insert the event into Netcool/OMNIbus because it could not connect to the Netcool/OMNIbus server. This problem could be caused for one of the following reasons:
The Netcool/OMNIbus server is down.
The Netcool/OMNIbus server hostname/IP address or port number is not configured correctly for the Netcool/OMNIbus web service.
A network outage is preventing the Netcool/OMNIbus web service from connecting to the Netcool/OMNIbus server.
To determine and correct the root cause of the problem:
Open a command terminal on the system where the Netcool/OMNIbus web service is installed.
Change the working directory to the adapters/conf directory in the Netcool/OMNIbus web service installation directory.
Edit the framework.properties file with a text editor.
Search for the omnibus.sql.url parameter. This parameter specifies the hostname/IP address to use when connecting to the Netcool/OMNIbus API server.
Verify that the host name or IP address is correct. If the hostname/IP address appears to be correct, try to ping the system where the Netcool/OMNIbus web service is installed using the hostname/IP address. If the ping fails, the system administrator needs to investigate why there is no connectivity.
If the hostname/IP address is valid and reachable, and the port number is correct, the Netcool/OMNIbus server must be down.
To start Netcool/OMNIbus server use
emctl start oms
The web service received the request and successfully sent the request to the TEC EIF probe. The web service timed out waiting for Netcool/OMNIbus to send a notification that the requested alert that was created/updated. This error occurs because Netcool/OMNIbus is not properly configured to send the response to the web service.
Listed below is a summary of the sequence of events that occur whenever an event is created/updated in Netcool/OMNIbus.
Enterprise Manager makes a web service call for a create/update operation.
The web service makes an API call to the EIF probe to insert an event.
The EIF Probe inserts a row in the custom.oracle_status table for the event.
The oracle_insert_alert trigger fires and creates/updates the appropriate alert in the alerts.status, alerts.details, and alerts.journal database tables.
The oracle_alert_created, oracle_alert_reinserted, or oracle_alert_updated trigger fires calling the oracle_send external procedure.
The oracle_send external procedure calls the oracle_send.cmd (Windows) or oracle_send.sh (Unix) script to send a notification to the web service.
The oracle_send.cmd/oracle_send.sh script calls the universal agent utility (uniagt.exe) to send the notification to the web service.
Upon receipt of the notification, the web service makes a JDBC call to retrieve field information for the alert.
The web service sends a response to Enterprise Manager with the alert information.
A failure in steps 3 through 8 results in a timeout being reported by the web service for Netcool/OMNIbus.
Perform the following steps to identify the location of the failure:
Verify that the Object Server and EIF Probe are operational. Correct any issues that are found and retry.
Open the Netcool/OMNIbus console and determine whether an alert was created/updated.
If the alert was NOT created/updated, the failure occurred in Cause step 3 or 4. Perform the following steps to determine the reason for the failure:
Check the EIF Probe log file for errors. If there are errors, you will need to determine the cause of the error and fix the problem. Most likely the error will be caused by a lack of connectivity between the probe system and the object server system.
If there are no errors in the EIF Probe log file, verify that a row was added to the custom.oracle_status table for the event. If a row was not added, there must be a problem with the configuration of the EIF probe. Enable debug in the EIF Probe and run another test. Look in the EIF Probe log file to see if there is any information about what the probe did with the event.
If a row was added to the custom.oracle_status table, examine the ErrorMessage column for any error information.
Examine the object server log file to verify that the oracle_insert_alert trigger fired. If the trigger did not fire, open the definition for the trigger and verify it is enabled.
If the trigger fired, look for any errors that occurred while running the trigger.
If the alert was created/updated, the failure occurred somewhere in Cause steps 5 through 8. Perform the following steps to determine the reason for the failure:
Examine the object server log file to verify that one of the oracle_alert_created, oracle_alert_reinserted, or oracle_alert_updated triggers fired. If none of the triggers fired, open the definition for the triggers and look for anything that might prevent the trigger from firing. One possibility is that the trigger has been disabled.
If one of the triggers fired, look for any errors that occurred while running the trigger. If there are no errors in the object server log, you will need to enable debug in the script to see if it is being called. Step c below gives instructions for enabling debug in a Windows environment and step d gives instructions for enabling debug in a Unix environment.
For Windows environments, perform the following steps to enable debug in the notification script.
Open the oracle_send.cmd script with a text editor.
Uncomment the following lines by removing the REM at the beginning of the line:
echo %DATE% %TIME% %* >> "%AGENT_DIR%\oracle_send.out" "%AGENT_DIR%\bin\uniagt" -r %OMNIBUS_WS_URL% -v 1 -O "%AGENT_DIR%\agent%1.log"
Comment the following line by prepending REM to the beginning of the line:
"%AGENT_DIR%\bin\uniagt" -r %OMNIBUS_WS_URL%
Save the file and exit.
For Unix environments, perform the following steps to enable debug in the notification script:
Open the oracle_send.sh script with a text editor.
Uncomment the following lines by removing the # at the beginning of the line:
echo `date` $* >> ${AGENT_DIR}/oracle_send.out
${AGENT_DIR}/bin/uniagt -r ${OMNIBUS_WS_URL} -v 1 -O ${AGENT_DIR}/agent/{1}.log
Comment the following line by prepending # to the beginning of the line:
${AGENT_DIR}/bin/uniagt -r ${OMNIBUS_WS_URL}
Save the file and exit.
After enabling debug, run another test and determine whether the oracle_send.out log file was created. If the file was created, open it with a text editor and look at the last line in the file to get the serial number. The line starts with the date/time the script was called followed by the serial number and the name of the trigger that fired.
Verify that an agent log was created for the serial number. The agent log should be named agent<serialno>.log where <serialno> is the serial number from the oracle_send.out log file.
If the file exists, open it with a text editor and look for errors sending to the web service. If errors occur, it will likely be caused by a connectivity issue or an invalid URL specified in the OMNIBUS_WS_URL environment variable. Check the hostname/IP address and port number in the URL. Unless specifically changed, the port number should be 8080. If the notification was sent successfully, you will see something similar to the following in the log.
2012/06/13 11:20:52 response headers: <HTTP/1.1 200 OK Content-Type: text/xml Content-Length: 0 Server: Jetty(6.1.14)
If the agent log indicates the notification was successfully sent to the web service, look in the web service log for errors. The web service log is located in the adapters/log directory of the web service installation directory and is named framework.log. Most likely the error will be caused by a failure to connect to the database to retrieve the alert information.
The web service could not insert the event into Netcool/OMNIbus because it could not connect to the Netcool/OMNIbus probe.
Open a command terminal on the system where the Netcool/OMNIbus web service is installed.
Change the working directory to the adapters/conf directory in the Netcool/OMNIbus web service installation directory.
Edit the framework.properties file with a text editor.
Search for the omnibus.probe.master.t_ServerLocation parameter. This parameter specifies the server name where Netcool/OMNIbus probe is located.
Verify that the server name is correct.
Search for the omnibus.probe.master.t_Port parameter. This parameter specifies the port where Netcool/OMNIbus probe is located.
Verify that the port number is correct.
This section provides cause and solution information on troubleshooting common alert messages. Find the error message in Table 5-2 that matches your error message, then refer to the corresponding section(s) indicated under Possible Cause for instructions to diagnose and correct the problem.
Table 5-2 Netcool/OMNIbus Error Messages
| Alert Message | Possible Cause | Applicable Versions |
|---|---|---|
|
The server sent HTTP status code 403: Forbidden |
11.1.0.1 |
|
|
Certificate chain received from <hostname> - <IPAddress> was not trusted causing SSL handshake failure. |
11.1.0.1 |
|
|
Tried all: 1 addresses, but could not connect over HTTPS to server: <IPAddress> port: <port> |
11.1.0.1 |
|
|
HTTP transport error: java.net.SocketException: Socket Closed |
11.1.0.1 |
|
|
HTTP transport error: java.net.UnknownHostException: <hostname> |
11.1.0.1 |
|
|
The server sent HTTP status code 404: Not Found |
11.1.0.1 |
The user name or password for accessing the Netcool/OMNIbus web service is incorrect.
Log in to the Oracle Enterprise Manager console by entering a user name with a "Super Administrator" role, entering the appropriate password, then clicking Login.
Click the Setup link at the top right part of the window. The Overview of Setup page appears.
Click the Management Connectors link on the left side of the window. The Management Connectors page appears, which shows the installed connectors.
Click on the Configure icon associated with the Netcool/OMNIbus Connector.
Click the General tab.
Correct the Netcool/OMNIbus Web Service Username and Netcool/OMNIbus Web Service Password fields and click OK.
The SSL handshake between the Oracle Enterprise Manager Connector Framework and the Netcool/OMNIbus web service failed. This failure occurs when the SSL certificate in the certificate store does not match the SSL certificate that the Netcool/OMNIbus web service provides.
You need to import the SSL certificate from the Netcool/OMNIbus web service into the certificate store. See Adding Signed Certificates to Enterprise Manager for details on setting up Oracle Enterprise Manager with the Netcool/OMNIbus SSL certificate.
The Netcool/OMNIbus web service is down.
Perform the following steps to check the status of the web service and start it if necessary.
If the Netcool/OMNIbus web service is installed on a Unix system:
Open a command terminal on the system where the Netcool/OMNIbus web service is installed.
Change the working directory to the adapters/bin directory in the Netcool/OMNIbus web service installation directory.
Enter the following command:
./service.sh status
If the command indicates that the service is not running, enter the following command:
./service.sh start
If the Netcool/OMNIbus web service is installed on a Windows system:
Open a command terminal on the system where the Netcool/OMNIbus web service is installed.
Change the working directory to the adapters/log directory in the Netcool/OMNIbus web service installation directory.
Open the framework.log file in a text editor.
Go to the bottom of the file and search backwards for the string iWave Adapter Framework. If the last occurrence found is iWave Adapter Framework Started, this indicates that the web service is started.
If the web service is not started, start the web service based on how the web service is installed.
If it is installed as a standalone application, change the working directory to the adapters/bin directory and run the startAdapters.bat command file.
If it is installed as a Windows service, enter the net start iWaveAdapters command.
If the web service is not down, there must be a problem with the port number. Perform the steps specified in Using the Correct URL for Netcool/OMNIbus Web Service Operations to identify the correct URL, including the port number.
The port number in the URL is incorrect.
Perform the steps specified in Using the Correct URL for Netcool/OMNIbus Web Service Operations to identify the correct URL, including the port number.
The system does not recognize the host name specified in the URL.
Select one of the following options to address this issue:
Coordinate with the system administrator to change the system configuration to recognize the host name.
Specify the IP address in the URL instead of the host name. To do this, perform the following steps:
Determine the IP address of the system where the Netcool/OMNIbus web service is installed.
Log in to the Oracle Enterprise Manager console by entering a user name with a "Super Administrator" role, entering the appropriate password, then clicking Login.
Click the Setup link at the top right part of the window. The Overview of Setup page appears.
Click the Management Connectors link on the left side of the window. The Management Connectors page appears, which shows the installed connectors.
Click on the Configure icon associated with the IBM Netcool/OMNIbus Connector. This invokes edit mode, enabling you to configure the connector.
Change the host name to the IP address in the URL specified for the getNewAlerts, getUpdatedAlerts, and acknowledgeAlerts operations.
Click OK.
The IP address specified in the URL is invalid, or the network is down.
Verify that the hostname/IP address configured for the connector is correct:
Log in to the Oracle Enterprise Manager console by entering a user name with a "Super Administrator" role, entering the appropriate password, then clicking Login.
Click the Setup link at the top right part of the window. The Overview of Setup page appears.
Click the Management Connectors link on the left side of the window. The Management Connectors page appears, which shows the installed connectors.
Click on the Configure icon associated with the Netcool/OMNIbus Connector. This invokes edit mode, enabling you to configure the connector.
Verify that the hostname/IP address specified in the URL for the getNewAlerts, getUpdatedAlerts, and acknowledgeAlerts operations are correct.
If the hostname/IP address is incorrect, provide the correct values and click OK.
If the URLs specify a host name, make sure that the host name resolves to the correct IP address. To determine the IP address of the host name, issue the ping <hostname> command, where <hostname> is the actual host name. This lists the IP address that was resolved for the host name. If this is incorrect, the system administrator needs to investigate why it is incorrect.
If the hostname/IP address appears to be correct, try to ping the system where the Netcool/OMNIbus web service is installed using the hostname/IP address. If the ping fails, the system administrator needs to investigate why there is no connectivity.
The URL hostname/IP address and port numbers are correct, but there is an invalid path.
Perform the steps specified in Using the Correct URL for Netcool/OMNIbus Web Service Operations to identify the correct URL, including the port number.