| Oracle® Web Services Manager Deployment Guide 10g (10.1.3.3.0) Part Number E10298-01 |
|
|
View PDF |
| Oracle® Web Services Manager Deployment Guide 10g (10.1.3.3.0) Part Number E10298-01 |
|
|
View PDF |
This appendix provides information for troubleshooting your Oracle Web Services Manager (Oracle WSM) deployment.
Problem
You install Oracle WSM and start Oracle Application Server. The following error appears in the ORACLE_HOME/j2ee/instance/log/gateway.log file:
Failed to retrieve policy set from policy manager with url
@ http://host_name:port_number/policymanager/services/RegistrationService: com.cfluent.policymanager.sdk.base.exception.ServerException: java.lang.Exception: Invalid component ID - C0003001"
(In the path to the gateway.log file, the variable instance is the name of the OC4J instance into which Oracle WSM is installed. If you install the standalone version of Oracle WSM, the default value of the instance is home.)
Solution
By default, at the time you install Oracle WSM, the component ID for the gateway is set to C0003001 in the gateway-config-installer.properties file. Therefore, when you start Oracle Application Server, the Oracle WSM tries to retrieve the policies for the C0003001 component. Because the gateway has not yet been created, the policies cannot be retrieved and an error is logged.
Log in to Web Services Manager Control, and add a gateway to Oracle WSM. Make the gateway the first policy enforcement point you create. This component will be assigned the component ID C0003001. Once the component has been added, the error message will no longer appear.
Problem
You log in to the Web Services Manager Control and get the following error:
The following exception occurred when processing the JSP: org.xml.sax.SAXException: Bad envelope tag: HTML Use your browsers "Back" button if you would like to try again.
Solution
This is a known bug that occurs after you deploy the Oracle WSM Policy Manager. Restart the Oracle Process Manager and Notification Server (OPMN) process (opmnctl restartproc) on the OC4J instance where the Oracle WSM components are installed. Then retry logging in to Web Services Manager Control.
