To diagnose the problem:
Verify that the OMU Web service has been successfully started and the WSDL for the OMU Web service can be accessed from the system where the OMU Web service is installed. Perform the following steps to do this:
Perform the steps in Using the Correct URL for OMU Web Service Operations to determine the URL used by the OMU Web Service.
Open a browser and paste the URL from the previous step in the address window. Append ?WSDL to the end of the URL and attempt to load the URL.
The WSDL should be loaded if the Adapter is operational.
Note:
A WSDL is an XML file that describes the web service.
If the WSDL cannot be loaded, this indicates the Web service had startup issues. See Troubleshooting Web Service Startup Errors to diagnose the problem.
Verify that the WSDL for the OMU Web service can be accessed from the system where the Enterprise Manager server is installed.
Open a browser at the Enterprise Manager server and copy the URL from step 1-b above to the address window. The host name for the URL will be localhost. Change localhost to the actual host name or IP address of the system where the OMU Web service is installed. If you specify a host name, make sure that the host name is recognized at the Enterprise Manager server system. This can be done using the ping command.
For example, if the OMU Web service is installed on the server with a host name of SDServer01 and the URL listed in framework.log is:
http://localhost:8080/services/hpovou/EventService
The URL used at the Enterprise Manager server system would be:
http://OMServer01:8080/services/hpovou/EventService
Attempt to load the WSDL by appending ?WSDL at the end of the URL. If the WSDL cannot be loaded, either the host name is not recognized at the Enterprise Manager system, or there is a connectivity issue between the two systems. If you specified a host name, try using the IP address instead of the host name in the URL. If it still does not load, you have a connectivity problem. You will need to consult with your IT department to resolve this issue.
Verify that the OMU Connector specifies the correct URL for the createEvent and updateEvent operations.
Log into the Oracle Enterprise Manager console with an account that has Super Administrator permissions.
From the Setup menu of the Enterprise Manager console, select Extensibility, then Management Connectors.
The Management Connectors page appears, which shows the installed connectors.
Click on the Configure icon associated with the OMU Connector. This invokes edit mode, enabling you to configure the connector.
Verify that the URL identified in step 2-b is specified for both operations (createEvent and updateEvent). If any of the operations are incorrect, change to the correct URL.
Note:
Do not append the WSDL to the end of the URL that is specified here.
Click OK.
If no errors were found in the previous steps, this rules out connectivity issues between the connector and the OMU Web Service. The problem must originate in the OMU Web Service or the Oracle OMU Agent. See Troubleshooting Web Service Operations Errors for information on diagnosing errors.