Oracle Data Integrator 12c Architecture.

Answer:-









Oracle Data Integrator 12c Architecture





1) 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.



2) Graphical User Interfaces:-









The Graphical User Interface is called as ODI Studio. The ODI Studio is used to access the Master and Work Repositories. The various tools/components (which will be discussed below) within the ODI Studio help in administering the infrastructure, developing projects, scheduling and monitoring executions.



ODI provides 4 tools to manage different aspects and steps of an ODI project:

• Designer


• Operator


• Topology Manager


• Security Manager

A. Designer





The Designer Navigator is the component of ODI where the most metadata of a project will be defined. It is used for designing ODI metadata and mapping objects. Some of the metadata components defined in a designer are as follows:



Models: Models are basically the source or target definitions in an integration project. ODI supports models on various technologies; some of them are Oracle, DB2, Teradata, XML, Flat Files, Web Services, etc.



Projects: Projects are the components that hold all the loading and transformation rules either for a functional module or an entire enterprise data warehouse. Some of the components in the projects are interfaces, procedures and packages.





B. Operator





In the operator navigator, you can monitor the execution of interfaces, packages, scenarios or load plans. The step by step session monitoring helps in performing debugging as well.



C. Topology Manager



The topology manager is used to describe the logical and physical architecture of the information system. The topology manager reads and writes only to the master repository as it maintains the technologies, data servers, schemas, contexts and other related information for each of the physical environments. This enables ODI to execute the same integration interfaces across different physical environments.



D. Security Manager



The security manager as called is used for managing security in ODI. Users and Profiles can be created here and privileges can be assigned to these users or profiles. The security manager metadata that is defined will be stored in the master repository.





3) Run-Time Agents:-







At runtime, the Agent coordinates the execution of the ODI sessions. It retrieves the code stored in the ODI repository, connects to the various source and target systems and orchestrates the overall data integration process. There are three types of Agents in Oracle Data Integrator 12c:



• Standalone Agents can be installed on the source or target systems and require a Java Virtual Machine.



• Colocated Standalone Agents can be installed on the source or target systems as well. They can be managed using Oracle Enterprise Manager and must be configured with an Oracle WebLogic domain. Colocated Standalone Agents can run on a separate machine from the Oracle WebLogic Administration Server.



• Java Enterprise Edition (Java EE) Agents are deployed on Oracle WebLogic Server and can benefit from the application server layer features such as clustering for High Availability requirements. Java EE Agents can be managed using Oracle Enterprise Manager.



4) ODI SDK:-



The ODI 12c SDK provides a mechanism to accelerate data integration development using patterns and the APIs in the SDK.

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.





5) ODI Console:-





The ODI Console is a web-based user interface (UI) where business users, developers, administrators and operators can have read access to the repository. These business users can also perform topology configuration and production operations.



Deployed on Oracle Weblogic Server.

Plug-in available to integrate with the Oracle Fusion Middleware Control Console.