Tag Archives: bi apps architecture

Oracle Data Integrator(ODI) Component Architecture

The Oracle Data Integrator platform integrates in the broader Fusion Middleware platform and becomes a key component of this stack. Oracle Data Integrator provides its run-time components as Java EE applications, enhanced to fully leverage the capabilities of the Oracle WebLogic Application Server. Oracle Data Integrator components includes the FMW exclusive features for Enterprise-Scale Deployments, high availability, scalability, and hardened security.

Oracle Data Integrator Component Architecture

ODI Repositories

The central component of the architecture is the Oracle Data Integrator Repository. It stores configuration information about the IT infrastructure, metadata of all applications, projects, scenarios, and the execution logs. The architecture of the repository is designed to allow several separated environments that exchange metadata and scenarios (for example: Development, Test, Maintenance and Production environments). The repository also acts as a version control system where objects are archived and assigned a version number.

The ODI Repository is composed of one Master Repository and several Work Repositories. Objects developed or configured through the user interfaces are stored in one of these repository types.

Master Repository:

There is usually only one master repository that stores the following information:

  • Security information including users, profiles and rights for the ODI platform
  • Topology information including technologies, server definitions, schemas, contexts, languages and so forth.
  • Versioned and archived objects.

Work Repository:

The work repository is the one that contains actual developed objects. Several work repositories may coexist in the same ODI installation (for example, to have separate environments or to match a particular versioning life cycle). A Work Repository stores information for:

  • Models, including schema definition, data stores structures and metadata, fields and columns definitions, data quality constraints, cross references, data lineage and so forth.
  • Projects, including business rules, packages, procedures, folders, Knowledge Modules, variables and so forth.
  • Scenario execution, including scenarios, scheduling information and logs.

When the Work Repository contains only the execution information (typically for production purposes), it is then called an Execution Repository.

ODI Studio and User Interfaces:

Administrators, Developers and Operators use the Oracle Data Integrator Studio to access the repositories. This Fusion Client Platform (FCP) based UI is used for administering the infrastructure (security and topology), reverse-engineering the metadata, developing projects, scheduling, operating and monitoring executions.

ODI Studio provides four Navigators for managing the different aspects and steps of an ODI integration project:

  • Designer Navigator is used to design data integrity checks and to build transformations such as for example:
    • Automatic reverse-engineering of existing applications or databases
    • Graphical development and maintenance of transformation and integration interfaces
    • Visualization of data flows in the interfaces
    • Automatic documentation generation
    • Customization of the generated code

  • Operator Navigator is the production management and monitoring tool. It is designed for IT production operators. Through Operator Navigator, you can manage your interface executions in the sessions, as well as the scenarios in production.

  • Topology Navigator is used to manage the data describing the information system’s physical and logical architecture. Through Topology Navigator you can manage the topology of your information system, the technologies and their data types, the data servers linked to these technologies and the schemas they contain, the contexts, the languages and the agents, as well as the repositories. The site, machine, and data server descriptions will enable Oracle Data Integrator to execute the same integration interfaces in different physical environments.

  • Security Navigator is the tool for managing the security information in Oracle Data Integrator. Through Security Navigator you can create users and profiles and assign user rights for methods (edit, delete, etc.) on generic objects (data server, data types, etc.), and fine-tune these rights on the object instances (Server 1, Server 2, and so forth).


Oracle Data Integrator also provides a Java API for performing all these run-time and design-time operations. This Oracle Data Integrator Software Development Kit (SDK) is available for standalone Java applications and application servers.

Run-Time Agent:

At design time, developers generate scenarios from the business rules that they have designed. The code of these scenarios is then retrieved from the repository by the Run-Time Agent. This agent then connects to the data servers and orchestrates the code execution on these servers. It retrieves the return codes and messages for the execution, as well as additional logging information – such as the number of processed records, execution time and so forth – in the Repository. The Agent comes in two different flavors:

  • The Java EE Agent can be deployed as a web application and benefit from the features of an application server.
  • The Standalone Agent runs in a simple Java Machine and can be deployed where needed to perform the integration flows.

Both these agents are multi-threaded java programs that support load balancing and can be distributed across the information system. This agent holds its own execution schedule which can be defined in Oracle Data Integrator, and can also be called from an external scheduler. It can also be invoked from a Java API or a web service interface.

Oracle Data Integrator Console

Business users (as well as developers, administrators and operators), can have read access to the repository, perform topology configuration and production operations through a web based UI called Oracle Data Integrator Console. This web application can be deployed in a Java EE application server such as Oracle WebLogic.

To manage and monitor the Java EE and Standalone Agents as well as the ODI Console, Oracle Data Integrator provides a new plug-in that integrates in Oracle Fusion Middleware Control Console.



Tags: , , , , , , , , , , , , ,

BI Apps Architecture Overview

“Oracle Business Intelligence Applications are complete, prebuilt BI solutions that deliver intuitive, role-based intelligence throughout an organization. These solutions enable organizations to gain more insight and greater value from a range of data sources and applications including Oracle E Business Suite, PeopleSoft, JD Edwards, Siebel, and third party systems.”

Oracle BI Applications are built on the Oracle BI Suite Enterprise Edition, a comprehensive and market leading BI platform. This enables organizations to realize the value of a packaged BI application, such as rapid deployment, lower TCO, and built-in best practices, or to build custom BI applications—all on one common BI foundation.”

The new BI Applications has been completely re-architected to leverage the power of ODI with its E-L-T architecture, and has new Out of box tools to increase the productivity and lower down the TCO. The BI Apps has significantly expanded with new analytical contents.

The BI Apps components:

  • Source Systems: The Oracle or non-oracle OLTP systems that holds the data for ETL into the Oracle Business analytics warehouse. This data becomes the underlying data for your analyses and includes customer information, inventory, sales, marketing, accounts, and other types of data you collect about your business.
  • Oracle Business Intelligence Enterprise Edition: Oracle Business Intelligence Enterprise Edition (Oracle BI EE) is a business intelligence platform that is used to access and present data in easy-to-understand formats, such as tables, graphs and Scorecards/KPIs.
  • Oracle Business Analytics Warehouse: The Oracle Business Analytics Warehouse is a modular enterprise-wide data warehouse data model with conformed dimensions for data integrated from multiple sources. The Oracle Business Analytics Warehouse supports the analytical requirements of Oracle Business Intelligence Applications.
  • Oracle BI Applications Configuration Manager (BIACM) and Functional Setup Manager (FSM):  This is similar to DAC tool. But unlike DAC, The BIACM and FSM have great features and functionality in BI APPS to simplify the configurations process, minimize the manual steps and configurations, and to have a guided list of configurations steps and checklists.  That reduces the dependency on documentation….
    •  Oracle BI Applications Configuration Manager (BIACM):  The BIACM is a web based UI application for setting up and maintaining an Oracle Business Intelligence Applications environment. Oracle BI Applications Configuration Manager works in conjunction with Functional Setup Manager to provide guided Tasks to configure Offerings and Functional Areas.
    • Functional Setup Manager (FSM): The FSM is also a web based UI application which enables you to manage and perform functional configuration tasks and to deploy the Offering and Functional Areas that were selected. Functional Setup Manager generates a list of configuration tasks for the deployed areas, which you can assign to different functional developers and monitor the implementation status.
  • Oracle Data Integrator: Oracle BI Applications uses Oracle Data Integrator (ODI) as its data integration platform. Oracle Data Integrator is a comprehensive data integration platform that covers all data integration requirements: from high-volume, high-performance batch loads, to event-driven, trickle-feed integration processes, to SOA-enabled data services with its innovative E-LT Architecture.  

    E-LT is an innovative approach to extracting, loading and Transforming data. Typically ETL application vendors have relied on costly heavyweight; mid-tier server to perform the transformations required when moving large volumes of data around the enterprise. ODI delivers unique next-generation, Extract Load and Transform (E-LT) technology that improves performance and reduces data integration costs, even across heterogeneous systems by pushing the processing required down to the typically large and powerful database servers already in place within the enterprise. 

    In an Oracle BI Applications environment, ODI works in conjunction with Oracle BI Applications Configuration Manager, which provides a user interface for managing load plans as well as access to ODI Console, the web-based console that enables you to view objects in the ODI repository.

  • Oracle GoldenGate: Oracle GoldenGate is an optional product. Oracle GoldenGate is a data replication tool leveraged to create a replicated OLTP schema. This replicated OLTP schema is used as a Source- Dependent Schema during ETL.

A logical Overview of BI Apps


Oracle BI Applications use all of the components depicted in above figure to deliver information specific to your business needs. The source system (OLTP) data is loaded into the Business Analytics Warehouse Database (OLAP) and it is transformed using the ODI mappings that are stored in the BI Applications Repository Database. This database contains the repository information for BI Applications ODI repository and the BI Applications Components Repository.

Optionally, you can leverage Oracle GoldenGate to replicate your OLTPs data and then to do Source – Dependent load. This helps us to least dependent on the source system availability for ELT operations.



Shiva Molabanti


Posted by on May 9, 2013 in OBI EE, OBIEE 11g, Weblogic


Tags: , , , , , , , , , , , , , , , ,