Document Transfer Utility GenericSoapPort Fails (Doc ID 1991616.1)

Last updated on MARCH 05, 2024

Applies to:

Symptoms

On: 11.1.9.0.0 version, Using Oracle Document Transfer Utility

Client is using an automated method to upload data.  This method uses the Oracle Document Transfer Utility GenericSoapService, oracle.ucm.fa_genericclient_11.1.1.jar.  It works successfully sometimes.  The process fails ~50% of the time.

ERROR
-----------------------

Error - oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid: WSM-02017 oracle.wsm.policymanager.accessor.ClasspathAccessor The document "/policies/policy=oracle/wss_username_token_client_policy" does not exist in the repository.

javax.xml.ws.WebServiceException: oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid: WSM-02017 oracle.wsm.policymanager.accessor.ClasspathAccessor The document "/policies/policy=oracle/wss_username_token_client_policy" does not exist in the repository.

        at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:880)
        at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:235)
        at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:106)
        at oracle.j2ee.ws.client.jaxws.WsClientProxyInvocationHandler.invoke(WsClientProxyInvocationHandler.java:254)
        at com.sun.proxy.$Proxy26.genericSoapOperation(Unknown Source)

        at oracle.ucm.idcws.client.AbstractTool.sendRequest(AbstractTool.java:903)
        at oracle.ucm.idcws.client.AbstractTool.ping(AbstractTool.java:651)
        at oracle.ucm.idcws.client.AbstractTool.ping(AbstractTool.java:638)
        at oracle.ucm.idcws.client.UploadTool.run(UploadTool.java:147)
        at oracle.ucm.idcws.client.UploadTool.main(UploadTool.java:101)
Caused by: oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid: WSM-02017 oracle.wsm.policymanager.accessor.ClasspathAccessor The document "/policies/policy=oracle/wss_username_token_client_policy" does not exist in the repository.
        at oracle.integration.platform.common.InterceptorChainImpl.createPolicyEnforcementException(InterceptorChainImpl.java:306)
        at oracle.integration.platform.common.InterceptorChainImpl.processRequest(InterceptorChainImpl.java:152)
        at oracle.integration.platform.common.mgmt.InterceptorChainManager.processRequest(InterceptorChainManager.java:276)
        at oracle.j2ee.ws.client.mgmt.runtime.SuperClientInterceptorPipeline.handleRequest(SuperClientInterceptorPipeline.java:96)
        at oracle.j2ee.ws.client.jaxws.DispatchImpl.handleRequest(DispatchImpl.java:625)
        at oracle.j2ee.ws.client.jaxws.DispatchImpl.handleRequest(DispatchImpl.java:603)
        at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:819)
        ... 9 more
-----------------

This is a system with scaled out nodes.  There are two nodes on the system.

Test the system by going to the WSDL in a browser:  https://<POD_NAME>.fs.<Data_Center>.oraclecloud.com/idcws/GenericSoapPort?WSDL

Verify the correct policy is returned:  PolicyReference URI="#wss11_saml_or_username_token_with_message_protection_service_policy" wsdl:required="false"

If the policy is "wss_saml_bearer_or_username_token_service_policy" it is incorrect.

Testing going to the URL several times should hit both nodes.  The Load Balancer should send 50% of the load to each node.  If the system has more than two nodes you may need to test the WSDL endpoint many times to verify the correct policy is in place.

Changes

 Release 13 was installed on the primary node and the scaled out node.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.