Facing "Error WSM-06102
PolicyReference" while invoking Imaging document service in Imaging
Problem statement:
We are facing an error while SOA invoking Imaging
document service to unlock the document method.
[2016-04-21T02:37:17.316-07:00] [soa_server1] [ERROR] [] [oracle.integration.platform.blocks.soap] [tid: orabpel.invoke.pool-4.thread-4] [userId: <anonymous>] [ecid: fe4f6d542a73d759:224403c:154381e41c9:-8000-0000000000000cab,1:17052] [APP: soa-infra] [composite_name: senaUpdateDocument] [component_name: senaUpdateDocument] [component_instance_id: 2480007] Unable to dispatch request to http://bali.sdsu.edu:16000/imaging/ws/DocumentService due to exception[[
oracle.fabric.common.FabricInvocationException: Unable to access the following endpoint(s): http://bali.sdsu.edu:16000/imaging/ws/DocumentService
at oracle.integration.platform.blocks.soap.AbstractWebServiceBindingComponent.dispatchRequest(AbstractWebServiceBindingComponent.java:592)
……..
Caused by: javax.xml.ws.WebServiceException: oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid: WSM-06102 The same code is working in DEV and PROD. We validated the values of csf-key mentioned in the configuration of DocumentService call.
When we disable the policy attached to the reference, it gives 401- Authorization error and it fails
[2016-04-21T02:37:17.316-07:00] [soa_server1] [ERROR] [] [oracle.integration.platform.blocks.soap] [tid: orabpel.invoke.pool-4.thread-4] [userId: <anonymous>] [ecid: fe4f6d542a73d759:224403c:154381e41c9:-8000-0000000000000cab,1:17052] [APP: soa-infra] [composite_name: senaUpdateDocument] [component_name: senaUpdateDocument] [component_instance_id: 2480007] Unable to dispatch request to http://bali.sdsu.edu:16000/imaging/ws/DocumentService due to exception[[
oracle.fabric.common.FabricInvocationException: Unable to access the following endpoint(s): http://bali.sdsu.edu:16000/imaging/ws/DocumentService
at oracle.integration.platform.blocks.soap.AbstractWebServiceBindingComponent.dispatchRequest(AbstractWebServiceBindingComponent.java:592)
……..
Caused by: javax.xml.ws.WebServiceException: oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid: WSM-06102 The same code is working in DEV and PROD. We validated the values of csf-key mentioned in the configuration of DocumentService call.
When we disable the policy attached to the reference, it gives 401- Authorization error and it fails
Also after checking the soa_server logs we are
getting below errros:
1. [soa_server1]
[ERROR] [] [oracle.integration.platform.blocks.soap] [tid:
orabpel.invoke.pool-4.thread-11] [userId: <anonymous>] [ecid:
fe4f6d542a73d759:3f106577:154375b998d:-8000-0000000000003d60,1:29090] [APP:
soa-infra] [composite_name: senaUpdateDocument] [component_name:
senaUpdateDocument] [component_instance_id: 2470018] Unable to dispatch request
to http:// /imaging/ws/DocumentService due to exception[[
javax.xml.ws.WebServiceException: oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid: WSM-06102 PolicyReference The policy reference URI "oracle/wss_username_token_client_policy" is not valid.
:25)
Caused by: oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid: WSM-06102 PolicyReference The policy reference URI "oracle/wss_username_token_client_policy" is not valid.
at (AbstractWebServiceBindingComponent.java:564)
at at
javax.xml.ws.WebServiceException: oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid: WSM-06102 PolicyReference The policy reference URI "oracle/wss_username_token_client_policy" is not valid.
:25)
Caused by: oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid: WSM-06102 PolicyReference The policy reference URI "oracle/wss_username_token_client_policy" is not valid.
at (AbstractWebServiceBindingComponent.java:564)
at at
Problem
related to this issue:
1.
"PolicySet Invalid: WSM-06102 PolicyReference The policy
reference URI "oracle/no_authentication_client_policy" is not
valid."
2. ORABPEL-05002
Errors occurring in log files
3. Unable
to invoke document service.
4. BPM
workspace issue
5. Unable
to start WebLogic Admin server
6. Some
BPEL got faulted.
7. Fabric
exception
Troubleshooting
and solution issue:
We have multiple root
cause for this issue.
1. While
upgradation some Jar files are missing.
2. Change
of WebLogic server password.
3. Unable
to get basic. Credentials
4. Missing
of Oracle System User in weblogic
5. Invalid
WSM policy
6. SOA-infra
application and WSM policy application is in warning state.
7.
WSM-06157: The
repository database is not configured correctly or not running.
8.
WSM-06160: The
policy manager application has not been deployed or is not running.
9.
WSM-06161: The
policy manager application has not been deployed.
10.
WSM-06162:
The policy manager application is not running or is not configured correctly.11. WSM-06159:
Cannot connect to the policy manager due to credential issue.
12. The Policy Manager is targeted to
an SSL server.
13. The credential required to access
the Policy Manager is invalid or is not authorized.
14. The repository may not be
configured correctly
15. Seems like some
corruption at WLS level with respect to oracle.wsm.seedpolicies libraries.
16. The error
occurs on other managed servers as well.
17. Errors also may occur
when un-targeting and re-targeting the oracle.wsm.seedpolicies libraries
to managed servers.
Solution
to Error WSM-06102
PolicyReference" while invoking Imaging document service in Imaging
We have multiple solutions available for this issue.
1.
upgradeWSMPolicyRepository(); using WLST command
2.
redeploy WSM Policy Manager on WebLogic Server.
3. With
SSL need to check keystore with valid jks
4. Need
to start all target servers.
Once we perform all the solution
that available on oracle support but still we are facing this issue we need to
do following solution. In our case we have upgraded our Imaging environment
from version 11.1.1.6.0 to version 11.1.1.9.0 so due to this our application
WSM-pm and its related jar are corrupted or somehow they are not upgraded
during environment upgradation. So we need to redeploy wsm-pm application
through WebLogic server as well as make sure that deployment order must be 5
not 100 or 300 in WLS. Basically during server start-up we need WSM-pm
application with deployment order 5 while starting Admin and managed server.
Solution:
In
order to resolve this issue we need to redeploy WSM-PM application along with wsm-seed-policies
jar under deployment of Weblogic server with order 5.
Please find details steps below:
1. Login to WLS
console, Deployments.
2. Stop WSM-PM application and
un-deploy it from WLS Console.
3. Un-deploy
oracle.wsm.seedpolicies library.
4. Deploy oracle.wsm.seedpolicies
located in
MIDDLEWARE_HOME/oracle_common/modules/oracle.wsm.policies_11.1.1/wsm-seed-policies.jar
a. Ensure to deploy as a LIBRARY
b. Target to: All Servers
5. Deploy wsm-pm application
located in MIDDLEWARE_HOME/oracle_common/modules/oracle.wsm.pm_11.1.1/wsm-pm.ear.
NOTE: When manually deploying wsm-pm.ear, it will end up having
deployment order "100". A deployment order of "5" is
required so it is available early during server startup for anything that needs
it.
a. Ensure to deploy as application.
b. Target to the Webcenter Managed
servers -ALL
c.
Admin Console, Deployments, Navigate to wsm-pm.
In "Settings for wsm-pm"
page, on the Overview tab,
"Deployment Order" should be 5.
6. Edit
DOMAIN_HOME/config/fmwconfig/jps-config.xml
and ensure it look like:
<jpsConfig
xmlns="http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" schema-major-version="11"
schema-minor-version="1"
xsi:schemaLocation="http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd
jps-config-11_1.xsd">
8. Re-start the Admin Servers and Managed Servers.
Reference:
support.oracle.com
 |
No comments:
Post a Comment