ODI Architecture

 

The repository forms the central component of the ODI architecture. This stores configuration  information about the IT infrastructure; the metadata for all applications, projects, scenarios, and execution logs. Repositories can be installed in an online transaction processing (OLTP) relational database. The repository also contains information about the ODI infrastructure, defined by the administrators. The two types of ODI repositories are master and work repositories.

 At design time, developers work in a repository to define metadata and business rules. The resulting processing jobs are executed by the agent, which orchestrates the execution by leveraging existing systems. The agent connects to available servers and asks them to execute the code. It then stores all return codes and messages in the repository. The agent also stores statistics, such as the number of records processed, and the elapsed time. Several repositories can coexist in an IT infrastructure. The graphic in this slide shows two repositories: one for the development environment and the other for the production environment. Developers release their projects in the form of scenarios that are sent to production.

In production, these scenarios are scheduled and executed on a Scheduler Agent that also stores all its information in the repository. Operators have access to this information and can monitor the integration processes in real time. Business users, as well as developers, administrators, and operators, can gain Web-based read access to the repository by using the ODI Console.