Pages

Thursday, September 29, 2016

Is there a Essbase Web services - Part 4

After the Part1, Part2 & Part3 let me cover the DatasourceService & QueryService in this post.

Accessing the Datasource Service


As stated earlier the Datasource Servcie is invoked via the url 

Note:Since i have added the web-service to the ohs, i can access the using the default webserver port (this is covered already in the earlier post)
  
Following are the various operations available for the Datasource Service 





Create:


Create()

Input: BaseObject
Output: BaseObject

Creating the application BlgPost with the properties 

                <storageType>MULTIDIMENSIONAL</storageType>
                <loadable>true</loadable>
                <autoLoad>false</autoLoad>
                <access>NONE</access>
                <connectable>true</connectable>
                <acceptCommands>true</acceptCommands>
                <acceptUpdates>true</acceptUpdates>
                <securtiyEnabled>true</securtiyEnabled>
                <lockTimeOut>60</lockTimeOut>
       
        <lroSizeLimit>0</lroSizeLimit>


Response:



The "BlgPost" application is visible in EAS console




Delete:


Delete()

Input: URI
Output: None

Deleting the application BlgPost 


Response:

Notice there is no output

Get:



Get()

Input: URI
Output: BaseObject

Get details about cube for the vision.Plan1

Response:

Retrieves Cube type,number of dimensions,cube calc info,cache buffer info & runtime info etc..

List:


List()

Input: UriType, URI
Output: BaseObject[]

Listing all the database part of a application "Vision"

 
 Response:

Plan1, Plan2 & Plan3 part of the Vision application is listed

Accessing the QueryService - Data Queries


Services offered by the Query Service is listed below,

Since most of the services are similar to the options we get from Smart view i am picking couple of them.

Execute:

execute()

Input:
Cube: URI (Essbase cube)
Text: MDX query statement
Options: MDX query options
Output: Either an MDX MDData result set or a grid based on result Format specified as 
part of input Options

Executing the MDX SELECT
 Extract(
         {
           ([Year].[Qtr1], [Market].[California]), 
           ([Year].[Qtr1], [Market].[Oregon]), 
           ([Year].[Qtr2], [Market].[Oregon])
         }, Year
 )
ON COLUMNS
FROM Sample.basic 

Have collapsed the Options part, but have left all the values as default

Responce:

Same MDX ran from EAS console



Accessing the QueryService -Metadata Queries


Querying a Member:

queryMember

In: URI (Essbase cube), QueryMemberOptions
Out: Essbase member array

QueryOption fields in QueryMemberOptions

QUERY_OPTION_MEMBERSONLY
QUERY_OPTION_ALIASESONLY
QUERY_OPTION_MEMBERSANDALIASES
QUERY_OPTION_COUNTONLY
QUERY_OPTION_NOTOTALCOUNTS
QUERY_OPTION_INCLUDEHYBRIDANALYSIS
QUERY_OPTION_EXCLUDEHYBRIDANALYSIS
QUERY_OPTION_FORCECASESENSITIVE
QUERY_OPTION_FORCEIGNORECASE
QUERY_OPTION_UNIQUENAME
QUERY_OPTION_USESUBSTITUTIONVAR

QueryType fields in QueryMemberOptions

QUERY_TYPE_CHILDREN
QUERY_TYPE_DESCENDANTS
QUERY_TYPE_BOTTOMLEVEL
QUERY_TYPE_SIBLINGS
QUERY_TYPE_SAMELEVEL
QUERY_TYPE_SAMEGENERATION
QUERY_TYPE_PARENT
QUERY_TYPE_DIMENSION
QUERY_TYPE_NAMEDGENERATION
QUERY_TYPE_NAMEDLEVEL
QUERY_TYPE_SEARCH
QUERY_TYPE_WILDSEARCH
QUERY_TYPE_USERATTRIBUTE
QUERY_TYPE_ANCESTORS
QUERY_TYPE_DTSMEMBERS
QUERY_TYPE_DIMUSERATTRIBUTES
QUERY_TYPE_INDEPDIMS
QUERY_TYPE_INDEPDIMS_DISCRETE
QUERY_TYPE_INDEPDIMS_CONTINUOUS

Query for returning all the bottom level members for YearTotal

Responce: 



since the Output was for all 12 periods i am showing for only Jan and its repeated for the rest of the 11 periods.


I am ending the series here, it was pretty awesome to learn about this Essbase web services. As Oracle strategy is towards cloud and more cloud, i believe this will be quite handy but have to wait and watch how this knowledge can be utilized for the Essbase cloud service.

Happy days ahead with cloud!!!



1 comment: