OBIEE Presentation Variable Syntax

Usually, we will use presentation variable which holds only one value.

Syntax:

@{Presentation_Variable_Name}

What if , there is a scenario where the user selection in prompt is multiple selection.

Then the normal syntax to call presentation variable doesn't work.

Solution for this scenario is, using the different syntax for presentation variable which contains multiple values.

Syntax:

@{Presentation_Variable_Name}['@']{'Default'}

OBIEE Presentation Variable Syntax

Usually, we will use presentation variable which holds only one value.

Syntax:

@{Presentation_Variable_Name}

What if , there is a scenario where the user selection in prompt is multiple selection.

Then the normal syntax to call presentation variable doesn't work.

Solution for this scenario is, using the different syntax for presentation variable which contains multiple values.

Syntax:

@{Presentation_Variable_Name}['@']{'Default'}

Physical Layer – Connection Pool

The connection pool contains information about the connection between Oracle BI Server and a data source. For each data source, there is at least one corresponding connection pool.

Components of Connection Pool

1. Connection Pool name: Name of the connection pool.

2. Call Interface: The call interface represents the driver which you use to connect to the data source. There are three kinds ODBC, OCI, XML.

3. Maximum Connections: Mention the maximum connections based on the concurrent users in the organization. Once this limit is reached, the Oracle BI Server routes all other connection requests to another connection pool if available or, if no other connection pools exist, the connection request waits until a connection becomes available. Increasing the allowed number of concurrent connections can potentially increase the load on the underlying database accessed by the connection pool. Ensure the right connections are provided.

4. Require fully qualified table names: When this option is selected, all requests sent from the connection pool use fully qualified names to query the underlying database.

5. Data source name (DSN): Name of the DSN

6. Share Logon: If this option is checked, then all connections to the database that uses the connection pool will use the user name and password specified in the connection pool. If this option is not selected, connections through the connection pool use the database user ID and password specified in the DSN or in the Siebel user profile.

7. Enable Connection Pooling: It allows multiple concurrent query requests to share a single database connection. This reduces the overhead of connecting to a database because it does not open and close a new connection for every query. If you do not select this option, each query sent to the database opens a new connection.

8. Use multithreaded connections: When the check box is selected, Oracle BI Server terminates idle physical queries (threads). When not selected, one thread is tied to one database connection. Even if threads are idle, they consume memory.

9. Execute queries synchronously: This provides the way to communicate with Oracle Database, if this option is checked, it is run asynchronously. If this option is not checked, the query is run synchronously. It is always uncheck by default.

10. Parameters supported: If this option is checked, that means all the DB parameters mentioned in the DB features are supported by server. By default, this option will be checked.

11. Isolation level: This option controls the transaction locking behavior for all statements issued by a connection. There are four kinds

a. Committed Read: Locks are held while the data is read to avoid dirty reads. Data can be changed before the transaction ends with that connection.

b. Dirty Read: Locking Can read uncommitted or dirty data, change values in data during read process in a transaction. Least restrictive of all types.

c. Repeatable Read: Places locks on all data used in a query so that nobody can update the data. However new rows can be inserted by other users but will be available in later reads in the current transaction.

d. Serialization: Places a range lock on data set preventing other users to insert or update the rows in data set until the transaction is complete. Most restrictive of all.

Physical Layer – Connection Pool

The connection pool contains information about the connection between Oracle BI Server and a data source. For each data source, there is at least one corresponding connection pool.

Components of Connection Pool

1. Connection Pool name: Name of the connection pool.

2. Call Interface: The call interface represents the driver which you use to connect to the data source. There are three kinds ODBC, OCI, XML.

3. Maximum Connections: Mention the maximum connections based on the concurrent users in the organization. Once this limit is reached, the Oracle BI Server routes all other connection requests to another connection pool if available or, if no other connection pools exist, the connection request waits until a connection becomes available. Increasing the allowed number of concurrent connections can potentially increase the load on the underlying database accessed by the connection pool. Ensure the right connections are provided.

4. Require fully qualified table names: When this option is selected, all requests sent from the connection pool use fully qualified names to query the underlying database.

5. Data source name (DSN): Name of the DSN

6. Share Logon: If this option is checked, then all connections to the database that uses the connection pool will use the user name and password specified in the connection pool. If this option is not selected, connections through the connection pool use the database user ID and password specified in the DSN or in the Siebel user profile.

7. Enable Connection Pooling: It allows multiple concurrent query requests to share a single database connection. This reduces the overhead of connecting to a database because it does not open and close a new connection for every query. If you do not select this option, each query sent to the database opens a new connection.

8. Use multithreaded connections: When the check box is selected, Oracle BI Server terminates idle physical queries (threads). When not selected, one thread is tied to one database connection. Even if threads are idle, they consume memory.

9. Execute queries synchronously: This provides the way to communicate with Oracle Database, if this option is checked, it is run asynchronously. If this option is not checked, the query is run synchronously. It is always uncheck by default.

10. Parameters supported: If this option is checked, that means all the DB parameters mentioned in the DB features are supported by server. By default, this option will be checked.

11. Isolation level: This option controls the transaction locking behavior for all statements issued by a connection. There are four kinds

a. Committed Read: Locks are held while the data is read to avoid dirty reads. Data can be changed before the transaction ends with that connection.

b. Dirty Read: Locking Can read uncommitted or dirty data, change values in data during read process in a transaction. Least restrictive of all types.

c. Repeatable Read: Places locks on all data used in a query so that nobody can update the data. However new rows can be inserted by other users but will be available in later reads in the current transaction.

d. Serialization: Places a range lock on data set preventing other users to insert or update the rows in data set until the transaction is complete. Most restrictive of all.

OBIEE 11g Architecture

OBIEE 11g Architecture 

Domains in OBIEE

Web Logic Server Domain

•      J2EE App Server used across the board for all 11g BI applications

•      Contains :

  Managed Server: Set of J2EE Applications used for “functioning” the BIEE system

 Admin Server: Set of J2EE Applications used for “administering” of BI EE system

·         Oracle Process Manager and Notification Server (OPMN) domain

•      Used to start/Stop system components (BI Svr, BI Pres Svr, BI Schdlr, BI ClustrCntrl)

•      Can be accessed from CMD or from EM page (GUI)

 Admin Server Components

•     WLS Admin Console

•      Admin GUI for WLS,Security and J2EE Components

•     Fusion Middleware-EM Control (FMW EM)

•      Admin GUI to Manage the BI Domain

•      JMX Beans

•      Java components that provide programmatic access for managing a BI domain.

Managed Server Components

•      BI Plugin: Sends web http requests to BI Presentation Services

•      BI Security: Integrates BI Server and FMW sec platform (using webservice calls)

•      BI Action Services: Dedicated web services for Action framework

•      BI Web Service SOA: Provides Web services for objects in the BIEE Presentation Catalog, to invoke analysis, agents, and conditions.

•      BI Office: Provides the integration between Oracle Business Intelligence and Microsoft Office products

BIEE Domain System Components

•     BI Server

–     Provides capabilities to query and access data as well as services for accessing and managing the RPD file (BIEE Metadata).

•     BI Presentation Services

–     Provides the framework and interface for the presentation of business intelligence data to Web clients. It maintains an Oracle BI Presentation Catalog service on the file system for the customization of this presentation framework.

•     BI Scheduler     

–      Provides framework for scheduling and delivering reports to users (used by delivers)

•     BI Javahost

–     Enables BI Presentation Services to support various components: Java tasks for BI Scheduler, BI Publisher, and Graph generation.

•     BI Cluster Controller

–     Used for distributing requests to BI server and ensure load balancing

•     Files

–     Repository file (e.g. SampleSales.rpd)

–     Config Files (nQconfig.ini, instanceconfig.xml,)

–     Log Files (nqserver.log, nqquery.log, nqscheduler.log, sawlog0.log etc)

–     Presentation catalog(<MW_HOME>\OracleBIPresentationServicesComponent\coreapplication_obips1\catalog)

OBIEE 11g Architecture

OBIEE 11g Architecture 

Domains in OBIEE

Web Logic Server Domain

•      J2EE App Server used across the board for all 11g BI applications

•      Contains :

  Managed Server: Set of J2EE Applications used for “functioning” the BIEE system

 Admin Server: Set of J2EE Applications used for “administering” of BI EE system

·         Oracle Process Manager and Notification Server (OPMN) domain

•      Used to start/Stop system components (BI Svr, BI Pres Svr, BI Schdlr, BI ClustrCntrl)

•      Can be accessed from CMD or from EM page (GUI)

 Admin Server Components

•     WLS Admin Console

•      Admin GUI for WLS,Security and J2EE Components

•     Fusion Middleware-EM Control (FMW EM)

•      Admin GUI to Manage the BI Domain

•      JMX Beans

•      Java components that provide programmatic access for managing a BI domain.

Managed Server Components

•      BI Plugin: Sends web http requests to BI Presentation Services

•      BI Security: Integrates BI Server and FMW sec platform (using webservice calls)

•      BI Action Services: Dedicated web services for Action framework

•      BI Web Service SOA: Provides Web services for objects in the BIEE Presentation Catalog, to invoke analysis, agents, and conditions.

•      BI Office: Provides the integration between Oracle Business Intelligence and Microsoft Office products

BIEE Domain System Components

•     BI Server

–     Provides capabilities to query and access data as well as services for accessing and managing the RPD file (BIEE Metadata).

•     BI Presentation Services

–     Provides the framework and interface for the presentation of business intelligence data to Web clients. It maintains an Oracle BI Presentation Catalog service on the file system for the customization of this presentation framework.

•     BI Scheduler     

–      Provides framework for scheduling and delivering reports to users (used by delivers)

•     BI Javahost

–     Enables BI Presentation Services to support various components: Java tasks for BI Scheduler, BI Publisher, and Graph generation.

•     BI Cluster Controller

–     Used for distributing requests to BI server and ensure load balancing

•     Files

–     Repository file (e.g. SampleSales.rpd)

–     Config Files (nQconfig.ini, instanceconfig.xml,)

–     Log Files (nqserver.log, nqquery.log, nqscheduler.log, sawlog0.log etc)

–     Presentation catalog (<MW_HOME>\OracleBIPresentationServicesComponent\coreapplication_obips1\catalog)