In the Diagram Property tab of the Property Inspector, modify the

Working with Integration Interfaces 11-15 To change the LKM in use: 1. In the Flow tab, select one of the Source Sets or the Staging Area, if it is not into the Target group, by clicking its title. The Property Inspector opens for this object.

2. If you are working on a Source Set, change the Name of this source set. This step is

optional and improves readability of the flow.

3. Select a LKM from the LKM Selector list.

4. KMs are set with default options that work in most use cases. You can optionally modify the KM Options. Note that KM options of the previous KM are retained using homonymy when switching from a KM to another. By changing KMs several times you might lose custom KM option values. To change the IKM in use: 1. In the Flow tab, select the Target by clicking its title. The Property Inspector opens for this object.

2. In the Property Inspector, select a IKM from the IKM Selector list.

3. Check the Distinct option if you want to automatically apply a DISTINCT

statement on your data flow and avoid possible duplicate rows. 4. KMs are set with default options that work in most use cases. You can optionally modify the KM Options. Note that KM options of the previous KM are retained using homonymy when switching from a KM to another. By changing KMs several times you might lose custom KM option values. An important option to set is FLOW_CONTROL. This option triggers flow control and requires that you set up flow control.

11.3.7 Set up Flow Control and Post-Integration Control

In an integration interface, it is possible to set two points of control. Flow Control checks the data in the incoming flow before it gets integrated into the target, and Post-Integration Control checks the target datastore as if in a static check at the end of the interface. Note: Only KMs that have already been imported in the project can be selected in the interface. Make sure that you have imported the appropriate KMs in the project before proceeding. Note: Knowledge modules with an Incremental Update strategy, as well as flow control, require that you set an update key for the target datastore of the interface. Note: For more information on the KMs and their options, refer to the KM description and to the Oracle Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator. 11-16 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator

11.3.7.1 Set up Flow Control

The flow control strategy defines how data is checked against the constraints defined on the target datastore before being integrated into this datastore. It is defined by a CKM. In order to have the flow control running, you must set the FLOW_CONTROL option in the IKM to true. Flow control also requires that an update key is selected on the target datastore of this interface. Refer to Section 11.3.2.3, Define the Update Key for more information. To define the CKM used in an interface:

1. In the Controls tab of the interface, select a CKM from the CKM Selector list.

2. Set the KM Options.

3. Select the Constraints to be checked.

4. Fill in the Maximum number of errors allowed. Note that if you leave this field

empty, an infinite numbers of errors is allowed. The interface stops during the flow control if any or the post-integration control if any if the number of errors allowed is reached.

5. Check the box if you want the interface to fail when a percentage of errors is

reached during flow or post-integration control, rather than a fixed number of errors. This percentage is calculated with the following formula: errors_detected 100 checked_rows where: ■ checked_rows is the number of checked rows during flow and post-integration control. ■ errors_detected are the number of errors detected during flow and post-integration control. This formula is calculated at the end of the execution of the interface. If the result of this formula is superior to the indicated percentage, the interface status will be in error. If the interface falls into error during a flow control, no changes are performed into the target. If the interface falls into error after a post-integration control, the changes performed to the target are not committed by the Knowledge Module.

11.3.7.2 Set up Post-Integration Control

The post-integration control strategy defines how data is checked against the constraints defined on the target datastore. This check takes place once the data is integrated into the target datastore. It is defined by a CKM. In order to have the post-integration control running, you must set the STATIC_CONTROL option in the IKM to true. Post-integration control requires that a primary key is defined in the data model for the target datastore of your interface. Concerning the maximum number of errors allowed the same behavior is applied as for flow control. Post-integration control uses the same CKM as the flow control.

11.3.8 Execute the Integration Interface

Once the interface is created, it is possible to execute it. To run an interface:

1. While editing the interface, click Execute in the toolbar.