Informatica Data Quality Client Architecture

Plan reads
from/writes to
Relational DB
and Flat Files

Data Quality C/C++ Platform

Data Quality Engine

Standalone Data Quality

Plan status
is returned
to user

Workbench- Java UI

Database connection libraries

Databases
Source/target
data

Staging

DQ
Repository
MySql
Oracle
SQLServer

On opening the plan, workbench reads the

xml from the DQ Repository through the
Database connection libraries.
The plan is executed using the DQ engine
through a set of API calls.

Client Server Architecture

Data Quality

Data Quality Client

Workbench- Java UI

Data Quality
Engine

Remote Data Quality Server

Plan status is
returned to user
execute
plan

Database
connection
libraries DQ plan

Database connection libraries

Databases
Staging

Local DQ
Repository

Data Quality Engine

Remote Server must

be able to access
Files and Dbases
required by the plan

Remote
API

(CORBA)

Remote DQ Staging
Repository

Dictionaries should
reside on the server
Dictionaries

On opening the plan, workbench reads the plan from the

local or remote DQ Repository through the Database
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.
3