Remote Portlet Communication Error When Accessing a Task in Functional Setup Manager.

(Doc ID 1363634.1)

Last updated on JUNE 09, 2016

Applies to:

Oracle Fusion Application Toolkit - Version 11.1.1.5.1 and later
Information in this document applies to any platform.
** 12/15/2014 reviewed for currency ***

Symptoms

Users  attempt to access the Enterprise Scheduling Services (ESS) Definitions screen in Functional Setup Manager (FSM) ---> Setup and Maintenance page  by searching for Manage Custom Enterprise Scheduler Jobs for either Financial or Supply Chain.  The search fails with  the error  "Remote Portlet Communication Error" as shown below.


Consumer Client Log - FunctionalSetupServer_1.out_923

<Sep 23, 2011 2:23:21 PM CDT> <Error> <oracle.portlet.client.connection.wsrp.HTTPClientTransport> <WCS-40151> <A request to the producer URL "http://<host>:<port>/financialCommon/portlets/WSRP_v2_Markup_Service" resulted in a status 500 response with fault string "InvalidSecurity : error in processing the WS-Security security header". The fault code given was "{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}InvalidSecurity".>
<Sep 23, 2011 2:23:21 PM CDT> <Error> <oracle.portlet.binding> <BEA-000000> <An error has occured for Portlet Binding portlet1.
oracle.portlet.client.container.PortletHttpException: HTTP <unknown method> request to URL http://<host><domain>:<port>/financialCommon/portlets/wsrp2?WSDL failed with status code 500 reason <unknown reason>. Check that the producer URL has been correctly specified, that the producer server machine and producer container are running, that the producer application is deployed correctly, and that the client can reach the server if behind a firewall.

....
....
Caused By: oracle.portlet.client.container.PortletHttpRuntimeException: HTTP <unknown method> request to URL http://<host><domain>:<port>/financialCommon/portlets/wsrp2?WSDL failed with status code 500 reason <unknown reason>. Check that the producer URL has been correctly specified, that the producer server machine and producer container are running, that the producer application is deployed correctly, and that the client can reach the server if behind a firewall.
at oracle.portlet.client.connection.wsrp.ActivityServerWrapper.checkAndReturnHttpException(ActivityServerWrapper.java:57)

 

Producer Server Log - FinancialCommonServer_1.out_923

<Sep 23, 2011 2:23:21 PM CDT> <Error> <oracle.webservices.service> <OWS-04115> <An error occurred for port: {urn:oasis:names:tc:wsrp:v2:wsdl}WSRP_v2_Markup_Service: oracle.fabric.common.PolicyEnforcementException: InvalidSecurity : error in processing the WS-Security security header.>
oracle.fabric.common.PolicyEnforcementException: InvalidSecurity : error in processing the WS-Security security header

at oracle.fabric.common.AbstractSecurityInterceptor.processResult(AbstractSecurityInterceptor.java:235)
at oracle.fabric.common.BindingSecurityInterceptor.processRequest(BindingSecurityInterceptor.java:95)
at oracle.integration.platform.common.InterceptorChainImpl.processRequest(InterceptorChainImpl.java:127)
at oracle.integration.platform.common.mgmt.InterceptorChainManager.processRequest(InterceptorChainManager.java:279)
at oracle.j2ee.ws.server.mgmt.runtime.SuperServerInterceptorPipeline.handleRequest(SuperServerInterceptorPipeline.java:155)
.....
....
Caused by: oracle.wsm.common.sdk.WSMException: InvalidSecurity : error in processing the WS-Security security header
at oracle.wsm.security.policy.scenario.executor.WssUsernameTokenScenarioExecutor.receiveRequest(WssUsernameTokenScenarioExecutor.java:194)
at oracle.wsm.security.policy.scenario.executor.SecurityScenarioExecutor.execute(SecurityScenarioExecutor.java:596)
at oracle.wsm.policyengine.impl.runtime.AssertionExecutor.execute(AssertionExecutor.java:41)

 

Troubleshooting Steps:

1) Connect to the consumer FSM/Common domain using WLST and execute the
command listPolicySets().  Notice the the Common Domain does not have any
GPA set.





2) Connect to the producer Financial common domain and execute the same
  command listPolicySets().



3) Confirm if the policies are present on both the producer and consumer.
    a. Log into Functional Setup Manager (FSM).
    b. Go to the Review Topology link.
    c. Go to the Diagnostic tests tab
    d. Click on Go to Task Configuration
    e. Search for the tasks.
    f. Click on the Run button for Validate Consumer Oracle Web Services Management  
       Policy Manager and Validate Provider Oracle Web Services Management Policy
       Manager. Users will be asked for WLS user/pwd.  The result will list all the policies
       present in the repository.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms