Running the Package Oracle Fusion Middleware Online Documentation Library

Working with Integration Interfaces 11-3 ■ Knowledge Modules IKM, LKM, CKM that will be selected in the flow must be imported into the project. See Chapter 9, Creating an Integration Project for more information. ■ Variables, Sequence and User Functions that will be used in the mapping, filter or join expressions must be created in the project. See Chapter 12, Working with Procedures, Variables, Sequences, and User Functions for more information.

11.2 Introduction to the Interface Editor

The interface Editor provides a single environment for designing integration interfaces. The interface Editor enables you to create and edit integration interfaces. Figure 11–1 Interface Editor The Interface Editor consists of the sections described in Table 11–1 : Table 11–1 Interface Editor Sections Section Location in Figure Description Designer Navigator Left side The Designer Navigator displays the tree views for projects, models, solutions, and other global components. Source Diagram Middle You drag the source datastores from the Models tree and Interfaces from the Projects tree into the Source Diagram. You can also define and edit joins and filters from this diagram. Source Diagram Toolbar Middle, above the Source Diagram. This toolbar contains the tools that can be used for the source diagram, as well as display options for the diagram. Dataset Tabs Middle, below the Source Diagram. Datasets are displayed as tabs in the Interface Editor. 11-4 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator

11.3 Creating an Interface

Creating an interface follows a standard process which can vary depending on the use case. The following step sequence is usually performed when creating an interface, and can be used as a guideline to design your first interfaces: 1. Create a New Interface 2. Define the Target Datastore 3. Define the Datasets 4. Define the Source Datastores and Lookups 5. Define the Mappings 6. Define the Interface Flow 7. Set up Flow Control and Post-Integration Control 8. Execute the Integration Interface Note that you can also use the Quick-Edit Editor to perform the steps 2 to 5. See Section 11.4, Using the Quick-Edit Editor for more information.

11.3.1 Create a New Interface

To create a new interface:

1. In Designer Navigator select the Interfaces node in the folder under the project

where you want to create the interface.

2. Right-click and select New Interface. The Interface Editor is displayed.

3. On the Definition tab fill in the interface Name.

Interface Editor tabs Middle, below the Dataset tabs The Interface Editor tabs are ordered according to the interface creation process. These tabs are: ■ Overview ■ Mapping ■ Quick-Edit ■ Flow ■ Controls ■ Scenarios ■ Execution Target Datastore Panel Upper right You drag the target datastore from the Models tree in the Designer Navigator into the Target Datastore panel. The target datastore, with the mapping for each column, is displayed in this panel. To edit the datastore in the Property Inspector, select the datastore’s title or a specific column. You can also create a temporary target for this interface from this panel. Property Inspector Bottom Displays properties for the selected object. If the Property Inspector does not display, select Property Inspector from the View menu. Table 11–1 Cont. Interface Editor Sections Section Location in Figure Description Working with Integration Interfaces 11-5

4. Select a Staging Area and an Optimization Context for your interface.

5. Go to the Mapping tab to proceed. The steps described in

Section 11.3.2, Define the Target Datastore to Section 11.3.5, Define the Mappings take place in the Mapping tab of the Interface Editor.

11.3.2 Define the Target Datastore

The target datastore is the element that will be loaded by the interface. This datastore may be permanent defined in a model or temporary created by the interface in the staging area.

11.3.2.1 Permanent Target Datastore

To insert the permanent target datastore in an interface:

1. In the Designer Navigator, expand the Models tree and expand the model or

sub-model containing the datastore to be inserted as the target. 2. Select this datastore, then drag it into the Target Datastore panel. The target datastore appears.

3. In the Property Inspector, select the Context for this datastore if you want to target

this datastore in a fixed context. By default, the datastore is targeted on the context into which the interface is executed. This is an optional step. 4. If you want to target a specific partition of this target datastore, select in the Property Inspector the partition or sub-partition defined for this datastore from the list. This is an optional step. Note: The staging area defaults to the target. It may be necessary to put it on a different logical schema if the target does not have the required transformation capabilities for the interface. This is the case for File, JMS, etc. logical schemas. After defining the target datastore for your interface, you will be able to set a specific location for the Staging Area from the Overview tab by clicking the Staging Area Different From Target option and selecting a logical schema that will be used as the staging area. If your interface has a temporary target datastore, then the Staging Area Different From Target option is grayed out. In this case, the staging area as well as the target are one single schema, into which the temporary target is created. You must select here this logical schema. Oracle Data Integrator includes a built-in lightweight database engine that can be used when no database engine is available as a staging area for example, when performing file to file transformations. To use this engine, select In_MemoryEngine as the staging area schema. This engine is suitable for processing small volumes of data only. The optimization context defines the physical organization of the datastores used for designing an optimizing the interface. This physical organization is used to group datastores into sourcesets, define the possible locations of transformations and ultimately compute the structure of the flow. For example, if in the optimization context, two datastores on two different logical schema are resolved as located in the same data server, the interface will allow a join between them to be set on the source.