• To make Decision quickly
• To Data Visualization and Dashboard Design
• To understand Business Performance Management Systems
• To get the solution for business growth

• SQL developers
• Project Managers
• Database Professionals
• Mainframe Professionals
• Who want to become Business Object Professionals and Business Intelligence Professionals
• Entry-level trainees

• Basic knowledge of SQL
• Basic knowledge of Reports
• Basic knowledge of MS Excel

• Presentation server:Which convert the request comes from end user to logical SQL and sends it to Oracle BI Server.
• Oracle BI server: TheBI server is converting the logical sql to Physical sql so that database will understand the sql.
• Database: Database fetches the required result using the Physical query

There are following main features of OBIEE:

• Hierarchy Drilling (Drill up and Drill down)
• Report and Dashboard Scheduling
• Graphical Reporting
• Ad Hoc Analysis
• Global support and development capability

• Collecting Business Requirements from Business people
• Identify source systems which is required to develop suitable reports
• Design ETL to load data from source to the Data Warehouse
• Creating repository
• Create reports and dashboards
• Set up security
• Build cache mechanism and aggregations
• Testing and QA.

The OBIEE can connect to Sources like Relational Databases like Oracle, SQL Server, Cubes or Flat files can be connected to OBIEE.

OBIEE repository contains metadata of Same Data base or different databases. It contains following information:

• Data Modelling
• Connectivity Information
• SQL Information
• Aggregate Navigation
• Security
• Caching

Physical Layer (Schema Design): Contains the Schema information and place where import the tables from source.

Business Model Layer: Where hierarchy can be build and multiple LTS is possible.

 Presentation Layer: Presentation layer is used to provide object level security and provide customized views of Business Model in Business Model layer to users.

Physical layer is used for:

• Importing data
• Creating Aliases
• Building physical joins
• Setting up connection pool and its properties
• Enabling/ Disabling cache for individual table

Physical layer joins are called as physical joins and attributes can be joined using either equal operator or using any expression.

BMM layer joins are called as logical joins and can be define as inner join or Left join or Right join.

In physical join we can’t define type of join and in logical join we can’t make expression or greater than or less than in join.

Connection pool contains the data base information and is useful to import meta data into Physical layer.

Alias table is exactly replica to any physical table in Physical layer. If any changes are happened in main table it will reflect in alias table also.

Duplicate table is replica of main table at an instance only, If any changes are happed in main table it will not reflect in duplicate table.

In any join there is a table used in more than once then t is called as circular join.

There are 4 types of variables in OBIEE

• Repository variable
• Session variable
• Presentation variable
• Request variable

To define dynamic repository variable using any SQL expression Initialization block is needed.

The main object in presentation layer is Subject area and defines one subject area for one business entity.

The tables which are available in presentation layer is Presentation tables and it might be built by using one or more physical tables.

Cache is log of any query developed in Analytics page. Go to manage and get identity and select any user then you can define log level for that particular user or role.

Manual purging

Using EPT tables

By setting cache persistence time at table level.

Go to manage in RPD and click on identity and click on active user filter and give value as * and enter, you will get all user list.

Event pooling table is used to purge data automatically having table information whose cache should be purge.

Analytics page: Presentation server component.

Console: WebLogic server component.

Enterprise Manager: BI server component.

• Bar
•  Line
•  Area
•  Pie
•  Line-Bar
•  Time Series Line
•  Pareto
•  Scatter
•  Bubble
•  Radar

Instanceconfig.xml

Go to administration and click on manage session

BI presentation server cache

BI server cache

Data Base cache

Click on advance tab in analytics age and click on the check box bypass BI presentation server cache.

To navigate one report to another report or another dashboard or web page action links are used.

Agent is used to schedule report or dash board agent is used.

Dash board published content in OBIEE and contains one or more than one report in a dash board page.

EM is Fusion middle ware control page and it controls the all BI server components.

EM is the place where RPD and catalog deployment process is going on.

Console is Weblogic Server web page, and is useful to control the Admin server and managed servers.

Operation process management network control is the BI control component to control the BI server components like Presentation server, Java host, BI publisher etc.

Node manager is the bridge between admin server and managed server in Weblogic server.

Getting report in Analytics page by writing SQL query without RPD Meta data.

Update the values in report directly in report and will be updated in Data base called right back.

• Object level security
• Data level security

There are two reports and the second report is navigated through first report called master detail report.

Level based hierarchies

Skipped and Ragged hierarchies

Parent child hierarchies

Catalog manager is window component and is used to connect to catalog.

Job manager is also window based component and is used to monitor the scheduled jobs.

Opaque is a view build by SQL query in physical layer in RPD.

Multi user development environment is used to work multiple people on a same RPD and to deploy their work without disturbing others work.

To find the usage of reports by the users called usage tracking, We need set of configurations are needed for this Usage tracking.

To guide the OBIEE to build query by using specific tables we will define implicit fact column in Presentation layer columns.

• Ago
• To date
• Period Rolling