You are here: Processor Library > Product Data > Product Data Processor

Process Product Data

The Process Product Data processor connects to an instance of Oracle Enterprise Data Quality for Product Data (OEDQ-P) version 5.6.2 and uses a production Data Service Application (DSA) to process product data using semantic rules; for example, to enhance and add structure to unstructured product data.

Note: The processor will only appear if the OEDQ server is configured to connect to an OEDQ-P instance using an edqp.properties file. This file must be created in [Install Path]/config/edqp with the following settings:

server = [name or IP address of the OEDQ-P server]

port = [the http port of OEDQ-P server. This will be 2229 in a default installation]

batchsize = [number of records to submit to OEDQ-P at a time – defaults to 1000]

A batchsize greater than 1000 may cause an Out of Memory error.

Use

The Process Product Data processor allows OEDQ-P to be used within an OEDQ process to parse and match product data with a DSA.

Configuration

Note: This processor always appears with a re-run marker, indicating that it will be completely re-executed each time the process is run, regardless of whether or not its configuration has changed. This will also mean that processors that are downstream of the processor will need to be rerun. This is because there may be changes made outside of the OEDQ application that could lead to different results on subsequent executions.

Inputs

The inputs to the processor should correspond to the expected inputs of the selected DSA.

Note: The ID of the record as understood by OEDQ-P should always be the first input attribute to the processor. This is used to correlate the records returned from the DSA with the input records.

Options

DSA Name (selection): The name of a deployed (in production) DSA on the configured server.
Output Name (selection): The name of an output step in the selected DSA. This is used to drive the output attributes from the processor. The processor will return the record set and attributes as configured in the selected DSA and Output step.

Note: If you need to use the data from multiple output steps in your process, this should be done using multiple instances of the Process Product Data processor.

Outputs

The output attributes from the processor are determined by the selected DSA and Output step in the Options tab. The set of attributes will correspond to the configuration of the output step of the DSA in OEDQ-P.

Flags

edqp.success (Y/N)

Y - The record was returned by the OEDQ-P DSA.
N - The record was not returned by the OEDQ-P DSA.

Execution

All modes are supported.

Note: The processor is suitable for record-by-record processing through EDQ-P; for example, for parsing product descriptions using a DSA. For EDQ-P operations that need to work across a record set, such as matching, Oracle recommends calling an EDQ-P job using an EDQ External Task, and sharing data using either files or a staged data area in a database. As EDQ is by its nature multi-threaded, the processor assumes that the DSA it uses can scale horizontally by calling multiple instances of an EDQ-P job (one per thread).

Results Browsing

The Process Product Data processor presents no summary statistics on its processing..

In the Data view, each input attribute is shown with the output attributes to the right.

Output Filters

Returned – records that were returned from the selected DSA and output step.
Not Returned – records that were input to, but not returned from, the selected DSA and output step.

Example

In this example, an OEDQ-P DSA is used to parse, enhance and translate unstructured product descriptions relating to Electrical Resistors.

Example of the results from the Process Product Data processor