Explain OBIEE Architecture & Components in Oracle BI

1 / 55

OBIEEbeginner

OBIEE Architecture & Components

Understand the layered architecture of OBIEE — Presentation Services, BI Server, and the underlying data sources — and how a request flows through them.

Oracle Business Intelligence Enterprise Edition (OBIEE) is not a single monolithic tool; it's a stack of cooperating services, each with a distinct job. Interviewers ask about architecture early because it tells them whether you understand *why* a dashboard is slow or *where* a security rule actually gets enforced, rather than just knowing how to click through the web UI.

Think of a restaurant: Presentation Services is the waiter taking your order and plating the food, the BI Server is the kitchen translating "a burger" into precise cooking instructions for whichever station (grill, fryer) has the ingredients, and the physical databases are the pantries each station pulls from.

Key Concepts

At the front is Presentation Services (obips), which renders the dashboard/analysis UI, manages user sessions, and talks to the BI Server (obis, also called the Oracle BI Server or nqsserver) using a proprietary protocol. The BI Server is the brains of the operation — it holds the RPD (repository) metadata, translates logical SQL into physical SQL for each source, and returns a unified result set even when the query spans multiple databases. Below that sit the actual data sources: Oracle Database, Essbase, Hyperion, flat files, or any ODBC/JDBC source registered in the RPD's physical layer.

Presentation ServicesBI Serverobipsobisnqsserver

Supporting these two core services are Java Host (for Java-based extensions like Actions and R integration), the Scheduler/Job Manager (for iBots and agents), and Security providers (typically WebLogic's embedded LDAP or an external LDAP/Active Directory/SSO provider). All of this runs inside WebLogic Server (WLS), which is why OBIEE troubleshooting often means checking managed server logs in $DOMAIN_HOME/servers/*/logs alongside the BI-specific logs.

Java HostScheduler/Job ManagerSecurity providersWebLogic Server (WLS)$DOMAIN_HOME/servers/*/logs

The request lifecycle matters for interviews: a user opens an analysis, Presentation Services sends logical SQL to the BI Server, the BI Server consults the RPD to generate one or more physical SQL statements, executes them (or serves from cache), aggregates/joins results in memory if the query spans multiple physical sources, and returns the result set back up the chain for rendering. Knowing this flow lets you reason about where a slow query, a security leak, or a caching bug actually lives.