Variables in OBIEE 11g

 Variables is main part in obiee development In obiee having 4 types of variables is there. We will Disuses the types and syntax and what is use.. 

There are basically 4 different types of variables in OBIEE 11g. 

1. Session Variables
2. Repository Variables
3. Presentation Variables
4. Request Variables.

1.Session Variables:

As the name suggests, session variables are created during the creation of session i.e., as soon as a user logs into the BI server. So, Every login has its own session variable.

There are two types of session variables

System (which are defined by OBIEE and are reserved)

Non-System which are defined by developers.

Session Variables can be created only through Oracle BI Administration Tool.

Referencing session variable:

For displaying session variables, we should use @{biServer.variables'NQ_SESSION.VariableName']} .

For using session variables in expression, we should use VALUEOF(NQ_SESSION.“VariableName”).

Repository Variables:

A repository variable is a variable that has a single value at any point in time.

There are two types of repository variables

Static (which changes only if admin or developer changes it value)

Dynamic ( value is refreshed using a query)

*Repository variables can be created only through Oracle BI Administration Tool. 

Referencing repository variable:

For displaying repository variables, we should use @{biServer.variables.VariableName} or @{biServer.variables['VariableName']}.

For using repository variables in expression, we should use VALUEOF(“VariableName”) for static variable and for dynamic variable VALUEOF(“Dynamic Initialization Block Name”.“VariableName”).

Presentation Variable:

A presentation variable is a variable which can be created as a part of creation of dashboard prompts. Dashboard prompts must be either Column Prompt or Variable Prompt.

The value of presentation variable is set by the prompt for which it is created (upon user selection).

Referencing presentation variable:

For displaying presentation variables, we should use either

@{variables.VariableName}[Format]{DefaultValue} or Format and DefaultValue are optional

Format is useful to format the data for e.g., for Date, format can be MM/DD/YYYY.

 Note: Default Value is not formatted. @{scope.variables['VariableName']}.

Scope should be used if you create variables with same name.

Scope can be analyses, dashboard etc.

Order of precedence is analyses, dashboard pages, dashboards.

For using presentation variables in expression, we should use @{“VariableName”}{DefaultValue}. Default value is optional.

Request Variable:

Request Variable is used to overwrite the value of session variable and it happens only during request initiation to the database from column prompt.

Can be created only during the creation of column prompt.

Referencing request variable: Same as presentation variable.

  

        

Master Detail Event in OBIEE 11G

Master-detail linking of views allows us to establish a relationship between two or more views such that one view, called the master view, will drive data changes in the other (connected) views, called detail views. For e.g., let’s assume that we have two views, one a table that shows dollars by region, the other a graph that shows dollars by brand with region on a section slider. Using the master detail linkage, we could connect the two in such a manner that on clicking a particular region, the region in the section slider of the graph as well as the data in the graph will change.

Let’s understand how to set this up. Let’s create a sample new analysis. I am using the SampleApp that is delivered with OBIEE 11g. I created a report with the following sample fields:

Let’s designate the T05 Per Name Year as the column that will be the master driving our detail views. Click properties for T05 Per Name Year. On the interaction tab, set the value Primary Interaction to ‘Send Master-Detail Events’. We would also need to specify a channel for the detail views to be listening. In this example, we’ll use 1. Multiple channels allows for creating multiple listener events in the dashboard/report.

We’ll create an analysis that includes a vertical bar chart and a pivot table. We create a graph and move the T05 Per Name Year to the sections and display as a slider:

Open the graph properties and edit to ‘Listen to Master-Detail Events’. The specified channel name “must” match the name given in the column properties earlier.

NOTE : In the detail view we need to include that column which is to be passed from master to detail as a prompt.
For example: Assume you are clicking on the “Site Desc” column from the master view and want the detail view to change according to the site clicked upon. In this case you should make the “Site Desc” column in the detail view as a prompt.

 

How to Connect DAC server To Informatica repository

DAC uses the Informatica pmrep and pmcmd command line programs to Communicate with Informatica Power Center in the following ways:

DAC Server uses:
a)Pmrep to communicate with Power Center Repository Services.

b)Pmcmd to communicate with Power Center Integration Services to run the Informatica workflows.

DAC Client uses:
a)Pmrep to synchronize tasks with Informatica workflows and to keep the DAC task source and target table’s information up to date.

Differnce Between Ragged and Skip level Hierarchy in OBIEE11g

 Ragged  Hierarchy:

         A hierarchy in which all the lowest-level members do not have the same depth.
 For example: a Time hierarchy might have data for the current month at the day level, the previous month's data at the month level, and the previous 5 years' data at the quarter level. This type of hierarchy is also known as an unbalanced hierarchy.

Skip-level  Hierarchy:

A hierarchy in which certain members do not have values for certain higher levels.
For example: in the United States, the city of Washington in the District of Columbia does not belong to a state. The expectation is that users can still navigate from the country level (United States) to Washington and below without the need for a state.

Object Level Security In OBIEE11g

we can restrict access for dashboard,pages,sections..
Followings steps are to show how to restrict access users for dashboard,pages and sections

Dashboard Restriction:
1.Click on catalog

2.Select Dashboard(s) on shared folders from the left side of page on Folders sections .

3.Click on permissions from the Tasks Section…..

4.Click on Add users/roles

5.Select list as users enter the name of users and click on search

6.Move to user(s) to selected Members , set the permission and  click on OK…

Page/Tab Restriction:
1.Click on dashboard and select the dashboard which you have to restrict…


2.Go to Page Options => Edit Dashboard


3.Go to Tools => Dashboard Properties


4.Select Tab which you want to restrict and click on permissions


5.Click on Add users/roles


6.Select list as users enter the name of users and click on search


7.Move to user(s) to selected Members , set the permission and  click on OK…