FDM Batch Files Generated via TDM Portal Fail to Mask Data when Executed in Javelin

Products

• CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

A .BAT file generated from the TDM Portal executes successfully in Javelin's InvokeProcessActivity, but no data masking occurs in the target database.

The same masking operation works correctly when using a .BAT file generated directly from the Fast Data Masker (FDM) UI.

Javelin-generated AUDIT files do not contain execution tracking data such as volume of rows masked or time elapsed.

Environment

• Test Data Manager (TDM) Portal
• Fast Data Masker (FDM)
• Javelin Workflow Automation

Resolution

To resolve the masking failure and capture audit metrics, follow these steps:

1. Modify Pathing to Absolute

Edit the .BAT file generated by the TDM Portal. Locate the masking command and replace the relative filenames with their full absolute paths.

Example (Portal Generated):
%FDM% "connection.txt" "masking.csv" "options.txt"

Example (Corrected):
%FDM% "C:\TDM\Work\connection.txt" "C:\TDM\Work\masking.csv" "C:\TDM\Work\options.txt"

2. Enable Console Redirection for Auditing

To capture execution metrics (rows masked, time elapsed) for Javelin audit logs, modify the execution line in the batch file to redirect output to a log file:

%FDM% "C:\Path\To\Conn.txt" "C:\Path\To\Mask.csv" "C:\Path\To\Options.txt" > C:\TDM\Logs\MaskingResult.log 2>&1

3. Update Javelin Workflow

After the InvokeProcessActivity completes, add a step in Javelin to read the MaskingResult.log file. This content can then be parsed or appended to your Javelin audit logs for full visibility.