Configure and Start Oracle GoldenGate Processes

30 Oracle SOA Suite Cross References 30-1 30 Oracle SOA Suite Cross References This chapter describes how to work with Oracle SOA Suite cross references in Oracle Data Integrator. This chapter includes the following sections: ■ Section 30.1, Introduction ■ Section 30.2, Installation and Configuration ■ Section 30.3, Working with XREF using the SOA Cross References KMs ■ Section 30.4, Knowledge Module Options Reference

30.1 Introduction

Oracle Data Integrator features are designed to work best with Oracle SOA Suite cross references, including integration interfaces that load a target table from several source tables and handle cross references.

30.1.1 Concepts

Cross-referencing is the Oracle Fusion Middleware Function, available through the Oracle BPEL Process Manager and Oracle Mediator, previously Enterprise Service Bus ESB, and leveraged typically by any loosely coupled integration built on the Service Oriented Architecture. It is used to manage the runtime correlation between the various participating applications of the integration.

30.1.1.1 General Principles

The cross-referencing feature of Oracle SOA Suite enables you to associate identifiers for equivalent entities created in different applications. For example, you can use cross references to associate a customer entity created in one application with native id Cust_100 with an entity for the same customer in another application with native id CT_001. Cross-referencing XREF facilitates mapping of native keys for entities across applications. For example, correlate the same order across different ERP systems. The implementation of cross-referencing uses a database schema to store a cross reference information to reference records across systems and data stores. For more information about cross references, see Working with Cross References in the Oracle Fusion Middleware Developers Guide for Oracle SOA Suite. The optional ability to update or delete source table data after the data is loaded into the target table is also a need in integration. This requires that the bulk integration