Explain Oracle EBS Architecture Overview in Oracle Applications

1 / 60

EBSbeginner

Oracle EBS Architecture Overview

Understand the multi-tier architecture that underpins Oracle E-Business Suite R12

Oracle E-Business Suite (EBS) is built on a multi-tier architecture consisting of the desktop tier, application (middle) tier, and database tier. The desktop tier is where end users interact with the system through a browser, using Oracle Forms (via JInitiator/native Java plugin in older versions, or now via Web Forms) and OA Framework (OAF) self-service pages. This separation of concerns allows Oracle to scale each tier independently based on load.

Think of EBS like a restaurant: the desktop tier is the dining room where customers place orders, the application tier is the kitchen staff and expediters coordinating the work, and the database tier is the pantry and recipe book that holds all the actual ingredients and instructions.

Key Concepts

The application tier hosts the Forms Server, Web Server (Oracle HTTP Server built on Apache), Concurrent Processing Server, and Admin Server. Each of these services can be scaled horizontally across multiple nodes for high availability, and in R12.2 this tier introduced Online Patching using Edition-Based Redefinition (EBR), which allows patching without downtime.

Online Patching

The database tier stores all application data, PL/SQL packages, and metadata in an Oracle Database instance. EBS is essentially a giant PL/SQL and Forms-based application layered on top of a highly normalized relational schema, with thousands of tables, views, and packages organized by product family (AP, AR, GL, PO, etc.).

Understanding this architecture is fundamental for any consultant because performance issues, patching strategy, and customization decisions almost always map back to which tier is involved. For instance, a slow concurrent program points to the application tier's concurrent manager, while a slow report might point to database-tier SQL tuning.