Tuesday, 16 July 2013

OBIEE 11g/Essbase - Architecture

This blog is an attempt to explain OBIEE/Essbase g Architecture is a simplified manner. This is an extension to what I have blogged previously on OBIEE 11g Architecture. The addition of Essbase components would make it a perfect BI offering
The blog on OBIEE 11g can be accessed by following link
Key Architecture Points
Extensive use of Fusion Middleware (FMW) technology stack
WebLogic used as Application Server
Enterprise Manager (EM) used for system management
Introduction of OPMN for BI System components
Centralized Configuration Management i.e. modify on central server, propagate to other servers
Horizontal and Vertical Scale out procedures
Security – Oracle Platform Security Services
Everything Scriptable / Programmatic control
Architecture Terminology
A BI Domain consists of Java components that are deployed into one or more Java EE (JEE) containers within a single Weblogic domain; system (non-JEE) components and processes; and required configuration files, metadata repositories, and infrastructure.
A WebLogic Domain is a set of web logic instances servicing one or more J2EE applications
A WebLogic Admin Server is a JEE container that runs in a dedicated Java virtual machine with java components which provides a management of both the WebLogic and BI Domain. A WebLogic Domain contains one Admin Server.
A WebLogic Managed Server (Similar in concept to an OracleAS ‘OC4J’ instance) is a JEE container that runs in a dedicated Java virtual machine that provides the run-time environment for the Java-based services and applications within the system. An Oracle BI domain contains one or more Managed Servers that are distributed across one or more host computers.
A Node Manager provides process management services for Administration Server and Managed Server Processes. In short it is a daemon process that provides remote server start, stop and restart capabilities in addition to monitoring.
OPMN (Oracle Process Manager and Notification Server) maintains the Oracle Business Intelligence system components processes.
Oracle BI System Components are deployed as a non-JEE components, such as server processes and services written in C++ and J2SE. These provide the core services that enable Oracle Business Intelligence. The system components include BI Server (provides query and data access), Presentation Server (provides the framework and interface for the presentation of business intelligence data to Web clients), Scheduler (provides scheduling for analyses delivery), Cluster Controller (distributes requests to BI Server, ensuring requests for load balancing) and BI Java host (provides component services for presentation server to support java tasks for scheduler, publisher and graph generation).
Essbase System Components are deployed as a non-JEE components such as server process and services. The Essbase system components include Essbase Studio Server, Essbase Agent and Essbase Apps.
 Oracle BI J2EE Components are java components which are deployed as JEE applications to service SOAP, HTTP and other forms of requests. The major J2EE components includes BI Publisher (Enterprise Reporting Solution), BI Office (Integration with Microsoft Products), Action Framework Service (Dedicated Web Services), BI SAW Bridge Plug-in (Application that routes HTTP and SOAP requests), Security Services (Enable Integration of BI Server with Oracle FMW security Platform) and Web Services for SOA (Dedicated Web Services for SOA).
Oracle Essbase J2EE Components are java components which are deployed as JEE application to service SOAP, HTTP and other forms of requests. The major newly added Essbase J2EE components includes EAS, Financial Reporting, Hyperion Services Provider, workspace and calc Manager.
The additional J2EE components are Administrative Components (Enterprise Management application and JMX – MBeans for managing all configuration and run-time settings for Oracle Business Intelligence) and Oracle Real Time Decisions (Oracle RTD) – Enterprise Analytics Software for decision support system.
Fusion Middleware Technologies
The OBIEE 11g Architecture leverage on FMW technologies, some of the highlights are as follows
Web Logic Server (WLS) – Application Server, Required on every OBIEE machine, supports scripting with WLST
OPMN (Oracle Process Management Network) – Used for distributed process start/stop/restart, Process recovery (optional) and Process ‘Ping’ , Managed via Enterprise Manager ( EM) , can be used for performance collection( DMS), required on every OBIEE machine
DMS (Dynamic Monitoring System) – Standard FMW performance data collection format, allows collection of current and historical data, additional to perfmon, can be persisted to database, implemented by component teams (no control of content)
ODL (Oracle Diagnostic Logging) – Defines standard FMW Logging content and format, defines mechanism for analyzing diagnostics across s/w components and systems, support for ECID ( transaction ID) and implemented by component teams ( no control of content)
JPS (Java Platform Security) – offers an integrated suite security services to components in the Oracle stack – Authentication Service, Authorization Service, Policy Management Service ( Policy Store), User and Role Management Service ( Identity Store) , Credential Storage Service (CSF) and Auditing Service
CSF (Credential Store Framework) – provides secure handling of credentials used in BI system – looking at SSL certificates
OBIEE/Essbase Architecture
The architecture for Oracle Business Intelligence depends on whether the product is installed with the Simple Install type or the Enterprise Install type. With the Enterprise Install type, all architectural components are installed. With the Simple Install type, all architectural components are installed except Node Manager and the Managed Server
Single Host Architecture –Enterprise Install
Single host enterprise architecture has one JEE container for Web Logic Admin Server that runs in a dedicated Java virtual machine for management of Web Logic and BI domain and other JEE container that runs in dedicated Java virtual machine to provide the run-time environment for the java-based services and application within the system.

Single Host Architecture –Simple Install
A single install and simple install is similar to that of the Enterprise Single Host installation apart from following differences
  • The Node Manager is not installed.
  • All components that are part of the Managed Server in an Enterprise Install type are instead part of the Administration Server. The Managed Server is not installed.

Enterprise BI Architecture on Multiple Hosts
The Java components (WebLogic server domain) and the system components (BI instance) are clustered on each host as part of the single BI domain. The Administration Server exists on both hosts, but is only active on one host.

No comments:

Post a Comment