Initial Data Loads High Volume Transactions with Xref Table Intermittent High Volume Transactions

22-2 Developers Guide for Oracle Application Integration Architecture Foundation Pack ■ Section 22.1.4, Intermittent High Volume Transactions

22.1.1 Initial Data Loads

In this design pattern, shown in Figure 22–1 , the initial set of data of a particular object is loaded from the source database to the target database; for example, loading Customer Account information or loading Invoice information into a new application database from an existing source application database. In the process, Xref data may or may not get established depending on the integration requirement. The Oracle Data Integrator package that is developed for a specific integration cannot be reused for loading data into another participating application. Figure 22–1 Initial Data Loads

22.1.2 How to Perform the Oracle Data Integrator Data Load

To perform the Oracle Data Integrator Data load: 1. The source application ERP APP1 populates the interface table using its native technology. Some applications can choose other strategies such as views or base tables as opposed to interface tables.

2. A job scheduler invokes the source side Oracle Data Integrator package.

3. Oracle Data Integrator extracts the data from Source Interface table and populates

the Target Interface table. Note: The following sample steps describe how you perform the initial data load from ERP Application 1 to ERP Application 2 as shown in Figure 22–1 . Using Oracle Data Integrator for Bulk Processing 22-3 4. After populating the Target interface table, you can choose to have Oracle Data Integrator populate the Xref table with App 1 ID and generate common ID. This step is optional. 5. Oracle Data Integrator either deletes or updates the rows that were processed from the Source interface table to indicate that the rows are processed. 6. In the target application ERP APP2, the native application extracts data from the target interface table and populates the target database, thereby generating ERP Application 2 ID. 7. A job scheduler on the target application invokes the Oracle Data Integrator package to populate the Application 2 ID onto the Xref table matching on the Common ID. For more information about Oracle Data Integrator, see Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.

22.1.3 High Volume Transactions with Xref Table

Whenever a need exists for a high-volume data transfer, AIA recommends using the Oracle Data Integrator solution for data transfer between applications. Using this approach, the Oracle Data Integrator package transfers data from source to target system on a regular basis. For details about how to load data, see Section 22.1.2, How to Perform the Oracle Data Integrator Data Load . AIA recommends that the interface tables on the source side have a mechanism to indicate processed rows.

22.1.4 Intermittent High Volume Transactions

If you have a requirement that batch loading co-exists with regular online transactions, AIA recommends the approach illustrated in Figure 22–2 . 22-4 Developers Guide for Oracle Application Integration Architecture Foundation Pack Figure 22–2 Intermittent High-Volume Transactions In this scenario, two different flows send data from the source to the target application, one using the AIA Oracle Data Integrator approach, and the other using the standard AIA approach. Note that the responsibility for ensuring data integrity lies with the participating applications. AIA recommends that only new records should be loaded using the AIA Oracle Data Integrator architecture approach. For details about how to send data from source to target using AIA-Oracle Data Integrator architecture, see Section 22.1.2, How to Perform the Oracle Data Integrator Data Load . Create operations should be performed using the AIA Oracle Data Integrator approach while all other operations should be performed using AIA. In this design pattern, do not use the AIA Oracle Data Integrator approach as an alternate route to send data when Oracle Fusion Middleware is unavailable. Instead, messages should be queued using an appropriate message queuing technology such as JMSQ, and handled using the guaranteed message technology recommended by AIA. For more information about guaranteed messages, see Section 13.7, Guaranteed Message Delivery.

22.2 High-Volume Transactions with Xref Table