No Rows Yet Message Displays

22-20 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter connectweblogic,weblogic, soa host : soa administration port revokeAppRoleappStripe=soa-infra, appRoleName=BPMWorkflowAdmin, principalClass=oracle.security.jps.service.policystore.ApplicationRole, principalName=SOAAdmin grantAppRoleappStripe=soa-infra, appRoleName=BPMWorkflowAdmin, principalClass=weblogic.security.principal.WLSUserImpl, principalName=user In this example, the LDAP identity store has a user named user. If the user to which you want to grant the BPMWorkflowAdmin role does not exist in the LDAP identity store, then you must restart the Oracle SOA Suites managed server to make this change effective.

22.5.2.3 Issues with the wsm-pm Application

Problem Issue with the wsm-pm application on either the Worklist services managed server, or the Oracle SOA Suites managed server, or on both. Solution The wsm-pm application manages the Web service security policies that control the SAML authentication in the Worklist service. To validate the wsm-pm application, log in to the wsm-pm applications validation page as a user with administrative rights. Use this format for validation: http:host:portwsm-pmvalidator. If there are no issues with this application, then accessible policies must display. If policies do not display, then investigate the related logged information on the server whose wsm-pm application is failing.

22.5.2.4 Clocks are Out of Sync for More Than Five Minutes

Due to security reasons, the Web service security interaction between the Worklist services managed server and that of the Oracle SOA Suite BPEL must take place with a time difference of less than five minutes. That is, the clocks on both host machines must have a time difference of less than five minutes, otherwise authentication fails. The SAML assertion uses the NotBefore condition to verify this. Problem Clocks of the Worklist services managed server and the Oracle SOA Suite BPELs managed server are out of sync for more than five minutes. Solution Ensure that the current time is not set to earlier than the SAML assertions clockskew, which is 300 seconds by default. Either match the time on the client and service machines, or configure the agent.clock.skew property in seconds in the policy-accessor-config.xml file. This file is located in the DOMAIN_HOMEconfigfmwconfig directory.

22.5.2.5 Worklist Service Timed Out or is Disabled

Problem The Worklist service cannot obtain a query result from the Oracle SOA Suite BPEL server within a defined period. Managing the Worklist Service 22-21 The Worklist service issues queries to the Oracle SOA Suite BPEL server using concurrent threads. These threads are allotted a certain amount of time in which to respond. If these threads do not respond in the allotted time, for example 15 seconds, then the Worklist service times out the call, and it allows the task flow to display the unavailability message. In such a case, log files include related exceptions such as the following: [2009-03-03T12:09:34.769-08:00] [WLS_Spaces] [ERROR] [WCS-32103] [oracle.webcenter.worklist.model] [tid: [ACTIVE].ExecuteThread: 3 for queue: weblogic.kernel.Default self-tuning] [userId: user] [ecid: 0000HzDx68KC0zT6uBbAEH19fOWs00002q,0] [APP: webcenter] Unable to query BPEL repository.[[ oracle.webcenter.concurrent.TimeoutException: Execution timedout queued : 1 ms suspended : 0 ms running : 15389 ms timeout : 15000 ms service : Worklist resource : ir source : oracle.webcenter.concurrent.CallableTaskbf3952 oracle.webcenter.concurrent.CallableTask submission : 150 at oracle.webcenter.concurrent.Submission.transitionToSubmission.java:595 at oracle.webcenter.concurrent.Submission.timeoutSubmission.java:634 at oracle.webcenter.concurrent.InternalExecutorService.checkForTimeoutsInternalExecu torService.java:566 at oracle.webcenter.concurrent.InternalExecutorService.access300InternalExecutorSer vice.java:18 at oracle.webcenter.concurrent.InternalExecutorService1.runInternalExecutorService. java:352 at java.util.TimerThread.mainLoopTimer.java:512 at java.util.TimerThread.runTimer.java:462]] Solution If errors such as this occur consistently, then there may be fundamental issues with the resources available to the managed servers running the Worklist service and the Oracle SOA Suite BPEL server. Validate that the volume of users and resources provided is adequate to run these servers in the infrastructure provided. Note: Continuous occurrence of TimeoutExceptions can also disable the Worklist service. Due to which this service cannot connect to the BPEL instance that is failing to respond quickly. In such a case, the logs contain oracle.webcenter.concurrent.DisabledException exceptions. These exceptions are related to the Worklist service failure.