Create a New Translate Table
A translate table is a table of replacement values for the data that you want to disguise. First your translate table is defined. Later, when the translation technique is selected, the user chooses from a list of predefined translate tables and access paths. The Manage Translate Tables view lists the currently defined translate tables and allows you to create new ones.
Before you can create a translate table, you must open the repository where the translate table will reside.
To create a translate table:
- From the Data Privacy Menu, Resource Administration stack bar, select Manage Translate Tables.
- Click Add. The New Translate Table wizard is initiated.
Enter a Translate Table Name or accept the default name and enter an optional Description.
The Translate Table Name is the name that appears in the list of translate tables that can be chosen for a particular rule. This name is used within the disguise rule action to request the use of a specific translate table. The disguise rule does not see the actual database table name or location, only the Translate Table Name.
- Click Next. The Source view appears.
To select the source for the translate table, Browse for the Table Host and actual table name. Select Credentials from the list, or click Add to create a new credential.
Use the Test button to verify that the specified credential can successfully log on to the specified host. A Validate Connection message will appear indicating whether the connection was successful.
For more information, see Translate Table Source.- If you are using DB2, SQL Server, or Oracle, continue with the next step.
- If you are using a mainframe database (z/OS), the screen will change and two new sections are added. Enter the desired Metadata Layout. Browse for the Host and Layout for the translate table. It may take a few moments for the metadata layout to compute. Specify the Source CCSID if necessary.
Check the box to Allow mainframe translate table to be accessed by File-AID/EX Data Privacy. Provide the Executive Host and Executive Port information.
- Click Next. The Field Mapping view will appear.
Create a label for each of the fields that you want to appear in the translate table. Fields that are not mapped cannot be used. To create the label, click in the Label column next to the desired field. Click the drop down button to show a list of available label values. Select the label or type in a label of your choice.
In edit mode, this page will show a list of the previously created labels along with the field. To change or create new labels, click the link Reload table to map labels to fields. This will fetch the metadata from the database and show the fields in the list. Previously created labels will automatically be mapped to the field.
A warning message will appear if any of the labels cannot be mapped.
The Label all button can be used to automatically label all the fields using the field names.
- Click Next. The Access Path Failed view appears. This view includes three tabs that let you specify the action to take if access to this translate table fails.
There are three choices on the Actions tab if the source value is not found during disguise execution:
- For each of the labels, enter a return value, which will be used to specify what will be returned if access to the translate table fails to return a row. If no value is specified, blanks will be returned for character fields and zeroes will be returned for numeric fields. For more information, see Translate-Table-Access-Path-Failed To specify values to return, when the access path fails to return a value from the translate table, select Values to return and enter the value in the Return Value column in the table.
- Retain the source value.
- Apply format-preserving encryption to the source value. If this option is selected, select an encryption key from the list.
- On the Long Data Values tab, there are two choices when the source value is longer than the translate table value:
- Process as source not found; invoke access path failed. This is the default.
- Truncate long source data value, no warning will be logged
- On the Logging Options tab, you can select one or both of the following logging options, but they are not required:
- Log warning messages
When this option is selected, a warning message, including the source value will be written to the Java detail log. If this option is not selected, a count of access path failed values will be written to the Java detail log, but no actual source values will be logged.
When the logging option is selected, a checkbox is enabled to specify a warning threshold and a count of the maximum number of warning messages to write. When this threshold is reached, logging values will stop but access path failed values will continue to be counted.
The count of values is reported on a per source field basis, so the logging threshold applies to each field as well.
- Execution threshold
- The option to specify an execution threshold is provided to enable you to stop the disguise job from executing if the count of access path failed values exceeds the threshold value specified. Choose a number that is higher than the number of failures you would reasonably expect in the field.
- Click Next. The Project Availability view appears. There are two choices:
- Make this translate table available to all projects. Select this option to allow all projects to access this translate table.
- Restrict availability of this translate table to the projects selected below. Select this option and check the desired projects to restrict access to this translate table to only the selected projects.
Click Next. The References view appears. This view presents a report of the translate table's usage. The project view list shows all the projects that use this translate table. The project, along with rules and rule actions, is displayed in the list. If a label is being used in a rule action and is not defined in the translate table, an Error: Not mapped message appears in the Messages column.
Click the Show label view link to switch the view to label view. This view displays the report by label. Expand the tree to show the project, rule, and rule actions that are using each label. If a label is defined in the translate table, but is not being used in any project, a Not used message appears in the Messages column.
Click Finish. Your translate table now appears in the list of translate tables on the Manage Translate Tables view.