Informatica Data Quality – Client Architecture

Data Quality – C/C++ Platform Standalone Data Quality

Plan reads
from/writes to
Relational DB
and Flat Files Data Quality Engine
Plan status Workbench- Java UI
is returned to
user

Database connection libraries

On opening the plan, workbench reads the
Databases xml from the DQ Repository through the
Database connection libraries.
Source/target Staging DQ
data Repository The plan is executed using the DQ engine
MySql through a set of API calls.
Oracle
SQLServer

1
 Client – Server Architecture
Data Quality Client Remote Data Quality Server
Data Quality Remote Server must
Workbench- Java UI be able to access
Plan status is
Data Quality returned to user Data Quality Engine Files and Dbases
required by the plan
Engine
Remote
execute API
plan (CORBA)

Database Remote DQ Staging

connection Repository Dictionaries should
libraries reside on the server
DQ plan
Database connection libraries Dictionaries

Databases
On opening the plan, workbench reads the plan from the
Staging Local DQ local or remote DQ Repository through the Database
Repository
connection libraries.
A call is made to the DQ engine through remote API to
execute the plan.

2
 IDQ – PowerCenter Integration
PowerCenter

Data Quality Client Repository

Integration Service
PowerCenter Mapping

PowerCenter Mapplet

The plan can be exported directly to the PowerCenter Repository as a mapplet.

Alternatively, the plan can be exported from IDQ and imported into PowerCenter.
The plan can be executed natively in PowerCenter as a mapplet in a mapping.
The Data Quality Components become Custom Transformations in PowerCenter.