© Copyright VLR Training | 2020
Oracle data integrator online training offer by vlr training. One of the best Oracle data integrator online training institute in Hyderabad, Oracle Data Integrator (ODI) is an Extract, load and transform (ELT) (in contrast with the ETL common approach) tool produced by Oracle that offers a graphical environment to build, manage and maintain data integration processes in business intelligence systems.
Oracle Data Integrator, or ODI, provides a new declarative design approach to defining data transformation and integration processes based on a unique Extract-Load-Transform (ELT) architecture. The declarative design approach separates the declarative rules from the implementation details. ODI architecture eliminates the need for a standalone ETL (Extract-Transform-Load) server and proprietary engine while leveraging the inherent power of RDBMS engines.
Some of the key features that would help in making a decision if Oracle Data Integrator satisfies the data integration needs are:
Repositories are the central component of Oracle Data Integrator architecture. Objects developed or configured through the user interfaces are stored in the repositories. There are two types of repositories in ODI:
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.
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:
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.
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.
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.
The run-time agents are responsible for executing the interfaces/packages/scenarios in ODI. The agents retrieve the code from the repository and orchestrate the execution of the code on the data servers. It also retrieves the return codes and messages for the execution. There are two types of agents in ODI:
1. Standalone Agent
2. Java EE Agent
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.