Scribd
Upload
1K views

DQ Architecture

The document describes different architectures for Informatica Data Quality: - Standalone architecture reads plans from a local repository and executes them using a local Data Quality engine. - Client-server architecture reads plans from a remote repository and executes them using a remote Data Quality engine through a remote API. - PowerCenter integration exports plans to the PowerCenter repository as mapplets to execute natively in PowerCenter mappings, with Data Quality components appearing as custom transformations.

Uploaded by

Shiva CH
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
1K views

DQ Architecture

The document describes different architectures for Informatica Data Quality: - Standalone architecture reads plans from a local repository and executes them using a local Data Quality engine. - Client-server architecture reads plans from a remote repository and executes them using a remote Data Quality engine through a remote API. - PowerCenter integration exports plans to the PowerCenter repository as mapplets to execute natively in PowerCenter mappings, with Data Quality components appearing as custom transformations.

Uploaded by

Shiva CH
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 3

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

You might also like