Pages

Friday, September 16, 2016

Is there a Essbase Web services - Part 2

In the previous post Is there a Essbase Web services -Part 1, I did talk about invoking the Essbase Web services & during the task I did encountered issues and would like to post the solution along with the issues I have encountered.

Issue on a distributed instance:

Once the WSDL is enabled to true in the http:WeblogicAdminServer:7001/em and disabling the OWSM authentication by adding the flag “essbase.webservices.disable.owsm=true”

To the file essbsae.properties









I was getting this error message, while invoking the web services





 In the Admin Server logs, I could find these error





















 2016-09-15T06:38:13.148-04:00] [AdminServer] [ERROR] [] [oracle.webservices.jaxws] [tid: [ACTIVE].ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 53358c088264267c:-4550a3cd:156d7ba2f8b:-8000-000000000000070e,0] [APP: em] [DSID: 0000LShKoTm9PdWjLxNM8A1Nl8b6000009] Error while invoking endpoint "http://essbaseserver.corp.verticaledgecg.com:13080/essbase-webservices/DatasourceService" from client; Security Subject: epm_admin

In the AnalyticProviderServices logs, I could find these error

















An error occurred for port: {http://essbase.webservices.oracle}DatasourceServicePortType: 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 "&(@appliesTo~="WS-Service()")(policysets:global/%)" is queued for later retrieval. .

Solution:

Login to Weblogic Admin Console (http://weblogicAdminServer:7001/console)

Go to Services ->Data Sources -> mds-owsm


On the Targets tab -> Click Lock & Edit at Change Center
Select AnalyticProviderServices  and then click Save

























Select Deployment->wsm-pm















Go to Targets tab & select the Component checkbox to select all components.
Click Change Targets & select AnalyticProviderServices  , and then click Yes.
Click Activate Changes from Change Center.

Make sure it looks like the following image,
















Restart the AnalyticProviderServices & I was able to access the web services.






















Issue on a single Instance:
Similarly, this issue was encountered in a different instance where the error look alike but when I drill further the errors are quite different.

After enabling the web services, it did throw the same error message while invoking the web services,

An error occurred for port: {http://essbase.webservices.oracle}DatasourceServicePortType: 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 "&(@appliesTo~="WS-Service()")(policysets:global/%)" is queued for later retrieval. .


In the Admin Server, I could see this error message - "Unable to get the Action Executor"


Solution:


 Using the WLS console make sure that the "OracleSystemUser" user exist, as a member of "OracleSystemGroup". "OracleSystemGroup", in turn, should have the WebLogic Server global role, OracleSystemRole, assigned to it.


Once i have the needed user and groups in palace with the proper access as shown below, i was able to access the web services.


























More to come on this, stay tuned :-)


No comments:

Post a Comment