Implementing Data Masking and Data Subset with IMS Unload File Sources

Back Next

Step 5. Import PowerExchange Source Metadata into PowerCenter

When you import PowerExchange data maps into PowerCenter to create source definitions, the source definitions become available for import into Test Data Manager.

After you connect to a source database from PowerCenter, you can import source metadata into the PowerCenter repository. You must create a folder in the PowerCenter repository to store source definitions and metadata that you import into the PowerCenter repository. When you import metadata from PowerCenter into the TDM repository, Test Data Manager creates a copy of the PowerCenter folder in the TDM repository.

You do not need to import PowerExchange target metadata into PowerCenter. When you generate a workflow from the TDM Workbench, the required target definitions are generated automatically.

In the PowerCenter Designer, connect to a PowerCenter repository.

Create a folder for the source that you are importing.

Click Sources > Import from PowerExchange
.

The

Import from PowerExchange

dialog box appears. The following figure shows this dialog box:

Enter the following information in the dialog box:

Attribute	Required/ Optional	Description
Location	Required	Name of the PowerExchange Listener (node name from PowerExchange DBMOVER member) on the system on which the database resides.
User Name	Required	User name for the database to connect to.
Password	Required	Password associated with the user name.
Multi-Record Datamaps	Required	Lists multiple-record data maps. When you use data masking or data subset with IMS unload file sources, you must select this option.
Use Sequence Fields	Required	Specifies whether to generate sequence fields. When you use data masking or data subset with IMS unload file sources, you must select this option.
Source Type	Required	Data source type. Select IMS .
CDC Datamaps	n/a	Displays CDC extraction maps only. Clear this check box.
Network Timeout	Optional	Number of seconds that elapse during a network send or receive operation before PowerExchange ends the connection and issues a timeout error message.
Schema	Optional	Schema name to use to filter the resulting data maps. You can enter name patterns by using the following wildcard characters: * (asterisk). Represents one or more characters. ? (question mark). Represents one character.
Map name	Optional	Data map name to use to filter the resulting data maps. You can enter name patterns by using the following wildcard characters: * (asterisk). Represents one or more characters. ? (question mark). Represents one character.
Respect Case	Optional	If this attribute is selected, PowerExchange filters data maps by using the exact case of the Schema and Map name fields. Otherwise, PowerExchange ignores the case when searching for data maps.
Selected Datamaps	n/a	Lists the available data maps for the connection, source type, and filter details that you entered.

Click Connect
.

The available schemas appear in the

Selected Datamaps

list.

Expand the schema to display all the tables for all the data maps in the schema, and select the tables that you want to import. You can import multiple tables from a single data map or from multiple data maps.

Click OK
.

The PowerCenter source definitions are listed and have names in the format mapname_tablename.

The following example shows the source definition for the COURSE-STUDENT hierarchy:

When you select

Multi-Record Datamaps

, the source definition includes multiple groups. When you select

Use Sequence Fields

, the source definition includes generated primary key and foreign key fields.

Optionally, to view the XML that describes the hierarchy structure, double-click the source definition. On the

Metadata Extensions

tab of the

Edit Tables

dialog box, click the arrow in the

Value

column for

Hierarchy Structure

The Hierarchy Structure dialog box appears. The following image shows an example hierarchy structure:

When you generate a workflow, the Hierarchy Structure metadata extension provides the metadata to maintain the relationships between the segments in the source data as it passes through PowerCenter transformations.

For more information about importing PowerExchange source definitions into PowerCenter, see

Rename Saved Search

Table of Contents

Implementing Data Masking and Data Subset with IMS Unload File Sources

Implementing Data Masking and Data Subset with IMS Unload File Sources

Step 5. Import PowerExchange Source Metadata into PowerCenter

Step 5. Import PowerExchange Source Metadata into PowerCenter