Table of Contents

Search

  1. Preface
  2. Introduction to Transformations
  3. Transformation Ports
  4. Transformation Caches
  5. Address Validator Transformation
  6. Aggregator Transformation
  7. Association Transformation
  8. Bad Record Exception Transformation
  9. Case Converter Transformation
  10. Classifier Transformation
  11. Comparison Transformation
  12. Consolidation Transformation
  13. Data Masking Transformation
  14. Data Processor Transformation
  15. Decision Transformation
  16. Duplicate Record Exception Transformation
  17. Expression Transformation
  18. Filter Transformation
  19. Hierarchical to Relational Transformation
  20. Java Transformation
  21. Java Transformation API Reference
  22. Java Expressions
  23. Joiner Transformation
  24. Key Generator Transformation
  25. Labeler Transformation
  26. Lookup Transformation
  27. Lookup Caches
  28. Dynamic Lookup Cache
  29. Match Transformation
  30. Match Transformations in Field Analysis
  31. Match Transformations in Identity Analysis
  32. Normalizer Transformation
  33. Merge Transformation
  34. Parser Transformation
  35. Python Transformation
  36. Rank Transformation
  37. Read Transformation
  38. Relational to Hierarchical Transformation
  39. REST Web Service Consumer Transformation
  40. Router Transformation
  41. Sequence Generator Transformation
  42. Sorter Transformation
  43. SQL Transformation
  44. Standardizer Transformation
  45. Union Transformation
  46. Update Strategy Transformation
  47. Web Service Consumer Transformation
  48. Parsing Web Service SOAP Messages
  49. Generating Web Service SOAP Messages
  50. Weighted Average Transformation
  51. Window Transformation
  52. Write Transformation
  53. Appendix A: Transformation Delimiters

Developer Transformation Guide

Developer Transformation Guide

Identity Match Type Properties

Identity Match Type Properties

Use the Match Type view to specify the type of analysis that the Match transformation performs and to set the properties that define the analysis. You can specify single-source analysis or dual-source analysis. You can also specify a persistent data store for the identity index data.
The properties that you configure depend on the type of analysis that you select. Many of the options are common to all types of analysis.

Common Properties

The following properties are common to all types of identity analysis:
Population
Identifies the population file that the transformation uses. The population file contains the key-building algorithms that generate the index keys.
Key Level
Determines the number of keys that the identity algorithms generate. The default setting is
Standard
. The
Limited
setting results in a lower number of keys, higher accuracy, and longer processing time. The
Extended
setting results in a higher number of keys, lower accuracy, and shorter processing time.
Key Type
Describes the type of information that the key field contains. Identity analysis can generate keys for person names, organizations, and addresses. Select the key type that best describes the column that you specify on
Key Field
property.
Search Level
Indicates the balance of search depth and search speed that the transformation applies to the match analysis. The search depth corelates inversely to the number of matches returned. For example, the
Exhaustive
option returns fewer matches.
Key Field
Specifies the column that the Match transformation uses to generate the index key data. Verify that the column that you select contains the type of information that you specified on the
Key Type
property.
Index Directory
Identifies the directory to which the Data Integration Service writes index key data for the current transformation. By default, the property is blank. If you do not specify an index directory, the Data Integration Service uses the location that you set on the Content Management Service.
You can enter a path to the directory, or you can use a parameter to identify the directory. Specify a local path on the Data Integration Service machine. The Data Integration Service must be able to write to the directory.
Cache Directory
Identifies the directory to which the Data Integration Service writes temporary data during the index creation stage of identity match analysis. Update the property to specify a location for data from the current transformation. By default, the property is blank. If you do not specify a cache directory, the Data Integration Service uses the location that you set on the Content Management Service.
You can enter a path to the directory, or you can use a parameter to identify the directory. Specify a local path on the Data Integration Service machine. The Data Integration Service must be able to write to the directory.
Cache Size
Determines the amount of system memory that the Data Integration Service assigns to identity index creation. The default value is 400,000 bytes.
If the index creation operation generates a greater amount of data, the Data Integration Service writes the excess data to the cache directory. If the operation requires more memory than the system memory and the file storage can provide, the mapping fails.
If you enter a value of 65536 or higher, the transformation reads the value in bytes. If you enter a lower value, the transformation reads the value in megabytes.

Dual-Source Properties

Set the following property in addition to the common properties when you configure the transformation for dual-source analysis:
Master Data Set
Identifies the data source that contains the master data. Specify a master data set in dual-source analysis.

Persistent Data Storage Properties

Set the following properties in addition to the common properties when you configure the transformation to use the persistent index data store:
Persistence Method
Specifies whether the transformation updates the current index tables with index data from the mapping data source. Select one of the following options:
  • Update the database with new IDs.
    The transformation adds all rows to the index data that do not duplicate a sequence identifier in the index data. The transformation does not update the current rows in the index.
    By default, the transformation performs match analysis when you select the option. You can use the Matching Process option to enable or disable the match analysis.
  • Do not update the database.
    The transformation does not update the index tables with index data from the mapping data source.
    The transformation performs match analysis when you select the option.
  • Remove IDs from the database.
    The transformation deletes rows from the index tables if the rows share sequence identifiers with the mapping source data.
    The transformation does not perform match analysis when you select the option.
  • Update the current IDs in the database.
    The transformation replaces rows in the index tables with rows from the mapping source data if the rows share sequence identifiers. The transformation does not add rows to the index.
    By default, the transformation performs match analysis when you select the option. You can use the Matching Process option to enable or disable the match analysis.
The default persistence method is
Update the database with new IDs
.
Matching Process
Determines whether the current transformation performs identity analysis.
The option that you select on the Persistence Method property determines the options on the Matching Process property.
DB Connection
Identifies the database that contains the index tables.
Persistent Store
Identifies the index tables within the database that you specify.

0 COMMENTS

We’d like to hear from you!