Business Intelligence – Oracle

Archive for the ‘Hyperion Web Analysis’ Category

Oracle BI EE and Hyperion Web Analysis – Drill from BI EE to Web Analysis – Part 1

Posted by Venkatakrishnan J on February 10, 2009

If you had looked at my blog entry here, i would have shown how to go about drilling from BI EE to HFR. Along the same lines, lets look at another common requirement which is to drill from BI EE to Web Analysis. Again as i have said here before, the fundamental idea is to get the URL parameters for Web Analysis and understand how Web Analysis accepts its parameters. In order to understand this, lets create a simple report using Web Analysis studio as shown below.


Our aim is to determine the URL parameters for Web Analysis. So, for one of the measure values add Related Content and just include the same report as shown below



Now, if you see there are 3 types of links offered by Web Analysis

1. Embedded Link
2. Java Link (The Web Analysis Studio Link)
3. HTML Link

Lets analyze all the 3 links one by one. The first one is the Embedded link.


As you see this has the following parameters

1. module – This is a workspace specific parameter which specifies that the report comes as a related content.
2. repository_uuid – This a constant id for the webanalysis report
3. repository_format_id – Since workspace can embed multiple objects of different mime types, this specifies the output type of the report.
4. repository_name – name of the WebAnalysis report
5. repository_path – path to the actual Web Analysis report
6. SSO_TOKEN – This token is useful for all SSO enabled workspace contents. If this is passed in the URL, the target application is opened automatically without signing in. (If SSO is not enabled then SSO_USERNAME and SSO_PASSWORD can be passed in the URL)
7. CONTEXT – This passes the actual POV of the cell that we have clicked. This is the most important parameter as this would let us know how the parameters are passed to web analysis.
8. mime_type – This determines the application type.

Typically it is recommended to use the Embedded link as the output type is generally driven by the URL parameter itself. The second link is the Java Link. This helps in drilling within the studio itself. This is not generally used a lot unless a person requires the drill to happen within the studio itself.


The parameters are exactly the same as the one in embedded link. But not every parameter in the Embedded link is supported in the Java Link.

The third type of link is the HTML link. This is used for generic content viewing in HTML. Its URL is shown below


In all the 3 links above, the most important of all is the $CONTEXT$ parameter. This is what passes down the individual Point of View (POV) values to the target. But to pass this from BI EE, we need to know how this $CONTEXT$ parameter is structured. So, instead of using a report as a related content, lets include a custom link as shown below.


Now, launch this URL from within Web Analysis Studio. You would see a new IE window with the actual CONTEXT parameter as shown below



In HFR, the $CONTEXT$ that we saw earlier had a specific format. If you look closely, Web Analysis too follows a similar pattern. To pass down individual member values to the report just use

attribute=<Dimension Name>.id.<Dimension Value>

For example,

There are also other parameters in the URL which are specific to Web Analysis. Now, that we have seen how the URL parameters for web analysis is structured, the integration from BI EE remains the same. The idea is to generate the above URL dynamically (which i have shown in the HFR blog entry). An example is given below


Posted in All Posts, EPM, Hyperion Essbase, Hyperion Web Analysis, OBI EE Plus | 2 Comments »