C Troubleshooting OracleAS Web Services

C.1.1 Receiving "Unsupported Response Content Type" Error

Invoking a Web service produces an "unsupported response content type" error.

Problem

A likely cause of the error is that the URI address of the endpoint in the stub or dynamic proxy is incorrect. With an incorrect URI address, the client receives a native HTTP response without a SOAP payload which results in an "unsupported response content type" error.

Solution

Ensure that the URI address is correct.

C.1.2 Cannot Publish Doc/Literal in JDeveloper

Web service cannot publish doc/literal in JDeveloper 9.0.3/9.0.4/9.0.5.1.

Problem

Trying to publish doc/literals without using Stateless Java Classes and JMS destinations.

Solution

Since Oracle Application Server 9.0.3, Oracle Application Server Web Services has supported doc/literal operations using Stateless Java Classes and JMS destinations. Information for this support is available in the Oracle Application Server documentation at:

http://download-west.oracle.com/docs/cd/B10464_02/web.904/b10447/docservices.htm#sthref259

C.1.3 Cannot Register Web Service

When deploying a Web service, using Oracle Application Server Control, the Web service cannot be registered in the Oracle Application Server UDDI Registry.

Problem

Although the button to register the service appears, it is not enabled. This problem often indicates that you have not installed the Oracle Application Server Portal. The Oracle Application Server UDDI Server is a J2EE servlet application that is deployed automatically by the Oracle Application Server Installer into the same J2EE OC4J container as the Oracle Application Server Portal.

Solution

Install the Oracle Application Server Portal. After installation, you must ping the servlet at least once to initialize the registry and enable the Application Server Control UDDI user interface.

C.1.4 UDDI Registry Screens Missing

The Oracle Application Server UDDI Registry screens in the Application Server Control are missing.

Problem

This problem indicates that the Oracle Application Server Portal is not installed. Requiring that the Oracle Application Server Portal be installed, before the Oracle Application Server UDDI Registry screens become available, ensures that customers have the Oracle Application Server MetaData Repository installed, which is a pre-requisite for Oracle Application Server UDDI management.

Solution

Install the Oracle Application Server Portal. After installation, you must ping the servlet at least once to initialize the registry and enable the Application Server Control UDDI user interface.

C.1.5 UDDI Management Screens Are Not Enabled

The Oracle Application Server Control UDDI management screens are not enabled.

Problem

The Oracle Application Server Control UDDI management screens are not enabled. The Oracle Application UDDI Registry is installed on another instance of Oracle Application Server.

Solution

The Oracle Application UDDI Registry must be installed in the same instance of Oracle Application Server as the Oracle Application Server Control UDDI management screens for the screens to be enabled.

C.2.1 Generating Web Services Diagnostic Messages

To obtain diagnostic information specific to Web services, set the system property ws.debug to True.

• To set ws.debug in an OC4J standalone version, at the command line enter:

  java Dws.debug=true ... -jar oc4j.jar
  
  

• For the OC4J Java, Standard, or Enterprise editions, ws.debug can be set from within the Oracle Application Server Control. From the Administration tab of the OC4J instance where the Web service is deployed, navigate to the Server properties link. In the Java options text field, add:

  Dws.debug=true
  
  

The diagnostic messages are located in the redirected output/errors log. You can find the log in the Log Viewer Application Server Control screens.