ODI Series Learning-the overall architecture concept

ODI overall architecture does not have Oracle database complex, because it belongs to the use of program functions, more is the program development and configuration of work, of course, the optimization of the ODI involves a lot of database optimization work, from the overall architecture, the foundation has, the overall grasp will be much simpler.

First understand the several components of the ODI component, the ODI database, and finally the relationship between the components and the database.

ODI is a platform for data integration. Simply speaking, it is in different information systems or databases to do data transmission, conversion. ODI is also a development platform for data integration, covering 2 main areas:

1.ODI is a service-driven model and can understand a commercially driven model that focuses more on how to comply with business rules rather than concentrating development efforts on the technical level.

2.ODI using ELT in the process of data integration, it itself does not perform the processing of data integration, so the implementation is done in the existing information system or database.

ODI is based on meta-data management. Metadata repositories are information systems or database data and their contents. They are centrally stored in a single database.

The ODI enables simple and fast integration. Simple and non-concise, fast non-small.

The core component of this entire architecture is the database (Repository). It stores the configuration information for the IT architecture, the metadata for all apps, projects, stories, and execution logs. Repositories can be installed on an RDBMS, which is a relational database. The database also contains information about the ODI schema. Administrators, developers, and executives can access the database using the different operations interface of ODI. The security interface and Topology Manager interface is used to manage the architecture, and the designer is used for metadata reverse or reverse engineering as well as project development, interfaces, etc., which the operator uses to dispatch and perform real-time operations.

ODI is divided into the design phase and the execution stage. During the design phase, developers define metadata, business rules, and constraints. This processing job is done by the agent in the existing information system. It connects to the available servers and executes the code with the server. It stores all the returned code and messages into the repository. It also stores statistical information, such as the number of records processed, processing time, and so on.

Different repositories can exist in the same it architecture at the same time. The database of the design phase and the database at the execution stage can exist simultaneously. The developer transmits the project to the production environment in the designer by publishing it as a story. In the production environment, these scenarios are scheduled by the job, dispatched by the agent, and the dispatch agent stores information for all repositories. The operator operator is a process that always provides real-time access and monitoring of data consolidation. Business users can also access the ODI repository on the web like developers, administrators, and operators. The ODI has a meta data navigation function, which is a Java EE application server that can directly connect to the ODI database.

ODI Series Learning-the overall architecture concept