Introduction to ODI-Oracle Data Integrator Real-time Data Integration

Currently, complex "Hot swappable" systems and Service-Oriented Architecture (SOA) have been widely used, making it increasingly difficult to reasonably integrate data. Although your primary application database runs on the Oracle database, there may be other smaller systems running on the databases and platforms provided by other vendors. Your applications can interact with each other through technologies such as Web Services. applications and data can be managed remotely or managed in the enterprise data center.

Oracle Data Integrator is a series of Oracle Integrated middleware products that meet the Data integration requirements in an environment with an increasing degree of heterogeneity. It is a Java-based application that can use databases to execute collection-based data integration tasks. It can also be extended to multiple database platforms and Oracle databases. In addition, you can extract and provide conversion data through Web Services and messages, and create an integration process for responding to and creating events in a service-oriented architecture.

Oracle Data Integrator product architecture

Oracle Data Integrator is organized based on the Java graphics module and the modular information library for scheduling proxy access. The graphic module is used to design and build the integration process, and the agent is used to arrange and coordinate integration tasks. When the Oracle Data Integrator project is put into production, the Data administrator can use the Web-based Metadata Navigator application to generate reports based on the Metadata in the database. Ready-made knowledge modules can use platform-specific code and tools to extract and load data across heterogeneous platforms.

The Oracle Data Integrator information library contains a primary information library (including detailed information about users and roles), connections to databases and other data sources, project versions, and one or more work information libraries (including detailed information about data models and ing for integrated data ). These databases can be stored in Oracle and non-Oracle relational databases. They can be managed using graphical modules and accessed by proxies during runtime.

Four graphic modules are available to create and manage Oracle Data Integrator projects:

• Designer is used to define data storage (tables, files, Web services, etc.), interfaces (Data ing), and packages (including interface integration steps ).
• Topology Manager is used to create and manage connections to data sources and proxies. It is generally restricted to accessible only by administrators.
• Operator is used to view and manage product integration jobs.
• Security Manager is used to manage users and their information databases.

These Java-based applications can run in any Java environment including Microsoft Windows, Macintosh OS X, and Linux.

Declarative design: Generally, data integration tasks involve two main fields:

• Business Rules on which data to be converted and associated with others
• Technical details on the actual data extraction, loading, and other operations

 

This Division means that the person who defines the business rules is usually the technical business expert or Data Expert of the organization, while the technical details are often left for developers and DBA and other technical personnel to define. Using most data integration tools, it is usually difficult to divide responsibilities in this way, because their data ing features mix business rules and technical implementation details in the same data ing. Oracle Data Integrator uses a different method. Like SQL, it uses declarative methods to build Data ing, which is called an "interface" in tools ".

When creating a new interface, developers or technical business users first define the data to be integrated and the business rules to be used. In this step, tables are joined together, filters are applied, and SQL expressions are used to convert data. The specific SQL language used is determined by the database platform that executes the code.

Then, in another step, technicians can use database-specific tools and design methods (such as incremental loading, batch loading tools, gradient dimensions, and Change Data Capture) extract, combine, and integrate the data in the most effective way.

1 2 3 Next Page