OBIEE ARCHITECTURE AND

PHYSICAL LATER

OBIEE Architecture and Physical Layer 1

AGENDA FOR DISCUSSION

 OBIEE ARCHITECTURE
 ADMIN TOOL BASICS
 INTRODUCTION TO PHYSICAL LAYER
 HIRERACHY
 CONNECTION POOL DETAILS
 CONNECTION SCRIPTS

 SALES SCHEMA
DEMO ON MODELLING THE PHYSICAL LAYER
 Q & A SESSION

OBIEE Architecture and Physical Layer 2

 Oracle BI EE Architecture
Web Server Web Browser
SAW Bridge (J2EE/ISAPI) XML, HTML,
(IIS, Tomcat, Websphere, iPlanet) XLS, PDF, TXT
over
Oracle BI Web TCP/IP (SSL) HTTP/HTTPS

SOAP Web Services, XML and URL Interface Web

Catalog
Service
Oracle Interactive Oracle Answers HTML, SOAP
Dashboards
Oracle Delivers Server over
HTTP/HTTPS
User Profiling, Security and Session Mngmt XML
Scheduling/Event Services Framework
Agent Execution Logic TCP/IP Cache Services (Web) & Connection Mngmt
Device Adaptive Content (SSL)
ODBC over TCP/IP (SSL)

Oracle BI Server
Logical SQL ODBC/JDBC (Logical Business Model) Oracle BI Administration
Oracle BI
Load Balancer
Cluster Controller

Metadata Interchange
Session Management Metadata Management Services
Intelligent Request Generation
Multi-User Development Services

Logical Request Generation Metadata Documentation Services

Cache
Security Services

Services Navigator Server Management Services

Query Govern.

Multi-Pass /
Sub-Request Logic

System / Perf Monitoring

Fragmentation
Externalized Optimization
Authentication
Aggregate
LDAP
Navigator
DB Authentication
Optimized Query Rewrites
Custom Authenticator
Execution Engine

Data Source Adapters

ODBC, CLI, OCI, XML, MDX

OBIEE Architecture and Physical Layer 3
Analytical and Operational Data Sources
ADMIN TOOL BASICS
Admin tool is the Utility in OBIEE where we can do all the
Metadata Development . Some of the functionalities that Admin
tool covers are
 Dimension Modeling (Physical And Logical)
 Security
 Cache management
 Session View
 Database request
 Designing Variables
 Multi user Development Management
OBIEE Architecture and Physical Layer 4
ADMIN TOOL BASICS (Contd..)
The Meta Data Design in OBIEE is split into following 3 Layers
Physical Layer
• DB connections
• DB parameter Settings
• Physical data Model

Business Model Layer (BMM)

• Logical Data Model
• Dimension Hierarchies
• Aggregate Navigation
• Fragmentation
• Level Based Measures

Presentation Layer
•Arranging Presentation tables (User Experience)
• Object level Security
• Aliases

OBIEE Architecture and Physical Layer 5

INTRODUCTION TO PHYSICAL LAYER

Presentation BMM
Layer Layer
Physical
Layer

OBIEE Architecture and Physical Layer 6

INTRODUCTION TO PHYSICAL LAYER

Data Source Name

Connection
Pool

Schema name

Aliases

Tables

OBIEE Architecture and Physical Layer 7

HIRERACHY IN THE PHYSICAL LAYER

The folder structure the the Physical Layer is as Follow

OBIEE Architecture and Physical Layer 8

CONNECTION POOL DETAILS

OBIEE Architecture and Physical Layer 9

ISOLATION LEVEL
The following are the different isolation levels
 Committed Read
Allows to insert new records and allows to update the records that a transaction is
using and would reflect only after commit, In other words data can be changed before end of
transaction resulting in non repeatable reads.

 Repeatable Read
Allows to insert new records and places the locks on the al the data that is used in
the query to prevent anybody else updating the data.
 Serializable

Locks the dataset and does not allow to insert or update the data set until the
transaction is complete.
 Dirty read
With this option it is possible to read uncommitted data and have rows appear and
disappear before end of transaction

OBIEE Architecture and Physical Layer 10

CONNECTION SCRIPTS

OBIEE Architecture and Physical Layer 11

SALES SCHEMA

OBIEE Architecture and Physical Layer 12

SUMMARY

Oracle
BI Server DEMO

OBIEE Architecture and Physical Layer 13

SUMMARY

Oracle
BI Server Q&A

OBIEE Architecture and Physical Layer 14