Implementing Data Masking and Data Subset with Sequential or VSAM Sources

Transcription

1 Implementing Data Masking and Data Subset with Sequential or VSAM Sources 2013 Informatica Corporation. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation.

2 Abstract You can use PowerExchange, PowerCenter, and Persistent Data Masking and Data Subset (TDM) to perform data masking and data subset with sequential or VSAM sources on z/os. This article describes the procedures for installing and configuring PowerExchange and performing data masking and data subset with these sources. Supported Versions PowerCenter PowerExchange Persistent Data Masking and Data Subset Table of Contents Overview Implementation Scenario Task Flow Step 1. Install and Configure PowerExchange on z/os Install PowerExchange on z/os Edit the DBMOVER Configuration Member on the z/os System Configure the PowerExchange Listener JCL on z/os Start the PowerExchange Listener Step 2. Install and Configure PowerExchange on the PowerCenter Services Machine Install PowerExchange on the PowerCenter Services Machine Edit the DBMOVER Configuration File on the PowerCenter Services Machine Step 3. Install and Configure PowerExchange on the PowerCenter Client Machine Install PowerExchange on the PowerCenter Client Machine Edit the DBMOVER Configuration File on the PowerCenter Client Machine Step 4. Define PowerExchange Data Maps for z/os Sources and Targets Step 5. Import PowerExchange Source Definitions into PowerCenter Step 6. Define PowerExchange NRDB Application Connections in PowerCenter Step 7. Log In to the ILM Workbench Step 8. Create an Application Step 9. Define Data Masking Rules and Policies Create a Rule Create a Policy Step 10. Assign Rules in Policies to Columns Step 11. Define Data Subset Components Create a Group Step 12. Create a Plan Step 13. Generate a Workflow Step 14. Edit the Session Properties

3 Step 15. Start the Workflow Step 16. Monitor the Workflow Overview To use data masking or data subset with sequential or VSAM sources, define PowerExchange data maps for the sources. Then import the source definitions into PowerCenter and define application connections. You can then include the sources in an application, create a plan for data masking and data subset, and generate and run a workflow to implement the plan. Data subset reduces size requirements for your enterprise application testing environment to facilitate testing and development. Use data subset to create small, targeted, and referentially intact copies of production data for nonproduction use. Use data masking to change sensitive production data to realistic test data for non-production environments. The ILM Server modifies source data based on masking rules that you configure for each column. Create masked data for software development, testing, training, and data mining. Implementation Scenario You are designing a data masking and data subset application that uses PowerExchange to access sequential or VSAM sources on z/os. In this scenario, you have already installed and configured PowerCenter and TDM on the appropriate machines. The implementation includes the following components: A z/os machine with sequential or VSAM data sources. On this machine, you will install PowerExchange Linux, UNIX, or Windows machine with an Informatica Domain and the PowerCenter Integration Service installed. On this machine, you will install PowerExchange Windows machine with PowerCenter Client installed. On this machine, you will install PowerExchange 9.5.0, including the PowerExchange Navigator. You will run the PowerExchange Navigator on this system to create data maps. You will run PowerCenter Client to define PowerExchange connections and data sources and edit workflow session properties. Windows or UNIX machine with the PowerCenter repository and TDM Server 5.3 installed. Web browser host from which you log in to the TDM Workbench. Note: You can install PowerCenter on an LPAR running zlinux and use HiperSockets for communications between PowerCenter on one LPAR and the PowerExchange Listener on the LPAR that contains the data source. In this configuration, you must install PowerExchange both on the LPAR with PowerCenter and on the LPAR with the PowerExchange Listener. Task Flow To use TDM data masking and data subset with sequential or VSAM sources, complete the following steps: 1. Install and configure PowerExchange on z/os. 2. Install and configure PowerExchange on the PowerCenter services machine. 3. Install and configure PowerExchange on the PowerCenter Client machine. 4. Define data maps for sequential or VSAM sources and targets on z/os. 5. Import PowerExchange source definitions into PowerCenter. 3

4 6. Define PowerExchange source and target application connections in PowerCenter. 7. Log in to the ILM Workbench. 8. Create an application, and add sequential or VSAM sources to it. 9. Define data masking rules and policies. 10. Assign data masking rules and policies to columns in the source. 11. Define data subset components. 12. Create a plan. 13. Generate a workflow. 14. Edit the session properties. 15. Run the workflow. 16. Monitor the workflow. Step 1. Install and Configure PowerExchange on z/os To install PowerExchange on z/os, run the MVS Installation Assistant. After you install PowerExchange, edit the DBMOVER configuration file, configure the PowerExchange Listener JCL, and start the PowerExchange Listener. Install PowerExchange on z/os To install PowerExchange on z/os, run the MVS Installation Assistant. For detailed instructions, see the PowerExchange Installation Guide. This guide also gives details about how access to the z/os databases and files is controlled. Edit the DBMOVER Configuration Member on the z/os System Edit the DBMOVER configuration member. Verify that the member includes a LISTENER statement. The LISTENER statement defines the TCP/IP port on which a named PowerExchange Listener process listens for work requests. The default DBMOVER member includes the required LISTENER statement. For more information about the DBMOVER configuration member, see the PowerExchange Reference Manual. Configure the PowerExchange Listener JCL on z/os Configure the PowerExchange Listener JCL before starting the PowerExchange Listener the first time. PowerExchange provides PowerExchange Listener JCL in the following members of the RUNLIB library: PWXLSTNR runs PowerExchange as a started task. STARTLST runs PowerExchange as a batch job. Note: When you ran the XIZZZ998 job during installation, the PWXLSTNR member was copied to the PROCLIB library. 1. Verify that the STEPLIB DD concatenation in the PowerExchange Listener JCL includes the load libraries for your source DBMSs. Usually, the PowerExchange LOADLIB library occurs before the data-source load libraries in the concatenation. The STEPLIB concatenation in the STARTLST member includes the load libraries for all data sources in a proper order. 2. Verify that the PARM statement specifies the node name that is defined in the LISTENER statement of the DBMOVER configuration file. 4

5 3. In the REGION parameter of the EXEC statement, enter a region size. The region size indicates the amount of storage to allocate for running the PowerExchange Listener. The sample JCL specifies a region size of 384 MB in the EXEC statement. Informatica recommends a region size of 0M, which indicates that z/os gives the job all the storage available below and above 16 megabytes. For important considerations about specifying a region size of 0M, see the z/os MVS JCL Reference. If you omit the REGION parameter, the system default applies. 4. Verify that the TIME parameter in the EXEC statement is set to NOLIMIT. The NOLIMIT setting enables the PowerExchange Listener job to run without a time limit and prevents timeout-related abends that might occur with abend code S If the SECURITY statement in the DBMOVER configuration file is set to 1 or 2, APF-authorize the PowerExchange LOADLIB library and any other load libraries in the STEPLIB DD concatenation of the PowerExchange Listener JCL. For more information, see the PowerExchange Bulk Data Movement Guide. Start the PowerExchange Listener To start the PowerExchange Listener, issue the MVS START command with the name of the started task. For example, issue the following command: START PWXLSTNR You can also run the PowerExchange Listener as a batch job. However, because it is a long-running task, using an MVS started task is more appropriate. Step 2. Install and Configure PowerExchange on the PowerCenter Services Machine Install and configure PowerExchange on the machine where the PowerCenter Integration Service runs. In the scenario described in this article, all PowerCenter services, including the PowerCenter Integration Service, reside on the same machine. Install PowerExchange on the PowerCenter Services Machine Install PowerExchange on the PowerCenter services machine. Use the PowerExchange installation instructions for the operating system type and bit-level. If PowerCenter services run on a 64-bit machine, use the PowerExchange 64-bit installation executable or tar file. If PowerCenter services run on a 32-bit machine, use the PowerExchange 32-bit executable or tar file. For detailed installation instructions, see the PowerExchange Installation Guide. Edit the DBMOVER Configuration File on the PowerCenter Services Machine Edit the DBMOVER configuration file on the PowerCenter services machine. Include a NODE statement to define the TCP/IP host name and port that PowerExchange uses to contact the PowerExchange Listener on the z/os system. Use the following format: NODE=({node_name node1},tcpip,host_name,{port 2480} [,{send_bufsize 65536}] [,{receive_bufsize 65536}] 5

6 ) [,{send_size 4096}] [,{receive_size 4096}] [,receive_timeout] [,{SSL ZOSSSL}] [,service_name] For more information, see the PowerExchange Reference Manual. Step 3. Install and Configure PowerExchange on the PowerCenter Client Machine Install and configure PowerExchange on the machine where you installed PowerCenter Client. You will run the PowerEchange Navigator on this machine. Install PowerExchange on the PowerCenter Client Machine Install PowerExchange on the machine where PowerCenter Client is installed. Run the PowerExchange 32-bit executable file to install PowerExchange. You must use the Windows 32-bit executable to install the PowerExchange Navigator, even on a Windows 64-bit machine. For detailed installation instructions, see the PowerExchange Installation Guide. Edit the DBMOVER Configuration File on the PowerCenter Client Machine Edit the DBMOVER configuration file on the PowerCenter Client machine. Include a NODE statement to define the TCP/IP host name and port that PowerExchange uses to contact the PowerExchange Listener on the z/os system. Use the following format: NODE=({node_name node1},tcpip,host_name,{port 2480} [,{send_bufsize 65536}] [,{receive_bufsize 65536}] [,{send_size 4096}] [,{receive_size 4096}] [,receive_timeout] [,{SSL ZOSSSL}] [,service_name] ) For more information, see the PowerExchange Reference Manual. Step 4. Define PowerExchange Data Maps for z/os Sources and Targets Create a PowerExchange data map for each sequential or VSAM source. Make each data map available to the source and corresponding target. If a target is on the same z/os system as the source, you can use the same data map for the source and target. Otherwise, send the data map to both the source and target systems. 1. On the Resources tab in the Resource Explorer, click Add > Data Map. 2. In the Name dialog box, enter the following information: Option Schema Name Description Enter a user-defined schema name. 6

7 Option Description PowerExchange uses this name as the first part of the data map name, as follows: schema_name.data_map_name The name must consist of alphanumeric characters and begin with a letter. Maximum length is 10 characters. Data Map Name Access Method Import Record Definitions Enter a user-defined map name. PowerExchange uses this name as the second part of the data map name, as follows: schema_name.data_map_name The name must consist of alphanumeric characters and begin with a letter. Maximum length is 10 characters. Select one of the following access methods: - ESDS. VSAM entry sequenced data set (ESDS) on z/os. - KSDS. VSAM key sequenced data set (KSDS) on z/os. - RRDS. VSAM relative record data set (RRDS) on z/os. - SEQ. Sequential data set on z/os. Select this option to import a copybook into the data map. Clear this option to add only the data map. By default, this option is selected. 3. Enter any additional information that is required for the access method that you selected. 4. If you selected the Import Records Definitions option, click Next. If you cleared this option, click Finish. 5. If you selected the Import Records Definitions option, provide the required information in the dialog boxes. 6. For each data map, click File > Send to Remote Node, and complete the Data Map Remote Node dialog box to send the data map to the PowerExchange Listener on the source system. In addition, if different Listeners will write to the source and target, send each data map to the Listener on the target system as well. For more information about creating data maps, see the PowerExchange Navigator User Guide. Step 5. Import PowerExchange Source Definitions into PowerCenter When you import source definitions into PowerCenter, they become available for import into the ILM Workbench. When you connect to a source database from PowerCenter, you import source metadata into the PowerCenter repository. You must create a folder in PowerCenter to store source definitions and metadata that you import into the PowerCenter repository. When you import metadata from PowerCenter into the ILM repository, the ILM Workbench creates a copy of the PowerCenter folder in the ILM repository. You do not need to import PowerExchange target definitions into PowerCenter. When you generate a workflow from the ILM Workbench, TDM generates the required target definitions. Note: TDM 9.3 does not support importing multiple records at a time from data sources with multi-record data maps. You can include only one record and table per source definition. 1. In the PowerCenter Designer, connect to a PowerCenter repository. 2. Create a folder for the source that you are importing. 7

8 3. Click Sources > Import from PowerExchange. 4. Enter the following information in the dialog box: Attribute Required/ Optional Description Location Required Name of the PowerExchange Listener (node name from PowerExchange dbmover.cfg) 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 Optional Clear this option. You can import only a single record and table per source definition for data subset and masking operations. Source Type Required Select SEQ or VSAM. CDC Datamaps n/a Clear this check box for TDM sources. 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 Enter a schema name to filter the resulting data maps. Map name Optional Enter a data map name to filter the resulting data maps. 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. 5. Optionally, enter a filter to view particular schemas and tables from the database. You can also enter a filter condition to display schemas and tables that meet the filter condition. To use a filter condition, enter a schema name in Schema, a table name in Map name, or enter both values. You can use the following wildcard characters in the filter condition: * (asterisk). Represents one or more characters.? (question mark). Represents one character. Use the following syntax when entering a wildcard character: Enter the filter condition as a prefix. For example, enter A* to display schemas and tables that begin with an A. Enter the filter condition as a suffix. For example, enter *A to display schemas and tables that end with an A. Enter the filter condition as a substring. For example, enter *cust* to display schemas that contain cust. 6. Click Connect. The available schemas appear in the Selected Datamaps list. 7. 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. 8

9 8. Click OK. The source definitions appear. The PowerCenter source is named mapname_tablename. Step 6. Define PowerExchange NRDB Application Connections in PowerCenter In the PowerCenter Workflow Manager, if the source and target are on the same system, configure a single connection. If the source and target are on different systems, configure separate connections for the source and target. When you generate a workflow, you can select the source and target connections that you configured in the PowerCenter Workflow Manager. 1. In the Workflow Manager, connect to a PowerCenter repository. 2. To configure a PowerExchange application connection, click Connections > Application. The Application Connection Browser dialog box appears. In the Select Type field, select PWX NRDB Batch. 3. Click New. The Connection Object Definition dialog box appears. 4. Enter the values for the connection attributes. The following table describes the connection attributes for PWX NRDB Batch application connections: Connection Attribute Required Description Name Yes Name of the application connection. Code Page Yes The code page for the PowerCenter Integration Service to use to extract data from the source database. Note: In Unicode mode, PWXPC sets the code page with this value overriding any code page specification in the PowerExchange configuration file. Location Yes Location of the source or target database as specified as a node in the PowerExchange configuration file dbmover.cfg. User Name Yes Database user name. Password Yes Password for the user name. Compression No Controls whether to compress source data during the session. Encryption Type No The encryption type. Encryption Level No The encryption level. Pacing Size No The pacing size. Interpret as Rows No Controls whether the pacing size is expressed in kilobytes or number of rows. Offload Processing No Controls whether to use offload processing. Offload processes transfers PowerExchange bulk data processing from the source system to the PowerCenter Integration Service machine. 9

10 Connection Attribute Required Description Select one of the following options: - No. Disables offload processing. - Auto. PowerExchange determines whether to use offload processing. - Filter Before. Offloads processing to the PowerCenter Integration Service machine but continues to filter data on the source system. - Filter After. Offloads the bulk data processing to the PowerCenter Integration Service machine, including the filtering of data. Default is No. Worker Threads No The number of threads that PowerExchange uses on the PowerCenter Integration Service machine to process bulk data. For optimal performance, this value should not exceed the number of installed or available processors on the Integration Service machine. Valid values are from 1 through 64. Default is 0, which disables multithreading. If you use reader or writer pipeline partitioning, accept the default value of 0. You cannot use both multiple worker threads and partitioning. Array Size No Storage array size, in number of records, that is used for partitioned or multithreaded sessions. For partitioned sessions, this array size is shared across the partitions. Valid values are from 1 through Default is 25. To tune partitioned sessions, particularly when the Write Mode attribute specifies Confirm Write On, increase the array size. Write Mode No Controls whether data is sent to the PowerExchange Listener synchronously or asynchronously. Default is Confirm Write On. Convert character data to string No Convert character fields to string fields so that embedded nulls in data are processed as spaces. By default, this attribute is not selected. Retrieve PWX Log Entries No Controls whether PWXPC writes PowerExchange messages related to a bulk data movement session in the PowerCenter session log. Default is to write PowerExchange messages in the session log. PWX Override No PowerExchange connection override values, separated by semicolons. You can enter any of the following overrides: TCPIP_OP_TIMEOUT=network_operation_timeout; TCPIP_CON_TIMEOUT=connection_timeout; WRT_ERROR_HANDLING=Y; If you use writer partitioning and set the Write Mode attribute to Confirm Write On, you can specify WRT_ERROR_HANDLING=Y to use an alternative method of error handling that is more efficient than the default method when the input data contains many errors. You can also specify this statement in the dbmover.cfg configuration file. Connection Retry Period No Number of seconds that the PowerCenter Integration Service attempts to reconnect to the data source or target if the connection fails. If the PowerCenter Integration Service cannot connect to the database in the retry period, the session fails. Default value is Click OK. The new connection appears in the Application Object Browser. 10

11 For more information about PowerExchange NRDB application connections, see PowerExchange Interfaces for PowerCenter. Step 7. Log In to the ILM Workbench To access the ILM Workbench from a web browser, enter the host name and port number of the ILM server. To log in, enter a user name and password defined in Informatica Administrator. After a period of inactivity, your ILM Workbench session times out and you must log in again. 1. In the address bar of a web browser, enter the URL to access the ILM Workbench in the following format: Where: hostname is the host name or IP address of the machine where you installed the ILM Server. The ILM Workbench also accepts localhost as the host name. portnumber is the port number. The default is For example, you might enter the following URL: The Login dialog box of the ILM Workbench appears. 2. Enter the user name and password in the Login dialog box. Select the security domain. By default, the security domain is Native. If you have configured the Informatica domain to use LDAP authentication, you can select the LDAP security domain. 3. Click Login. The ILM Workbench appears. To log out of and close the ILM Workbench, click Logout > Logout. Step 8. Create an Application An application contains one or more sources and data discovery, subset, and masking components that are associated with the source or source schema. Note: Data discovery operations are not supported for PowerExchange nonrelational sources. From the ILM Workbench, create an application. Specify the PowerExchange sources that you defined in PowerCenter Designer. 1. Click Design to access the Design perspective. 2. On the Designer tab in the Navigator, expand the Data Source View node. Navigate to the Applications node where you want to create an application. 3. Right-click the Applications node, and click Create. 4. In the Create Application dialog box, select or enter the following options: Option Name Description Data Sources Description Required. The name for the application. Optional. The description for the application. Required. The data sources that you want to associate with the application. Any data sources that you select will not be available to other applications. 11

12 5. Click Finish. 6. In the Create Success message box, click OK. The application appears in the selected Applications node. Create objects in the application and configure connections for the application based on the operations that you want to perform. Step 9. Define Data Masking Rules and Policies Use data masking to replace source data in sensitive columns with realistic test data for non-production environments. When you create data masking rules, you define the logic used to replace sensitive data. To specify the sensitive columns that you want to mask, assign data masking rules to source columns and policies. A policy is a collection of data masking rules. When you assign rules to policies, you can assign multiple source columns to the data masking rules. You can also assign a rule directly to a source column. You can assign data masking rules based on the datatype of the source columns. Create a Rule Create a rule to define a masking technique, the datatype to mask, and masking parameters. 1. Click Design to access the Design perspective. 2. On the Designer tab in the Navigator, right-click the Rules node, and click Create. The Rule Wizard dialog box appears. 3. Enter a name and optional description for the rule. 4. Select a masking technique and the datatype to mask. 5. To enable users to override masking parameters for a rule, select the Override Allowed option. 6. Optionally, select a rule qualifier. Select Instruction to configure an instruction qualifier. Select Expression to configure an expression qualifier. Click Configure to build an expression in the Expression Builder. Select None if you do not want to configure a rule qualifier. 7. Click Finish. Create a Policy Create a policy and add one or more rules to it. Optionally, add other policies to it. 1. Click Design to access the Design perspective. 2. On the Designer tab in the Navigator, right-click the Policies node, and click Create. The New Policy dialog box appears. 3. Enter a name and optional description for the policy, and click Next. 4. To allow overrides for masking parameters for rules in the policy or child policies, select the Override Allowed option. 5. To add rules to the policy, click Add Rule. To create a rule, select the New Rule option. Enter information for the rule, and click Finish. To add an existing rule, enter filter criteria and click Go. Select one or more rules, and click Finish. The rules appear in the New Policy dialog box. 12

13 6. To add child policies to the policy, click Add Policy. a. In the Add Components dialog box, enter filter criteria and click Go. b. Select one or more policies, and click Finish. The policies appear in the New Policy dialog box. 7. To add masking parameters to a rule or policy, click the Click Here link in the Parameters column cell for the rule or policy. a. Click the Browse button. b. In the Masking Parameters dialog box, enter properties for the masking parameters. c. To configure an expression, click Configure Expression. In the Expression Builder, build the expression, and click OK. 8. Click Finish. The policy appears in the Policies pane. Step 10. Assign Rules in Policies to Columns Assign rules in policies to one or more columns in the application source that you want to mask. 1. Click Design to access the Design perspective. 2. On the Designer tab in the Navigator, expand the Data Source View node, and navigate to and select the Applications node that contains the application source in which you want to assign policies to columns. The applications appear in the Applications pane. 3. In the Applications pane, select the application. Then, click Policy Assignments. 4. In the Policy Assignment dialog box, select a policy. The rules associated with the policy appear in the Rule grid. 5. Select the rule and click the assign to a port icon on the right. The Port Search dialog box appears. 6. Search for the ports that you want to associate with the rule, and click Finish. The ports appear in the Assignments for Selected Rule grid. 7. To build an expression for the assignment, click the Click here to build expression link in the Expression column for the port. Then, click the Browse button. The Expression Wizard appears. Click Configure to invoke the Expression Builder to build the expression. Click OK, and then click Finish. 8. Click Finish. Step 11. Define Data Subset Components To implement data subset for nonrelational data sources, you can first add groups to the application. Note: You can also add entitites and templates to a data subset application. However, these objects are of limited usefulness for nonrelational sources. Create a Group To create a group, select the tables and residual tables that you want to add to a data subset plan. 1. Click Design to access the Design perspective. 13

14 2. On the Designer tab in the Navigator, expand the Data Source View node. Navigate to the application in the Applications node where you want to create a group. 3. Expand the application, right-click the Groups node for the application, and click Create. 4. In the Create Group dialog box, enter a name for the group and optional description for the group. 5. To select one or more tables for the group, click Add Table. 6. Optionally, you can filter the list of tables by name in the Table Search dialog box. 7. Click Go. The tables that meet the filtering criteria appear in the list of tables. 8. From the list of tables, select one or more tables, and click Finish. The Create Group dialog box shows the selected tables. 9. To choose residual tables to include in or exclude from the group, click Add Residual Tables. The Add Residual Tables - Select Plans dialog box appears. 10. If a plan contains tables that you want to exclude from the residual group, select the plan, and click Next. The Add Residual Tables - Verify Tables dialog box lists the tables to be added to the residual group. 11. Click Finish. 12. In the Confirm message box, click OK. The group appears in the Groups pane. Step 12. Create a Plan When you create a plan, add components to it to define its operations. Add groups or other components to plans to complete data subset operations. Add ports and policies to plans to perform data masking operations. After you add components, you can validate the plan. 1. Click Implement to access the Implement perspective. 2. On the Plan Workbench tab in the Navigator, expand the Data Source View node. Navigate to and select the Plans node for the application for which you want to create a plan. 3. Click the Create button on the toolbar. 4. In the Create New Plan dialog box, enter a name and optional description for the plan. 5. To add a data masking operation to the plan, add data masking components: Component Ports Policies Description Click Add Port. Enter filter criteria in the Port Search Wizard dialog box, and click Go. Select one or more ports, and click Finish. Click Add Policy. Enter filter criteria in the Policy Search Wizard dialog box, and click Go. Select one or more policies, and click Finish. 6. To assign a rule to a port, select a rule. 7. To create and assign a rule, select New Rule Assignment. In the Rule Wizard dialog box, enter information for the rule. Click Next. 14

15 8. Click Finish. 9. To add a data subset operation to the plan, add data subset components: Component Entities Groups Templates Description Click Add Entity. Enter filter criteria in the Entity Search Wizard dialog box, and click Go. Select one or more entities, and click Finish. Click Add Group. Enter filter criteria in the Group Search Wizard dialog box, and click Go. Select one or more groups, and click Finish. Click Add Template. Enter filter criteria in the Template Search Wizard dialog box, and click Go. Select one or more templates, and click Finish. Note: For nonrelational sources, you do not typically add entities or templates. 10. Click Next. The Create New Plan - Create Plan: Step 2 of 2: Define Component Param Values dialog box appears. 11. To define parameters for components in the plan, select the component in the Navigator. The right pane shows defined parameters for the component. 12. Optionally, click Detail Plan Report to run a detail plan report. 13. To validate the plan, click Validate Plan. When the plan validates successfully, the Confirm message box appears. Click OK. 14. Click Finish, and then click OK. The plan appears in the Plans pane. Step 13. Generate a Workflow After you create a plan, generate a workflow to create PowerCenter mappings. 1. Click Implement to access the Implement perspective. 2. On the Plan Workbench tab in the Navigator, expand the Data Source View node. Navigate to and select the Plans node for the application for which you want to generate a workflow. The Plans pane shows the plans. 3. Click Generate Workflow in the toolbar. The Workflow Configuration Page dialog box appears. 4. In the Workflow Configuration Page dialog box, define properties, and click OK. 15

16 The following table describes the properties that you configure on the General tab of the Workflow Configuration Page dialog box: Property Masking Type PowerCenter Folder Connections Description The masking type. Select Instream to mask the target. Read-only. The selection in the Name list shows the PowerCenter folder where the mapping is generated. The workflow connections. Select the source and target PowerExchange connections that you defined in the Workflow Manager. The following table describes the properties that you configure in the Advanced tab of the dialog box: Property Maximum Limits Locale Override Optimization Parameters Description The maximum number of workflows and sessions that you want to run. The data masking locale. The default task to perform for duplicate sources or mapplets. Select Reuse or Replace. Optimizes the performance of data masking and data subset operations. Step 14. Edit the Session Properties After you generate a workflow, edit the session properties for the workflow. For sources and targets, review or edit session attributes. 1. In the Workflow Designer, double-click the session to open the session properties. 2. On the Mapping tab, click the Sources view. In the Reader field of the Readers settings, the PowerExchange batch reader for the specific source type is shown. Verify that the reader for sequential or VSAM files is selected. 3. In the Connection Value field, verify that the appropriate application connection for the source is selected. 4. In the Properties settings, view or edit session attributes for the source. The following attributes apply to sequential or VSAM sources: Attribute Name Source Type Description Schema Name Override All Overrides the source PowerExchange data map schema name. Map Name Override All Overrides the source PowerExchange data map name. Filter Overrides All Filters the source data that PowerExchange reads based on specified conditions. PWXPC adds filter conditions specified to the WHERE clause on the SELECT SQL statement and passes the SQL statement to PowerExchange for processing. You can use 16

17 Attribute Name Source Type Description any filter condition syntax that PowerExchange supports for NRDB SQL. For a single-record source, use the following syntax: filter_condition For example, you can select records where a column called TYPE has a value of A or D by specifying the following filter condition: TYPE= A or TYPE= D File Name Override VSAM, SEQ Overrides the data set or file name in the PowerExchange data map. Enter enter the complete data set or file name. Filelist File VSAM, SEQ Select if the File Name Override field contains the data set name of a list of files. Select this option only if you have entered a filelist file for File Name Override. SQL Query Override All Overrides the SQL query sent to PowerExchange, including any Filter Overrides. PWXPC replaces the default SQL query with the SQL statement that you enter and passes the SQL statement to PowerExchange for processing. You can enter any SQL statement that PowerExchange supports for NRDB SQL. For a single-record source, use the following syntax: SQL_query_override For example, you can select records from table USER where a column called TYPE has a value of A or D by specifying the following SQL query override: Select ID, NAME from USER where TYPE= A or TYPE= D ; PWX Partition Strategy Offloaded DB2 Unload, VSAM, and sequential data sets Specifies one of the following partitioning strategies: - Single Connection. PowerExchange creates a single connection to the data source. Any overrides specified for the first partition are used for all partitions. With this option, if you specify any overrides for other partitions that differ from the overrides for the first partition, the session fails with an error message. - Overrides Driven. If the specified overrides are the same for all partitions, PowerExchange creates a single connection to the data source. If the overrides are not identical for all partitions, PowerExchange creates multiple connections. 5. On the Mapping tab, click the Targets view. 6. In the Connection Value field, verify that the appropriate application connection for the target is selected. 7. In the Properties settings, view or edit session attributes for the target. The following attributes apply to sequential or VSAM sources: Attribute Name Target Type Description BLKSIZE SEQ (MVS only) MVS data set block size. 17

18 Attribute Name Target Type Description Default is 0 (best possible block size). DATACLAS SEQ (MVS only) MVS SMS data class name. Delete SQL Override ADABAS, IMS, VSAM Overrides default Delete SQL sent to PowerExchange. Disp SEQ (MVS only) MVS data set disposition. Valid values are: - OLD - SHR - NEW - MOD Default is MOD if the data set exists, and NEW if it does not. File Name Override SEQ, VSAM Overrides the data set or file name in the PowerExchange data map. Enter the complete data set or file name. Important: Be sure to specify a different filename from the source filename. Initialize Target VSAM For empty VSAM data sets, requests that PowerExchange use open options that allow both inserts and updates. If this option is not selected, PowerExchange allows inserts into empty VSAM data sets only. Insert Only ADABAS, IMS, VSAM Processes updates and deletes as inserts. Note: You must select this option when the target has no keys. Insert SQL Override All Overrides the default Insert SQL sent to PowerExchange. LRECL SEQ (MVS only) MVS data set logical record length. Value is ignored if Disp is not either MOD or NEW. Default is 256. Map Name Override All Overrides the target PowerExchange data map name. Note: PWXPC sends the file name from the source in the mapping unless it is overridden in File Name Override. MGMTCLAS SEQ (MVS only) SMS management class name. Value is ignored if Disp is not either MOD or NEW. MODELDSCB SEQ (MVS only) MVS Model DSCB for non-sms-managed GDG data sets. Value is ignored if Disp is not either MOD or NEW. Post SQL All One or more SQL statements that are executed after the session runs with the target database connection. Pre SQL All One or more SQL statements that are executed before the session runs with the target database connection. Primary Space SEQ (MVS only) MVS Primary space allocation, in the units specified in Space. Value is ignored if Disp is not either MOD or NEW. Default is 1. RECFM SEQ (MVS only) MVS record format. Valid values are: F, V, FU, FB, VU, VB, FBA, VBA. 18

19 Attribute Name Target Type Description Value is ignored if DISP is not MOD or NEW. Schema Name Override All Overrides the target PowerExchange data map schema name. Note: PWXPC sends the file name from the source in the mapping unless it is overridden in File Name Override. Secondary Space SEQ (MVS only) MVS Secondary space allocations, in the units specified in Space. Value is ignored if Disp is not either MOD or NEW. Default is 1. Space SEQ (MVS only) MVS data set space units. Values are: - CYLINDER - TRACK Value is ignored if Disp is not either MOD or NEW. Default is TRACK. STORCLAS SEQ (MVS only) SMS storage class name. Value is ignored if Disp is not either MOD or NEW. Truncate Table Option IMS, VSAM Truncates table (deletes contents) before loading new data. Note: VSAM data sets must be defined with the REUSE option for truncate to function correctly. UNIT SEQ (MVS only) MVS unit type. Value is ignored if Disp is not either MOD or NEW. Default is SYSDA. Update SQL Override ADABAS, IMS, VSAM Overrides the default Update SQL that is sent to PowerExchange. Upsert ADABAS, IMS, VSAM Processes failed inserts as updates and updates as inserts. VOLSER SEQ (MVS only) MVS volume serial number. Value is ignored if Disp is not either MOD or NEW. 8. Click OK. For more information, see PowerExchange Interfaces for PowerCenter. Step 15. Start the Workflow After you generate and customize a workflow, you can start it to run sessions from the PowerCenter mappings. If you generated multiple workflows for the same plan, you can start each workflow separately. 1. Click Implement to access the Implement perspective. 2. On the Plan Workbench tab in the Navigator, expand the Data Source View node. Navigate to and select the Plans node for the application for which you want to generate a workflow. The Plans pane shows the plans. 3. If the plan you selected contains one workflow, click Start Workflow in the toolbar. 19

20 4. If the plan you selected contains multiple workflows, click the Workflow Components tab. a. Select the workflow you want to start. b. Click Start Workflow in the lower toolbar. 5. Click the Refresh button to update the status of the workflow. Step 16. Monitor the Workflow When you start a workflow, you can monitor its progress in the Plan Workflow Monitor window. If you generate a workflow for each table in a plan, you can open the Plan Workflow Monitor for individual workflows. 1. Select a plan in the Plans pane of the Implement perspective. 2. If the plan contains one workflow, click Plan Load Monitor in the toolbar. The Plan Load Monitor window appears. 3. If the plan contains multiple workflows, select the Workflow Components tab. a. Select a workflow in the Workflow Components tab. b. Click Plan Load Monitor. The Plan Load Monitor window appears. Author Jim Middleton Principal Technical Writer 20