In the Repository view, expand the Metadata node and the directory in which you saved
the source. Then drag this source into the design workspace.
The dialog box below appears.
Select tOracleInput and then click OK to close the dialog box.
The component is displayed in the workspace. The table used in this scenario
is called LOCATIONS.
Drag the following components from the Palette into the design workspace: two tMap components, tOracleOutput
Connect tMap with tUniservBTGeneric first.
Accept the schema from tUniservBTGeneric by
clicking Yes on the prompt window.
Connect the other components via the Row >
Double-click tUniservBTGeneric to open its
Basic Settings view.
Enter the connection data for the DQ Batch
Suite job. Note that the absolute path must be entered in the
field Job File Path.
Click Retrieve Schema to automatically create
a schema for tUniservBTGeneric from the input
and output definitions of the DQ Batch Suite
job and automatically fill in the fields in the Advanced
Check the details in the Advanced Settings
view. The definitions for input and output must be defined exactly the same as
the DQ Batch Suite job. If necessary, adapt
the path for the temporary files.
Double-click tMap_1 to open the schema
mapping window. On the left is the structure of the input source, on the right
is the schema of tUniservBTGeneric (and thus
the input for the DQ Batch Suite job). At the
bottom is the Schema Editor, where you can find
the attributes of the individual columns and edit them.
Assign the columns of the input source to the respective columns of tUniservBTGeneric. For this purpose, select a column
of the input source and drag it onto the appropriate column on the right
Click OK to close the dialog box.
Then define how to process the execution results of the job, including which
components will be used.
Before starting the Job, make sure that all path details are correct, the
server of the DQ Batch Suite is running and
that you are able to access the job.