Detokenization.properties File
Detokenization.properties
file explains all the parameters required to run the CT-V Bulk Utility for detokenization of tokens in File-to-File operation using token vault. It allows the user to configure the input and output files.
Below is a sample parameters file that can be used as a template:
Properties Settings
The Input.Type
refers to the way in which columns of input data are separated and identified for processing purposes. The Input.Type
must be set to either Delimited or Positional. The individual pieces of data in the input data file can be separated by delimiters (e.g., by commas) or set up according to a positional format. Processing does not allow for any formatting mistakes; there is no recovery or line-exception-reject processing.
Note
In case of stream data, positional format is to be used for Input.Type
file, and the new row starts after the position specified in the Input.ColumnN.End
parameter.
If you use a delimiter-separated-value file, then you can use escape characters to handle instances of special characters that would otherwise impact processing. The utility enables you to uniquely identify each column of data so that, if the column needs decryption, you can specify the key name, decryption algorithm (AES/CBC/PKCS5Padding), and decryption encoding (Base16, Base64).
The utility similarly enables you specify, for each column:
TokenVault
- The name of the token vault that will be used for tokenization or detokenization.CustomDataColumnIndex
- An index number assigned to a column in the input file. This index number has to appear in the output file, in the output sequence, if the column is to be used for output. TheOutput.Sequence
makes use of theCustomDataColumnIndex
.TokenFormat
- The token formats available for use are listed in themigration.properties
anddetokenization.properties
file for tokenization and detokenization respectively.LuhnCheck
- This is the value that is passed to TokenService insert method. Depending on the format of the value (e.g., FIRST_SIX_LAST_FOUR_FAIL_LUHN_TOKEN or EMAIL_ADDRESS_TOKEN), you can use this to define whether the token should pass luhn check, fail luhn check, or if it doesn't matter. When the luhn check matters, this input value (true or false) determines whether the luhn check logic specified by the format is enforced or ignored.
The following Multi-threading Configuration values can be adjusted to achieve performance improvements:
Threads.BatchSize
- Use this to set the number of rows in your batch. This controls how the input file is split in batches by controlling the number of rows in a batch. Depending on your system, you may need to adjust this value to achieve optimal performance. Recommended value is 10,000.Threads.CryptoThreads
- Use this to set the number of threads that will perform decryption of columns. This can be adjusted to change the ratio of Crypto to Tokenization threads, and to decrease the time for processing of the batch size, to achieve optimal performance.Threads.TokenThreads
- Use this to set the number of threads that will perform tokenization of columns. As with the crypto thread number, this can be adjusted for performance optimization.Threads.PollTimeout
- The amount of time (in milliseconds) processing threads will wait for a batch on the data queue before timing out, looking for more work in the queue, and checking for another batch. Leave this set at the default of 100 milliseconds. Do not change this parameter unless instructed to do so by customer support.
Predefined Token Formats
The following predefined token formats are available that can be used in the Bulk Utility:
RANDOM_TOKEN
RANDOM_ALPHANUMERIC_TOKEN
SEQUENTIAL_TOKEN (can be used with sequential vault only)
LAST_FOUR_TOKEN
FIRST_SIX_TOKEN
FIRST_TWO_LAST_FOUR_TOKEN
FIRST_SIX_LAST_FOUR_TOKEN
FIXED_NINETEEN_TOKEN
FIXED_TWENTY_LAST_FOUR_TOKEN
EMAIL_ADDRESS_TOKEN
DATE_MMDDYYYY_TOKEN
DATE_DDMMYYYY_TOKEN
DATE_YYYYMMDD_TOKEN
FIRST_SIX_LAST_FOUR_FAIL_LUHN_TOKEN
FIXED_FIRST_TWO_LAST_FOUR_FAIL_LUHN_TOKEN
SHA2_256_BASE16_TOKEN
SHA2_384_BASE16_TOKEN
SHA2_512_BASE16_TOKEN
SHA2_256_ BASE64_TOKEN
SHA2_384_ BASE64_TOKEN
SHA2_512_ BASE64_TOKEN
ALPHANUMERIC_TOKEN