OBIEE - BI Server Variables (session and repository)

> Reporting and Data Access Tools > Oracle Business Intelligence (OBIEE/Siebel Analytics) > OBIEE - BI Server (OBIS|nqsserver|nqs)

1 - About

The OBI Server can handle two types of variable :

In essence, a repository variable is the default value of a session variable.

The presentation service (dashboard) offers also a variable : The presentation variable

You can see their value and type in the session manager.

You can use them in BI Presentation Service, BI Server and Scheduler.

They are initialized with the help of an init block

Advertising

3 - Type of server variable

3.1 - Repository

A repository variable is a BI server variable that doesn't depend of the user (then of the login process).

You have two kind of repository variable :

  • Static (of a constant)
  • Dynamic (which is calculated/refresh periodically).

3.2 - Session

Session Variable are the second type of variable and depend of the user. When the user log in BI Presentation Service, they are initialized.

You have two kind of session variable :

  • Session System (reserved by OBIEE)
  • Session Non System (for your own purpose)

3.2.1 - Session System

Session System variables are session variables that the Oracle BI Server and Oracle BI Presentation Services use for specific purposes. System session variables have reserved names, that cannot be used for other kinds of variables (such as static or dynamic repository variable and nonsystem session variables).

3.2.2 - Session Non System

Session Non System variable are variable that you can create for your own purpose. You can set in:

Advertising

3.2.3 - Parameters

3.2.3.1 - Enable any user to set the value

You can set the session variable:

3.2.3.2 - Security Sensitive

When using a row-level database security strategy, such as a Virtual Private Database (VPD), the returned data results are contingent on the authorization credentials of the user.

For variables that you are using for authentication, in the Session Variable dialog, select Security Sensitive to identify them as sensitive to security when using a row-level database security strategy. This option ensures that cache entries are marked with the security-sensitive variables, enabling security-sensitive variable matching on all incoming queries.

This parameter is used to determine if the cached result of a logical sql can be shared between different users. See SAGetSharedRequestKey

4 - Support

5 - Documentation / Reference

Advertising