Data Validation Option Best Practices

Back Next

Detailed Architecture

The overall Data Validation Option architecture consists of a client, a repository, and a server. The client and repository are specific to Data Validation Option. The server (where test execution occurs) is PowerCenter.

The following image shows the three major elements: This image shows Data Validation Option, PowerCenter, and Enterprise Data, and the elements that they are made up of

This image shows Data Validation Option, PowerCenter, and Enterprise Data, and the elements that they are made up of

Data Validation Option: Data Validation Option consists of a desktop client, its own combined metadata repository, and a results warehouse. All test definitions and test results are stored in this warehouse. The warehouse has predefined database views against which all reporting occurs.

The following image shows how these elements are used when Data Validation Option tests data:

This image depeicts the elements involved in, and the flow of data testing, in Data Validation Option

Data Validation Option users define tests in the desktop clients and store those (metadata) definitions in the Data Validation Option repository.

Tests are then executed from a GUI or command line. Data Validation Option generates PowerCenter mappings that embody the test conditions runs those mappings in PowerCenter.

PowerCenter accesses the data being tested and applies the tests to that data.

Test results (like pass or fail, test details, error rows, and data values) are stored in the Data Validation Option warehouse.

Users can view test results in reports that are generated from views on the warehouse.

Based on this setup, there is a clear relationship between the Data Validation Option environment (clients, warehouse, repository) and the PowerCenter environment (PowerCenter repository and PowerCenter Integration Service).

The Data Validation Option repository stores metadata needed for testing. This includes both table metadata and connection information so users can define tests, as well as the user-defined test definitions themselves. The table and connection information is imported into the Data Validation Option repository from associated PowerCenter repositories.

During initial configuration, at least one PowerCenter repository must be associated with a Data Validation Option repository. There can be a many-to-one relationship between PowerCenter repositories and a Data Validation Option repository.

This means that one Data Validation Option repository can import metadata from more than one PowerCenter repository, but there are issues to consider.

Rename Saved Search

Table of Contents

Data Validation Option Best Practices

Data Validation Option Best Practices

Detailed Architecture

Detailed Architecture