Skip Headers
Oracle® Enterprise Manager Installation and Configuration Guide for IBM Tivoli Enterprise Console Connector
Release 1.0.4.1.0

E14038-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

5 Troubleshooting the Connector

This chapter provides information to assist in troubleshooting integration issues with IBM TEC. The chapter focuses on troubleshooting issues in the web service front-end and the back-end Agent.

This chapter discusses the following topics:

Preparing for Troubleshooting

In order to troubleshoot integration issues, you must adjust the Oracle Enterprise Manager logging options to capture additional information.

To enable debug logging information:

  1. Edit the emomslogging.properties file using a text editor. The location of the file depends on the Enterprise Manager version.

    Version 11.1.0.1

    <ORACLE_HOME>/oms11g/sysman/config
    

    Versions 10.2.0.4 and 10.2.0.5

    <ORACLE_HOME>/oms10g/sysman/config

    ... where <ORACLE_HOME> is the Oracle installation directory.

  2. Set the parameters as follows:

    log4j.appender.emlogAppender.Threshold = DEBUG log4j.rootCategory=DEBUG, emlogAppender, emtrcAppender

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

Using the Correct URL for TEC Web Service Operations

Perform the following steps to identify and configure the connector to use the correct URL for TEC Web Service operations.

  1. Open a command terminal on the system where the TEC web service is installed.

  2. Change the working directory to the adapters/log directory in the TEC web service installation directory.

  3. Open the framework.log file in a text editor.

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

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

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

  7. Click the Setup link at the top right part of the window. The Overview of Setup page appears.

  8. Click the Management Connectors link on the left side of the window. The Management Connectors page appears, which shows the installed connectors.

  9. Click on the Configure icon associated with the TEC Connector. This invokes edit mode, enabling you to configure the connector.

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

  11. Verify that the URL identified in step 5 is specified for the createEvent and updateEvent operations.

  12. If any of the operations are incorrect, change to the correct URL and click OK.

Diagnosing Problems with Event Generation and Updates

You might encounter issues involved in generating or updating events in TEC from alerts that have originated in Oracle Enterprise Manager or vice versa. The following sections provide diagnostic information to resolve these problems.

Alerts from Oracle Enterprise Manager to TEC

TEC can generate or update events from alerts that have originated in Oracle Enterprise Manager. Perform the following diagnostic steps if TEC events are not being generated or updated as expected.

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

    1. Open an Oracle Enterprise Manager console window and log in.

    2. Click on the Setup link in the upper right corner of the Oracle Enterprise Manager console.

    3. Click on the Notification Methods link on the left side of the window.

    4. Locate the TEC 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.

    5. Click on the Preferences link in the upper right corner.

    6. Click on the Notification Rules link on the left side of the window. This displays a list of all defined notification methods.

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

    8. 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 TEC notification method.

  2. Determine the error that Oracle Enterprise Manager has reported.

    1. Navigate to the page that displays the alert information that should have triggered the new event in TEC.

      For example, if the Memory Utilization % metric was set up to invoke the TEC 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 on the Alerts tab.

      2.) Click on the Critical sub-tab.

      3.) Click on the Memory Utilization % alert.

    2. 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 TEC 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.

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

      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.

      Versions 10.2.0.4 and 10.2.0.5

      $OMS_HOME/sysman/log
      

      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.

  3. Diagnose the problem based on the error event. See Section 5.4, "Resolving Alerts from Oracle Enterprise Manager" for information on troubleshooting common error events.

Events from TEC to Oracle Enterprise Manager

Oracle Enterprise Manager can generate or update alerts resulting from events that have originated in TEC. Perform the following diagnostic steps if Oracle Enterprise Manager alerts are not being generated or updated as expected.

  1. Open the $OMS_HOME/sysman/log/emoms.trc file in a text editor. The location of the file depends on the Enterprise Manager version.

    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

    Versions 10.2.0.4 and 10.2.0.5

    $OMS_HOME/sysman/log
    
  2. 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 Section 5.5, "Resolving Events from TEC" 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.

Resolving Alerts from Oracle Enterprise Manager

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

targetException=oracle.xml.parser.v2.XMLParseException: Start of root element expected

Invalid Web Service Credentials

10.2.0.4, 10.2.0.5

javax.net.ssl.SSLException: SSL handshake failed: X509CertChainInvalidErr

SSL Not Configured in Enterprise Manager

10.2.0.4, 10.2.0.5

The wallet "/gc/OracleHomes/oms10g/sysman/connector//certdb.txt" does not exist

Missing certdb.txt File

10.2.0.4, 10.2.0.5

Error opening socket: java.net.ConnectException: Connection refused

TEC Web Service Is Down

10.2.0.4, 10.2.0.5

Error opening socket: java.net.UnknownHostException: <hostname>

Unknown Host

10.2.0.4, 10.2.0.5

Error opening socket: java.net.NoRouteToHostException: No route to host

Invalid IP Address or Port Number

10.2.0.4, 10.2.0.5

SOAPException: faultCode=SOAP-ENV:Protocol; msg=Unsupported response content type &quot;text/html;

Invalid URL Path

10.2.0.4, 10.2.0.5

Error occurred while calling Web Service: soap:ServerAttempt to insert the event into TEC failed

TEC Server Not Operational

10.2.0.4, 10.2.0.5

Error occurred while calling Web Service: soap:ServerTimeout occurred waiting for synchronous response from TEC after inserting an event

TEC Server Timeout

10.2.0.4, 10.2.0.5

The server sent HTTP status code 403: Forbidden

Invalid Web Service Credentials

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.

SSL Not Configured in Oracle Enterprise Manager

11.1.0.1

HTTP transport error: java.net.SocketException: Socket Closed

TEC Web Service is Down, Invalid IP Address or Port Number

11.1.0.1

HTTP transport error: java.net.UnknownHostException: <hostname>

Unknown Host

11.1.0.1

The server sent HTTP status code 404: Not Found

Invalid URL Path

11.1.0.1

javax.xml.ws.soap.SOAPFaultException: Attempt to insert the event into TEC failed

TEC Server Not Operational

11.1.0.1

javax.xml.ws.soap.SOAPFaultException: Timeout occurred waiting for synchronous response from TEC after inserting an event

TEC Server Timeout

11.1.0.1


Invalid Web Service Credentials

Cause

The user name or password for accessing the TEC web service is incorrect.

Solution

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

  2. Click the Setup link at the top right corner of the window. The Overview of Setup page appears.

  3. Click the Management Connectors link on the left side of the window. The Management Connectors page appears, which shows the installed connectors.

  4. Click on the Configure icon associated with the TEC Connector.

  5. Click the General tab.

  6. Correct the TEC Web Service Username and TEC Web Service Password fields, then click OK.

SSL Not Configured in Enterprise Manager

Cause

The SSL handshake between the Oracle Enterprise Manager Connector Framework and the TEC web service failed. This failure occurs because Oracle Enterprise Manager is not configured correctly with the SSL certificate for the TEC web service. The SSL certificate the TEC 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 TEC web service.

Solution

Import the SSL certificate from the TEC web service into the certificate store. See Section 2.2.3, "Adding Signed Certificates to Enterprise Manager" on page 2-7 for details on setting up Oracle Enterprise Manager with the TEC SSL certificate.

Missing certdb.txt File

Cause

The TEC web service is configured to use SSL, but the certdb.txt file that contains the SSL information is missing.

Solution

Import the SSL certificate from the TEC web service into the wallet manager. See Section 2.2.3, "Adding Signed Certificates to Enterprise Manager" on page 2-7 for details on setting up Oracle Enterprise Manager with the TEC SSL certificate.

TEC Web Service Is Down

Cause

The TEC web service is down.

Solution

Perform the following steps to check the status of the web service and start it if necessary.

If the TEC web service is installed on a Unix system:

  1. Open a command terminal on the system where the TEC web service is installed.

  2. Change the working directory to the adapters/bin directory in the TEC web service installation directory.

  3. Enter the following command:

    ./service.sh status

  4. If the command indicates that the service is not running, enter the following command:

    ./service.sh start

If the TEC web service is installed on a Windows system:

  1. Open a command terminal on the system where the TEC web service is installed.

  2. Change the working directory to the adapters/log directory in the TEC web service installation directory.

  3. Open the framework.log file in a text editor.

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

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

Unknown Host

Cause

The system does not recognize the host name specified in the URL.

Solution

You can use the following options to address this issue:

Invalid IP Address or Port Number

Cause

The IP address or port number specified in the URL is invalid, or the network is down.

Solution

Verify that the hostname/IP address configured for the connector is correct:

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

  2. Click the Setup link at the top right part of the window. The Overview of Setup page appears.

  3. Click the Management Connectors link on the left side of the window. The Management Connectors page appears, which shows the installed connectors.

  4. Click on the Configure icon associated with the TEC Connector. This invokes edit mode, enabling you to configure the connector.

  5. Verify that the hostname/IP address and port number specified in the URL for the createEvent and updateEvent operations are correct.

  6. 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 TEC web service is installed using the hostname/IP address. If the ping fails, the system administrator needs to investigate why there is no connectivity.

Invalid URL Path

Cause

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.

Solution

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 depends on the Enterprise Manager version. For 11.1.0.1, the file is located at <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. For 10.2.0.5, the file is located at $OMS_HOME/sysman/log.

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. Perform the following steps to test the URL the connector is using.

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

  2. Click the Setup link at the top right part of the window. The Overview of Setup page appears.

  3. Click the Management Connectors link on the left side of the window. The Management Connectors page appears, which shows the installed connectors.

  4. Click on the Configure icon associated with the TEC Connector.

  5. Click the General tab.

  6. Select and copy the URL specified for the createEvent operation.

  7. Open an internet browser on the system where the Oracle Enterprise Manager server is installed.

  8. 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/tec/EventService?wsdl

    [Hostname] is the actual host name or IP address where the TEC 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 Section 5.2, "Using the Correct URL for TEC Web Service Operations" to configure the connector to use the correct URL.

TEC Server Not Operational

Cause

The web service could not insert the event into TEC because it could not connect to the TEC server. This problem could be caused for one of the following reasons:

Solution

Perform the following steps to determine and correct the root cause of the problem:

  1. Open a command terminal on the system where the TEC web service is installed.

  2. Change the working directory to the adapters/conf directory in the TEC web service installation directory.

  3. Edit the framework.properties file with a text editor.

  4. Search for the tec.server1.config.t_ServerLocation parameter. This parameter specifies the hostname/IP address to use when connecting to the TEC API server.

  5. 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 TEC web service is installed using the hostname/IP address. If the ping fails, the system administrator needs to investigate why there is no connectivity.

  6. Search for the tec.server1.config.t_Port parameter. This parameter specifies the port number to use when connecting to the TEC API server.

  7. Verify that the port number is correct. If the TEC server is running on a Unix machine with a port mapper, the port number should be set to 0. If the TEC server is running on a Windows system or Unix system without a port mapper, the port number must be set to the TEC reception port.

    Note:

    The TEC reception port is defined by the tec_recv_agent_port parameter in the .tec_config file in the $BINDIR/TME/TEC directory.

    If the hostname/IP address is valid and reachable, and the port number is correct, the TEC server must be down.

  8. To check the status of the TEC server, open a command terminal on the system where the TEC server is installed.

  9. Set up the TEC environment.

    • For Windows systems, enter the following commands to start the bash shell:

      %SystemRoot%\system32\drivers\etc\Tivoli\setup_env.cmd

      bash

    • For Unix systems, enter the following command to set the TEC environment variables:

      /etc/Tivoli/setup_env/sh

  10. Enter the following command to display the status of the TEC server:

    wstatesvr

  11. If the TEC server is down, contact your TEC system administrator to start the server.

TEC Server Timeout

Cause

The web service successfully sent the event to the TEC server, but did not receive a response in the time-out period. This problem could be caused for one of the following reasons:

Solution

Perform the following steps to determine and correct the root cause of the problem.

  1. Open a command terminal on the system where the TEC server is installed.

  2. Set up the TEC environment.

    • For Windows systems, enter the following commands to start the bash shell:

      %SystemRoot%\system32\drivers\etc\Tivoli\setup_env.cmd

      bash

    • For Unix systems, enter the following command to set the TEC environment variables:

      /etc/Tivoli/setup_env.sh

  3. Enter the following command to display the most recent entries in the TEC server log:

    wtdumprl –o DESC | more

  4. Locate the entry for the event that timed out, and verify that the log indicates that it was processed. If an error appears, it explains what is incorrect with the data. You will need to modify the mapping to fix the problem. See Section 4.1.3, "Changing a Mapping" for additional information.

  5. If the log indicates that TEC successfully processed the data, you need to verify that the TEC rule base invoked the tec2uniagt script located in the TEC Agent installation directory. Consult with your TEC administrator for information on setting up and viewing the rule logs.

Resolving Events from TEC

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 diagnos and correct the problem.

Table 5-2 TEC Error Messages

Error Message Possible Cause Applicable Versions

targetException=oracle.xml.parser.v2.XMLParseException: Start of root element expected.

Invalid Web Service Credentials

10.2.0.4, 10.2.0.5

SOAPException: faultCode=SOAP-ENV:IOException; msg=javax.net.ssl.SSLException: SSL handshake failed: X509CertChainInvalidErr

SSL Not Configured in Enterprise Manager

10.2.0.4, 10.2.0.5

SOAPException: faultCode=SOAP-ENV:IOException; msg=The wallet &quot;/gc/OracleHomes/oms10g/sysman/connector//certdb.txt&quot; does not exist

Missing certdb.txt File

10.2.0.4, 10.2.0.5

java.lang.Exception: Error occurred while calling Web Service

Invalid XML Format

10.2.0.4, 10.2.0.5

SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: java.net.ConnectException: Connection refused;

TEC Web Service IsDown, Invalid Port Number

10.2.0.4, 10.2.0.5

SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: java.net.UnknownHostException: <hostname>;

Unknown Host

10.2.0.4, 10.2.0.5

SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: java.net.NoRouteToHostException: No route to host;

Invalid IP Address

10.2.0.4, 10.2.0.5

SOAPException: faultCode=SOAP-ENV:Protocol; msg=Unsupported response content type

Invalid URL Path

10.2.0.4, 10.2.0.5

The server sent HTTP status code 403: Forbidden

Invalid Web Service Credentials

11.1.0.1

Certificate chain received from <hostname> - <IPAddress> was not trusted causing SSL handshake failure.

SSL Not Configured in Oracle Wallet Manager

11.1.0.1

Tried all: 1 addresses, but could not connect over HTTPS to server: <IPAddress> port: <port>

TEC Web Service Is Down

11.1.0.1

HTTP transport error: java.net.SocketException: Socket Closed

Invalid Port Number, Invalid IP Address

11.1.0.1

HTTP transport error: java.net.UnknownHostException: <hostname>

Unknown Host

11.1.0.1

The server sent HTTP status code 404: Not Found

Invalid URL Path

11.1.0.1


Invalid Web Service Credentials

Cause

The user name or password for accessing the TEC web service is incorrect.

Solution

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

  2. Click the Setup link at the top right part of the window. The Overview of Setup page appears.

  3. Click the Management Connectors link on the left side of the window. The Management Connectors page appears, which shows the installed connectors.

  4. Click on the Configure icon associated with the TEC Connector.

  5. Click the General tab.

  6. Correct the TEC Web Service Username and TEC Web Service Password fields and click OK.

SSL Not Configured in Oracle Enterprise Manager

Cause

The SSL handshake between the Oracle Enterprise Manager Connector Framework and the TEC web service failed. This failure occurs when the SSL certificate in the certificate store does not match the SSL certificate that the TEC web service provides.

Solution

You need to import the SSL certificate from the TEC web service into the certificate store. See Section 2.2.3, "Adding Signed Certificates to Enterprise Manager" on page 2-7 for details on setting up Oracle Enterprise Manager with the TEC SSL certificate.

Missing certdb.txt File

Cause

The TEC web service is configured to use SSL, but the certdb.txt file that contains the SSL information is missing.

Solution

You need to import the SSL certificate from the TEC web service into the wallet manager. See Section 2.2.3, "Adding Signed Certificates to Enterprise Manager" on page 2-7 for details on setting up Oracle Enterprise Manager with the TEC SSL certificate.

TEC Web Service is Down

Cause

The TEC web service is down.

Solution

Perform the following steps to check the status of the web service and start it if necessary.

If the TEC web service is installed on a Unix system:

  1. Open a command terminal on the system where the TEC web service is installed.

  2. Change the working directory to the adapters/bin directory in the TEC web service installation directory.

  3. Enter the following command:

    ./service.sh status

  4. If the command indicates that the service is not running, enter the following command:

    ./service.sh start

If the TEC web service is installed on a Windows system:

  1. Open a command terminal on the system where the TEC web service is installed.

  2. Change the working directory to the adapters/log directory in the TEC web service installation directory.

  3. Open the framework.log file in a text editor.

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

  5. 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 Section 5.2, "Using the Correct URL for TEC Web Service Operations" to identify the correct URL, including the port number.

Invalid Port Number

Cause

The port number in the URL is incorrect.

Solution

Perform the steps specified in Section 5.2, "Using the Correct URL for TEC Web Service Operations" to identify the correct URL, including the port number.

Invalid XML Format

Cause

The request sent to the TEC web service was rejected because the XML was formatted incorrectly. This problem should not occur unless the connector configuration XML files are manually updated.

Solution

Look at the error event in the fault string node of the SOAP fault response and determine what is incorrect in the request document. Examine any changes made to the XML configuration files for mistakes that could have caused the problem. You can determine the correct XML format by accessing the WSDL using a web browser.

Perform the following steps to access the WSDL:

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

  2. Click the Setup link at the top right part of the window. The Overview of Setup page appears.

  3. Click the Management Connectors link on the left side of the window. The Management Connectors page appears, which shows the installed connectors.

  4. Click on the Configure icon associated with the TEC Connector.

  5. Click the General tab.

  6. Select and copy the URL specified for the getNewAlerts operation.

  7. Open an internet browser on the system where the Oracle Enterprise Manager server is installed.

  8. 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/tec/EventService?wsdl

    [Hostname] is the actual host name or IP address where the TEC web service is installed.

If you cannot determine why the format is incorrect, contact Oracle for support.

Unknown Host

Cause

The system does not recognize the host name specified in the URL.

Solution

Select one of the following options to address this issue.

Invalid IP Address

Cause

The IP address specified in the URL is invalid, or the network is down.

Solution

Verify that the hostname/IP address configured for the connector is correct:

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

  2. Click the Setup link at the top right part of the window. The Overview of Setup page appears.

  3. Click the Management Connectors link on the left side of the window. The Management Connectors page appears, which shows the installed connectors.

  4. Click on the Configure icon associated with the TEC Connector. This invokes edit mode, enabling you to configure the connector.

  5. Verify that the hostname/IP address specified in the URL for the getNewAlerts, getUpdatedAlerts, and acknowledgeAlerts operations are correct.

  6. If the hostname/IP address 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 TEC web service is installed using the hostname/IP address. If the ping fails, the system administrator needs to investigate why there is no connectivity.

Invalid URL Path

Cause

The URL hostname/IP address and port numbers are correct, but there is an invalid path.

Solution

Perform the steps specified in Section 5.2, "Using the Correct URL for TEC Web Service Operations" to identify the correct URL, including the port number.