Abstract
Supported Versions
Data Validation Option Best Practices
General Architecture
Data Validation Option and PowerCenter Configuration
- Setting Up Data Validation Option and PowerCenter Configuration
Architecture Configuration
- PowerCenter Repository Setup
Data Validation Option Client
- Data Validation Client Overview
Naming Conventions
- Suggested Naming Conventions
User Management
Performance
- Data Validation Option Performance in PowerCenter Environment
- Performance Testing
  - Methodology and Metrics Calculations

Data Validation Option Best Practices

Back Next

Native Security

In native security, the user name (along with other preference settings) for a given Data Validation Client is stored in the

preferences.xml

file for that client.

There is no password required for native users. When the Data Validation Client starts, it reads this file and sets the preferences accordingly in the Data Validation Client.

This information can be seen in the .

File

Settings

Preferences

For example, see the following image:

This model is used by many Data Validation Option customers because it is simple and works. But if a company has security concerns or requirements, then this model, particularly with users and no passwords, falls short.

Rename Saved Search

Table of Contents

Data Validation Option Best Practices

Data Validation Option Best Practices

Native Security

Native Security