Business Intelligence – Oracle

Archive for August, 2008

Oracle BI EE 10.1.3.4 – Calling BI EE WSDL from BI Publisher

Posted by Venkatakrishnan J on August 12, 2008

Another very important and very good feature of BI Publisher 10.1.3.4 is the support for Complex Web Services. Support for Web Services in BI Publisher,i believe, was introduced in 10.1.3.2. But the major problem with that was the support was limited to very simple web services like Yahoo Stock quotes etc. But now with the support for complex web services, one can achieve more complex integration with BI EE as well as other reporting toolsets. One direct correlation of this support is the ability of BI Publisher now to have BI EE WSDL as a data source. Yes, BI Publisher now can call BI EE WSDL’s directly. Till the previous release, the only way to achieve this was by converting the complex WSDL to a simple one through servlets. Lets try this new feature out today by means of a simple report. We shall start with a new report with Web Service as the data source.

    

When we choose Web Service as our data source, we can now see there are 2 types of Web Services. Simple or Complex.

    

Lets choose complex. And in the WSDL URL lets enter the BI EE WSDL.

http://localhost:9704/analytics/saw.dll?WSDL

As soon as we enter the above WSDL, we should now be able to choose any one of the web services. Remember BI EE WSDL is a multi binding web service. That is, a single WSDL can provide a combination of multiple web services. For now lets choose SAWSession Service.

    

Lets choose the Logon method and enter the username and password parameters.

    

Now, lets see what happens when we look at the report output.

    

Strange. I was expecting the Web Service to return back the SessionID. But unfortunately it does not look to be straightforward. So far, i have not been able to get this to work (even when i try to pass the parameters from BIP parameters using ${Parameter_name}). Now, if you see the OC4J command window, you would see the actual SOAP envelope that has been fired by BI Publisher.

    

Now, lets copy the above SOAP envelope and fire it from SOAP UI to test whether this envelope actually works.

    

Well, it does work. So, I am not sure what else is required to get the login method to work from within BI Publisher. I believe the above behavior is probably due to the fact that BI Publisher actually tried to fire the SOAP envelope using a dummy parameter first and then with the actual parameters i,e your OC4J would actually show you the 2 SOAP envelopes being fired from BI Publisher

08/08/12 20:04:45 WebServiceCall::callComplexClient SOAP Message = <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body xmlns:ns1="com.siebel.analytics.web/soap/v5">
            <ns1:logon>
                  <ns1:name>%LABEL_1%</ns1:name>
                  <ns1:password>%LABEL_2%</ns1:password>
        </ns1:logon>
    </soap:Body>
</soap:Envelope>
08/08/12 20:04:45 After WSS soapMessage = <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body xmlns:ns1="com.siebel.analytics.web/soap/v5">
            <ns1:logon>
                  <ns1:name>Administrator</ns1:name>
                  <ns1:password>Administrator</ns1:password>
        </ns1:logon>
    </soap:Body>

The authentication failed message that we obtained is probably due to the first envelope. Not sure what more is required to get this to work. A very interesting feature but something i have not been able to test successfully so far(atleast with BI EE alone).

Posted in All Posts, Bi Publisher, OBI EE Plus | 3 Comments »

BI EE 10.1.3.4 – BI Publisher and MDX – Essbase Connectivity

Posted by Venkatakrishnan J on August 7, 2008

One of the new features of the BI EE 10.1.3.4 release is the new connectivity to Essbase from BI Publisher. Lets see how this works today. As a first step, lets set up the OLAP Connection to Essbase from within BI Publisher.

The connection is pretty straight forward. All one would have to do is to enter the Essbase server name. Now lets, go into BI Publisher and create a simple report.

    

As you see, there is no level or generation selection that is possible in a wizard interface. One would have to manually enter the MDX Query. This is a bit of a downer since i was atleast expecting a wizard interface to choose the levels (if not members). But anyway lets try entering a simple MDX query as shown below

SELECT
{[100-10], [100-20]}
ON COLUMNS,
{[Qtr1], [Qtr2], [Qtr3], [Qtr4]}
ON ROWS
FROM Sample.Basic

Lets save the above report. Now, lets click on data and see what happens. As you see below, the data is properly retrieved which is very good.

    

Now, lets try a complex MDX query as shown below

SELECT
Union(CrossJoin({[Sales], [Profit]}, {[Actual], [Budget]}),
Union(CrossJoin([Total Expenses].Children, {[Actual]}),{([Opening Inventory], [Variance]), ([Additions], [Variance %])}))
ON COLUMNS,
CrossJoin([200].Children, {[East], [West]} )
DIMENSION PROPERTIES [Product].Ounces
ON ROWS
FROM Sample.BasicWHERE {[Jan]}

    

    

This is something that BI Server lacks currently as one cannot enter MDX queries directly in the “Direct Database Requests”. If you are not sure what i mean, lets enter the same query above in the direct database requests page in BI Answers.

    

As you see, the above errors out as BI Server expects only columnar data through the MDX. The support for MDX is very limited from a BI EE standpoint. Now with the support of BI Publisher, the MDX support is more enhanced. But the drawback still is the lack of a wizard driven interface and also lack of true multi dimensional aware reporting.

Posted in All Posts, Bi Publisher, Hyperion Essbase, OBI EE Plus | 4 Comments »

BI EE 10.1.3.4 – Available for Download

Posted by Venkatakrishnan J on August 7, 2008

While i was away on a blogging slumber due to quite a few assignments off late, looks like 10.1.3.4 release of BI EE has finally made its way out. Quite a lot of features have been bundled into this release. The list below shows some of them which i thought are worth highlighting

1. Integration of BI EE into EPM. One can now view BI EE Answers, Dashboards, Delivers and BI Publisher from within the Workspace. I believe one would need 10.1.3.4 of BI EE and 11.1 of EPM to get this to work.
2. Migration of Discoverer EUL into BI EE Repository
3. Time Series based charting
4. Integration of BI EE and BI Publisher from within Weblogic

The other important addition in this release is the addition of multi dimensional data sources support in BI Publisher. One can download the software here. I am hoping to cover all these new features in the coming week. Lets see how the integration between EPM and BI EE works first in the next blog entry.

Posted in All Posts, OBI EE Plus | 2 Comments »