Make sure that for every field imported you have one corresponding Attribute. Make sure that you have one Entity Row for every data row imported.

16-8 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator

16.2.6 Reverse-engineer the Entities

In order to provide the Quality process with input data and use its output data in data integrators integration processes, it is necessary to reverse-engineer these Entities. This operation is performed using a customized reverse-engineering method based on the Oracle Data Quality RKM. The RKM reads metadata from the .ddx files located in the ddl folder of your data quality project. To reverse-engineer the Entities of a data Quality project:

1. Import the RKM Oracle Data Quality into your Oracle Data Integrator project.

2. Insert a physical schema for the File technology in Topology Manager. Specifying

for both, the Directory Schema and the Directory Work Schema, the absolute path of your data folder. For example C:\oracle\oracledq\metabase_ data\metabase\oracledq\projectN\data This directory must be accessible to the agent that will be used to run the transformations. Oracle Data Integrator will look in the schema for the source and target data structures for the interfaces. The RKM will access the output data files and reverse-engineer them.

3. Create a File model and reverse the ddl folder.

1. In Designer Navigator expand the Models panel.

2. Right-click then select New Model.

3. Enter the following fields in the Definition tab:

Name : Name of the model used in the user interface. Technology : File Logical Schema : Select the Logical Schema on which your model will be based.

4. In the Reverse tab and select:

5. Set the RKM options as shown in Table 16–1 : Parameter ValueAction Reverse : Customized Context : Reverse-engineering Context Type of objects to reverse-engineer : Table KM Select the RKM Oracle Data Quality Working with Oracle Data Quality Products 16-9

4. Click Apply. The model is created, but contains no datastores yet.

5. Click Reverse. Now, the model contains datastores that you can see in the Models

view.

16.2.7 Use Oracle Data Quality Input and Output Files in Interfaces

You can now create in Oracle Data Integrator interfaces sourcing or targeting the data Quality input and output files. For example, you can: ■ Create interfaces to load the input file using datastores from various sources. ■ Create interfaces to re-integrate the output data back into the sources after cleansing.

16.2.8 Run this Quality Project from Oracle Data Integrator

The OdiDataQuality tool executes the batch file to run the Oracle Data Quality project. This tool takes as a parameter the path to the runprojectN script file. It can run either in synchronous the tool waits for the quality process to complete or asynchronous mode. For more information about the OdiDataQuality tool and its parameters, see Section A.5.3, OdiDataQuality .

16.2.9 Sequence the Process in a Package

Create a package in Oracle Data Integrator sequencing the following process: 1. One or more Interfaces creating the Quality input file, containing the data to cleanse. 2. OdiDataQuality tool step launching the Oracle Data Quality process. 3. One or more Interfaces loading the data from the Oracle Data Quality output files into the target datastores. Table 16–1 KM Options for RKM Oracle Data Quality Parameter Default Value Description DDX_FILE_NAME .ddx Mask for DDX Files to process. If you have used a naming convention in the Quality project for the Entities that you want to use, enter a mask that will return only these Entities. For example, specify the ODI_csv.ddx mask if you have used the ODI_IN_XX and ODI_OUT_XX naming convention for your input and output entities. USE_FRIENDLY_NAMES No Set this option to Yes if you want the Reverse-Engineering process to generate user-friendly names for datastore columns based on the field name specified in the DDX file. USE_LOG Yes Set to Yes if you want the reverse-engineering process activity be logged in a log file. LOG_FILE_NAME tempreverse.log Name of the log file.