Table of Contents

Search

  1. Preface
  2. Working with Transformations
  3. Aggregator Transformation
  4. Custom Transformation
  5. Custom Transformation Functions
  6. Data Masking Transformation
  7. Data Masking Examples
  8. Expression Transformation
  9. External Procedure Transformation
  10. Filter Transformation
  11. HTTP Transformation
  12. Identity Resolution Transformation
  13. Java Transformation
  14. Java Transformation API Reference
  15. Java Expressions
  16. Java Transformation Example
  17. Joiner Transformation
  18. Lookup Transformation
  19. Lookup Caches
  20. Dynamic Lookup Cache
  21. Normalizer Transformation
  22. Rank Transformation
  23. Router Transformation
  24. Sequence Generator Transformation
  25. Sorter Transformation
  26. Source Qualifier Transformation
  27. SQL Transformation
  28. Using the SQL Transformation in a Mapping
  29. Stored Procedure Transformation
  30. Transaction Control Transformation
  31. Union Transformation
  32. Unstructured Data Transformation
  33. Update Strategy Transformation
  34. XML Transformations

Transformation Guide

Transformation Guide

Dictionaries

Dictionaries

A dictionary is a flat file or relational table that contains the substitute data for each row in the file. The Data Masking transformation generates a number to retrieve a dictionary row. The Data Masking transformation generates a hash key for repeatable substitution masking or a random number for non-repeatable masking. You can configure an additional lookup condition.
You can configure a dictionary to mask more than one port in the Data Masking transformation.
The following example shows a flat file dictionary that contains first name and gender:
SNO,GENDER,FIRSTNAME 1,M,Adam 2,M,Adeel 3,M,Adil 4,F,Alice 5,F,Alison
In this dictionary, the first field in the row is the serial number, and the second field is gender. You can add gender as a lookup condition. The Integration Service retrieves a row from the dictionary using a hash key, and it finds a row with a gender that matches the gender in the source data.
Use the following rules and guidelines when you create a dictionary:
  • The first row of a flat file dictionary must have column labels to identify the fields in each record. The fields are separated by commas. If the first row does not contain column labels, the Integration Service takes the values of the fields in the first row as column names.
  • A flat file dictionary must be in the $PMLookupFileDir lookup file directory. By default, this directory is in the following location:
    <PowerCenter_Installation_Directory>\server\infa_shared\LkpFiles
  • If you create a flat file dictionary on Windows and copy it to a UNIX machine, verify that the file format is correct for UNIX. For example, Windows and UNIX use different characters for the end of line marker.
  • If you configure substitution masking for more than one port, all relational dictionaries must be in the same database schema.
  • The line sequential buffer length of a flat file dictionary must be less than or equal to 600 characters.
  • You cannot change the dictionary type or the substitution dictionary name in session properties.

0 COMMENTS

We’d like to hear from you!