Cross Reference Table Structures

Oracle SOA Suite Cross References 30-5

30.1.3.2 Integration and Cross-Referencing Phase IKM

During the integration phase, a Common ID is created for the target table. The value for the Common ID is computed from the expression in the XREF_SYS_GUID KM option. This expression can be for example: ■ A database sequence SEQUENCE_NAME. NEXTVAL ■ A function returning a global unique Id SYS_GUID for Oracle, NewID for SQL Server This Common ID can also be automatically pushed to the target columns of the target table that are marked with the UD1 flag. Both the Common ID and the Source Primary Key are pushed to the cross reference table. In addition, the IKM pushes to the cross reference table a unique Row Number value that creates the cross reference between the Source Primary Key and Common ID. This Row Number value is computed from the XREF_ROWNUMBER_EXPRESSION KM option, which takes typically expressions similar to the Common ID to generate a unique identifier. The same Common ID is reused and not re-computed if the same source row is used to load several target tables across several interfaces with the Cross-References KMs. This allows the creation of cross references between a unique source row and different targets rows.

30.1.3.3 UpdatingDeleting Processed Records LKM

This optional phase parameterized by the SRC_UPDATE_DELETE_ACTION KM option deletes or updates source records based on the successfully processed source records: ■ If SRC_UPDATE_DELETE_ACTION takes the DELETE value, the source records processed by the interface are deleted. ■ If SRC_UPDATE_DELETE_ACTION takes the UPDATE value, a source column of the source table will be updated with an expression for all the processed source records. The following KM options parameterize this behavior: – SRC_UPD_COL: Name of the source column to update – SRC_UPD_COL_EXPRESSION: Expression used to generate the value to update in the column It is possible to execute delete and update operations on a table different table from the source table. To do this, you must set the following KM options in the LKM: ■ SRC_PK_LOGICAL_SCHEMA: Oracle Data Integrator Logical schema containing the source table to impact. ■ SRC_PK_TABLE_NAME: Name of the source table to impact. ■ SRC_PK_TABLE_ALIAS: Table alias for this table.

30.2 Installation and Configuration

Make sure you have read the information in this section before you start using the SOA XREF Knowledge Modules: ■ System Requirements and Certifications ■ Technology Specific Requirements ■ Connectivity Requirements 30-6 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator

30.2.1 System Requirements and Certifications

Before performing any installation you should read the system requirements and certification documentation to ensure that your environment meets the minimum installation requirements for the products you are installing. The list of supported platforms and versions is available on Oracle Technical Network OTN: http:www.oracle.comtechnologyproductsoracle-data-integrator index.html .

30.2.2 Technology Specific Requirements

There are no technology requirements for using Oracle SOA Suite cross references in Oracle Data Integrator. The requirements for the Oracle Database and Microsoft SQl Server apply also to Oracle SOA Suite cross references. For more information, see: ■ Chapter 2, Oracle Database ■ Chapter 7, Microsoft SQL Server

30.2.3 Connectivity Requirements

There are no connectivity requirements for using Oracle SOA Suite cross references in Oracle Data Integrator. The requirements for the Oracle Database and Microsoft SQl Server apply also to Oracle SOA Suite cross references. For more information, see: ■ Chapter 2, Oracle Database ■ Chapter 7, Microsoft SQL Server

30.3 Working with XREF using the SOA Cross References KMs

This section consists of the following topics: ■ Defining the Topology ■ Setting up the Project ■ Designing an Interface with the Cross-References KMs

30.3.1 Defining the Topology

The steps to create the topology in Oracle Data Integrator, which are specific to projects using SOA XREF KMs, are the following: 1. Create the data servers, physical and logical schemas corresponding to the sources and targets. 2. Create a data server and a physical schema for the Oracle or Microsoft SQL Server technology as described in the following sections: ■ Section 2.3.1, Creating an Oracle Data Server and Section 2.3.2, Creating an Oracle Physical Schema ■ Section 7.3.1, Creating a Microsoft SQL Server Data Server and Section 7.3.2, Creating a Microsoft SQL Server Physical Schema This data server and this physical schema must point to the Oracle instance and schema or to the Microsoft SQL Server database containing the cross reference tables.