Saturday, June 1, 2013

Unable to Login BPM Workspace/Composer

Last week I installed BPM PS6 on one of my local servers. Since it was intended to be a development environment, I configured my WebLogic domain to have a single server which would double up as my SOA/BPM server in additions to its Admin server capabilities.

After a clean install, while trying to login as weblogic [the administrator user] in to the BPM workspace or BPM composer, these applications wouldn't allow access throwing "Login Error" & "Authentication Error" respectively. However, I was successfully able to login to the WebLogic console & EM with same credentials.

On investigating the server logs, the following errors were reported by the managed server;

[APP: BPMComposer] BPM-80102: Error while creating the security service.  Cause: Identity Service Configuration error.[[ Identity Service Configuration has error.
Please refer to the identity service configuration guidelines and correct the Identity Service configurations. Contact Oracle Support Services if error is not fixable.
javax.security.auth.login.LoginException: BPM-80102: Error while creating the security service.  Cause: Identity Service Configuration error.
........
........
........
Caused by: ORABPEL-10555
Identity Service Configuration error.
Identity Service Configuration has error.
........
........
Caused by: oracle.bpel.services.workflow.client.WorkflowServiceClientException: javax.xml.ws.WebServiceException: oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid: WSM-02557 oracle.wsm.policymanager.accessor.BeanAccessor The documents required to configure the Oracle Web Services Manager runtime have not been retrieved from the Policy Manager application (wsm-pm), possibly because the application is not running or has not been deployed in the environment. The query "&(policysets:global/%)(@appliesTo~="WS-Client()")" is queued for later retrieval. WSM-02557 oracle.wsm.policymanager.accessor.BeanAccessor The documents required to configure the Oracle Web Services Manager runtime have not been retrieved from the Policy Manager application (wsm-pm), possibly because the application is not running or has not been deployed in the environment. The query "/policies/oracle/no_authentication_client_policy" is queued for later retrieval.

Clearly the error states an issue with the policy manager under OWSM (Oracle WebServices Manager).

If this is not the error message in your logs, you may review the blog post here to see if that helps.

Solution:

Step 1:

1. Login to WLS console (http://hostname:port/console) as weblogic [Admin user]
2. Under the Data Sources, ensure that the mds-owsm jdbc data source is targeted at the SOA managed server [If you have a single server install verify that it is targeted at AdminServer]. If not, edit the data source & update targets

Step 2:

1. Under the "Deployments" section of WLS console, make sure that the wsm-pm enterprise application is running. If the deployment state is other than "Active", there is a good posibility that this application is not targeted on the SOA managed server.
2. Solution here is to target this application manually on the SOA server. To do this, click on the wsm-pm application -> Go to Targets tab -> choose the wsm-pm root component -> Click on "Change Targets" -> Check the SOA managed server (or AdminServer in case of single server install) and choose "Yes".

Now, you should be able to successfully login to the BPM workspace & BPM composer applications.

5 comments:

  1. i faced the similar Error while creating in the BPM MSD and i solved the issue if any have the similar issue

    refer it

    http://ramkumarkannansoa.blogspot.com/2013/06/bpm-mds-connection-error-test-failed.html

    ReplyDelete
  2. Thanks Sathyam. This recurred on 12c and worked with your approach.

    ReplyDelete
  3. I Sathyam,
    I am also facing the same issue. I tried with all the settings changes as you suggested but I am still able to login to BPM workspace.

    ReplyDelete
    Replies
    1. I am aware that this was a workaround quick fix for the problem for PS6. I know this problem no longer exists in 11.1.1.9 & 12c releases. Can you upgrade your environment to 11.1.1.9?

      Delete