Creating and Editing Constraints and Filters

6-6 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator

6.4 Generating Interface INOUT

For a given model or datastore assembled using Common Format Designer, Oracle Data Integrator is able to generate: ■ Interfaces IN : These integration interfaces are used to load the models datastores assembled from other datastorescolumns. They are the integration process merging data from the original datastores into the composite datastores. ■ Interfaces OUT : These integration interfaces are used to extract data from the models datastores. They are generated using the interfaces including the interfaces IN already loading the models datastore. They reverse the integration process to propagate the data from the composite datastore to the original datastores. For example, an Active Integration Hub AIH assembles information coming from several other applications. It is made up of composite datastores built from several data models, assembled in a diagram. The AIH is loaded using the Interfaces IN, and is able to send the data it contains to the original systems using the Interfaces OUT. To generate the Interfaces IN:

1. In the Models tree of Designer Navigator, select the data model or datastore for

which you want to generate the interfaces.

2. Right-click, then select Generate Interfaces IN. Oracle Data Integrator looks for

the original datastores and columns used to build the current model or datastore. The Generate Interfaces IN Editor appears with a list of datastores for which Interfaces IN may be generated.

3. Select an Optimization Context for your interfaces. This context will define how

the flow for the generated interfaces will look like, and will condition the automated selection of KMs. 4. Click the ... button to select the Generation Folder into which the interfaces will be generated.

5. In the Candidate Datastores table, check the Generate Interface option for the

datastores to load.

6. Edit the content of the Interface Name column to rename the integration

interfaces.

7. Click OK. Interface generation starts.

The generated interfaces appear in the specified folder. To generate the Interface OUT: Note: Interfaces automatically generated are built using predefined rules based on repository metadata. These interfaces can not be executed immediately. They must be carefully reviewed and modified before execution Note: If no candidate datastore is found when generating the interfaces IN, then it is likely that the datastores you are trying to load are not built from other datastores or columns. Automatic interface generation does not work to load datastores and columns that are not created from other models datastores and columns. Working with Common Format Designer 6-7

1. In the Models tree of Designer Navigator, select the data model or datastore for

which you want to generate the interfaces.

2. Right-click, then select Generate Interfaces OUT. Oracle Data Integrator looks for

the existing Interfaces loading these the datastores. The Generate Interfaces OUT Editor appears with a list of datastores for which Interfaces OUT may be generated.

3. Select an Optimization Context for your interfaces. This context will define how

the flow for the generated interfaces will look like, and will condition the automated selection of KMs. 4. Click the ... button to select the Generation Folder into which the interfaces will be generated.

5. In the Candidate Datastores, check the Generation and Generate Interface

checkboxes to select either all or some of the candidate datastore to load from the target datastore of the existing interfaces.

6. Edit the content of the Interface Name column to rename the integration

interfaces.

7. Click OK. Interface generation starts.

The generated interfaces appear in the specified folder. Note: Interfaces automatically generated are built using the available metadata and do not always render the expected rules. These interfaces must be carefully reviewed and modified before execution. Note: If no candidate datastore is found when generating the interfaces OUT, then it is likely that no interface loads the datastores you have selected to generate the interfaces OUT. The interfaces OUT from a datastore are generated from the interfaces loading this datastore. Without any valid interface loading a datastore, not propagation interface from this datastore can be generated.