Oracle Data Integrator Components
Oracle Data Integrator (ODI) is a software application based on ETL (extract-transform-load) structure used for data transformation and merging processes. In today's business the meaning of well organized data has increased dramatically and that is why having specialized software is so important.
Furthermore, these applications must be prepared to work in mixed systems and platforms environment and be sure that none of the quality will deteriorate. Oracle Data Integrator provides decalrative rules apart from implementation details and also its E-LT (extract-load, transform) structure eliminates need of having separate ETL server which results in optimized performance, efficiency and scalability.
Main architecture component in Oracle Data Integrator is the repository that is accessed by client-server mode or thin client mode. Repository is absolutely open, comprehensive, shared metadata database which is accessible for the applications responsible for transformation, project development, integration and information redistribution. Other architecture components are the Topology Manager, Designer, Security Manager, Operator, Agent, Scheduler and Metadata Navigator. Graphical interface module that manages all the information about system's physical and logical structure is called the Topology Manager. Descriptions created with the Topology Manager of server data, machine and site will allow to run same interfaces on different systems. A tool designed to develop transformations and to check data integrity is called Designer. Among many fuctions its most significant are visualization of data flow, development and maintenance data integration and transformation, reverse-engineering of applications or repository's data. Oracle Data Integrator permissions and users management tool is simply called Security Manager. Operator is the module responsible for monitoring and production management.
Agent executes application interfaces which Designer designed, next the Scheduler schedules them. Metadata Navigator browses through contents of Oracle Data Integrator Repository in search of wanted content. It is a thin client-oriented for search and analysis but also to manage all production processes, it can also trace and cross-reference data lineage. Apart from this standard modules comes a bunch of „out-of-the-box” modules which can be fully extensible, e.g. Log Miner, SQL Server Triggers, Oracle DBLink, Check MS Excel, Oracle Merge, Check Sybase – all as a part of Pluggable Knowledge Architecture are written for certain systems and environments and in fact are the very core of the Oracle Data Integrator, making the whole process accessible, modular and as simple as it can be. In case where our target is an Oracle database, natural choice is to go with Oracle Warehouse Builder, but where target is not an Oracle based environment, like SQL Server or XML, Teradata we can use Oracle Data Integrator to support OWB. When the source is XML or Web Service, SOAP then ODI supplements as well.
Clearly Oracle Data Integrator can be used in many different cases – e.g. when some dirty data has to be filtered out before loading, or data integration is very complicated or/and processed in real-time.
Oracle Data Integrator works as well in the staging and transforming area as the support for other Oracle software. It is „hot pluggable” which means connecting to any heterogeneous environment and still provide with number of required operations.
Thanks & Regards
WWW.ODIGURUS.COM
Oracle Data Integrator (ODI) is a software application based on ETL (extract-transform-load) structure used for data transformation and merging processes. In today's business the meaning of well organized data has increased dramatically and that is why having specialized software is so important.
Furthermore, these applications must be prepared to work in mixed systems and platforms environment and be sure that none of the quality will deteriorate. Oracle Data Integrator provides decalrative rules apart from implementation details and also its E-LT (extract-load, transform) structure eliminates need of having separate ETL server which results in optimized performance, efficiency and scalability.
Main architecture component in Oracle Data Integrator is the repository that is accessed by client-server mode or thin client mode. Repository is absolutely open, comprehensive, shared metadata database which is accessible for the applications responsible for transformation, project development, integration and information redistribution. Other architecture components are the Topology Manager, Designer, Security Manager, Operator, Agent, Scheduler and Metadata Navigator. Graphical interface module that manages all the information about system's physical and logical structure is called the Topology Manager. Descriptions created with the Topology Manager of server data, machine and site will allow to run same interfaces on different systems. A tool designed to develop transformations and to check data integrity is called Designer. Among many fuctions its most significant are visualization of data flow, development and maintenance data integration and transformation, reverse-engineering of applications or repository's data. Oracle Data Integrator permissions and users management tool is simply called Security Manager. Operator is the module responsible for monitoring and production management.
Agent executes application interfaces which Designer designed, next the Scheduler schedules them. Metadata Navigator browses through contents of Oracle Data Integrator Repository in search of wanted content. It is a thin client-oriented for search and analysis but also to manage all production processes, it can also trace and cross-reference data lineage. Apart from this standard modules comes a bunch of „out-of-the-box” modules which can be fully extensible, e.g. Log Miner, SQL Server Triggers, Oracle DBLink, Check MS Excel, Oracle Merge, Check Sybase – all as a part of Pluggable Knowledge Architecture are written for certain systems and environments and in fact are the very core of the Oracle Data Integrator, making the whole process accessible, modular and as simple as it can be. In case where our target is an Oracle database, natural choice is to go with Oracle Warehouse Builder, but where target is not an Oracle based environment, like SQL Server or XML, Teradata we can use Oracle Data Integrator to support OWB. When the source is XML or Web Service, SOAP then ODI supplements as well.
Clearly Oracle Data Integrator can be used in many different cases – e.g. when some dirty data has to be filtered out before loading, or data integration is very complicated or/and processed in real-time.
Oracle Data Integrator works as well in the staging and transforming area as the support for other Oracle software. It is „hot pluggable” which means connecting to any heterogeneous environment and still provide with number of required operations.
Thanks & Regards
WWW.ODIGURUS.COM
