Fast Data Masker System Requirements

The Fast Data Masker component has the following system requirements. If you install Fast Data Masker with other components during the Server installation, ensure that your system meets the requirements.
tdm49
The Fast Data Masker component has the following system requirements. If you install Fast Data Masker with other components during the Server installation, ensure that your system meets the requirements.
2
2
Operating System
RHEL 6.0, RHEL 7.0, and Windows 7 (or higher) are supported.
Java
Fast Data Masker requires Java Runtime Environment (JRE) version 1.8.
Note:
If there is a problem with Java, Fast Data Masker contains a /jre folder that contains a suitable Java version.
Masking Rules and Files
  • All masking rules are stored in comma-separated text files.
  • Fast Data Masker contains a standard set of seed data files that you can easily add and amend.
Supported Data Sources
For the complete list of supported data sources (for example, database types, mainframe platforms, or file formats) for masking, see Supported Data Sources.
Additionally, you can review the following points:
  • For DB2 on z/OS, ensure that the db2jcc4.jar, db2jcc4_license_cu.jar, and db2jcc4_license_cisuz.jar files are available in the ..\Grid-Tools\FastDataMasker\lib folder.
    Note:
    The default location where Fast Data Masker is installed is C:\Program Files\Grid-Tools\FastDataMasker.
  • For DB2 on iSeries (AS400), ensure that the jt400.jar file is available in the ..\Grid-Tools\FastDataMasker\lib folder.
  • The following file formats are not supported:
    • HIPAA 40-10, 50-10, X12
    • EDI Files
    • SWIFT
  • For Netezza, the following points are applicable:
    • Ensure that you can create external tables; that is, create external table privileges for the login user.
    • Increase the commit size to at least the size of the largest table to be masked.
    • PARALLEL option is not supported for Netezza, as only one external table can be created at a time.
    • If PTS is being used, this has to be run on the Primary.
    • NPS client needs 1 GB of memory per million rows being masked; this is an approximate estimate. The memory requirement depends on the size of the table to be masked (row count) and the number of columns being masked.
    • Copy the nzjdbc.jar file to the ..\Grid-Tools\FastDataMasker\lib folder.
Minimum Resolution
The minimum resolution for the Fast Data Masker UI must be greater than 1024 x 768 pixels.
Maximum Memory Parameter
When you mask large XML files, set the maximum memory (JVM heap size) to eight times more than the XML file. For example, if the XML file is 1 GB, set the maximum memory to 8 GB.
The memory is required primarily to hold the DOM tree structure of the XML document.
If the
namespace aware
is on, set the maximum memory to ten times the size of the XML file.
To set the maximum memory in the FDM Mapper UI, update the
Max Memory (MB)
field at the bottom of the
Summary
tab.
To use the FastDatamasker_flat.jar directly, set the maximum memory in the -Xmx parameter. For example:
java -Xms100M -Xmx8000M -jar Fastdatamasker_flat.jar connect_xml.txt xpath.csv
Namespaces
By default, XML masking is not namespace aware. The XPath query is used literally with namespace prefixes that are not interpreted. For example, an XPath
/bookstore/bk:book/ti:title
looks under
bookstore
nodes for nodes with the name
ti_title
.
XML documents might have parallel or nested namespace declarations where prefixes are not uniquely mapped to namespace URLs. For example:
  • The same prefix that is used for more than one namespace
  • Different prefixes are used for the same namespace
In these cases, turn on namespace aware. This setting lets your XPath queries select the correct elements to mask in the XML document.
To turn on namespace aware, set the XMLNAMESPACEAWARE options parameter to Y.
Next, provide a mapping of prefixes to use in your XPath queries, to namespaces.  Define the prefixes in the XPATHNAMESPACEMAP options parameter.
This parameter has the following format:
prefix1=url1; prefix2=url2; ...
Example:
bk=urn:xmlns:25hoursaday-com:bookstore; inv=urn:xmlns:25hoursaday-com:inventory-tracking
The prefixes in the XPath queries might be different from the prefixes that are used in the XML document.  You can select the prefixes to use in the XPATH, but ensure that you specify the prefixes in XPATHNAMESPACEMAP.
Note:
The prefixes in your document might not map uniquely to namespace URLs.
To scan large XML documents to find the namespace URLs to use in your XPath, run an initial mask run. Use the following values:
  • XMLNAMESPACEAWARE =Y
  • Empty XPATHNAMESPACEMAP
  • XPath
    Example:
    /a/b
FastDatamasker parses your XML file and lists the namespace declarations. For example:
Namespaces declared in the XML document:
=urn:xmlns:25hoursaday-com:bookstore bk=urn:xmlns:25hoursaday-com:bookstore bka=urn:xmlns:25hoursaday-com:bookstore bk=urn:xmlns:26hoursaday-com:bookstore inv=urn:xmlns:25hoursaday-com:inventory-tracking
This example shows that the document has three declarations to the namespace URL
urn:xmlns:25hoursaday-com:bookstore
. The first declaration is the default namespace with an empty prefix. The prefix
bk
is used for two different namespace URLs.
Default Namespace Example
Consider the following XML file:
<table xmlns="http://www.w3.org/TR/html4/"> <tr> <td>Computers</td> </tr> </table>
In this example, the XPath to modify
Computers
is as follows:
/DEFAULT:table/DEFAULT:tr/DEFAULT:td
Therefore, for the default namespace, update the XPath for your XML files as shown above. The DEFAULT automatically maps to the default namespace.
Copy
sqljdbc_auth.dll
to Appropriate Locations for Microsoft SQL Server (Integrated Authentication).
If integrated authentication is enabled on the Microsoft SQL Server database, ensure that you copy the required
sqljdbc_auth.dll
file to the appropriate location.
If you are using the Fast Data Masker Mapper, copy the file as follows:
  • For 32-bit, copy
    sqljdbc_auth.dll
    from
    C:\Program Files\Grid-Tools\FastDataMasker\SQLSERVER_DLLs\x86
    to
    C:\Program Files\Grid-Tools\FastDataMasker
    (where Fastdatamasker.jar exists).
  • For 64-bit, copy
    sqljdbc_auth.dll
    from
    C:\Program Files\Grid-Tools\FastDataMasker\SQLSERVER_DLLs\x64
    to
    C:\Program Files\Grid-Tools\FastDataMasker
    (where Fastdatamasker.jar exists).
Note:
The default location where Fast Data Masker is installed is 
C:\Program Files\Grid-Tools\FastDataMasker
.
If you are using the batch file that was saved from the Fast Data Masker Mapper, copy the file as follows:
  • For 32-bit, copy
    sqljdbc_auth.dll
    from
    C:\Program Files\Grid-Tools\FastDataMasker\SQLSERVER_DLLs\x86
    to
    %APPDATA%\Grid-Tools\FastDataMasker
    (where the batch file exists).
  • For 64-bit, copy sqljdbc_auth.dll from
    C:\Program Files\Grid-Tools\FastDataMasker\SQLSERVER_DLLs\x64
    to
    %APPDATA%\Grid-Tools\FastDataMasker
    (where the batch file exists).
Limitations
Review the following limitations:
  • The use of Fast Data Manager on databases to which the user is connected via a VPN, can cause a 'Socket Error' / 'Socket write error' / 'Socket read timed out' error. We recommend the use of Fast Data Manager only with a local connection to the database.
  • The XML parser only supports simple DOCTYPE declarations with no nested groups. The following expressions are not supported in XPATH queries:
    • filter (select left from right)
    • variables
    • number()
    • text()
    • string()
    • name()
    • local-name()
  • In the case of XML file masking, if your XML has a large number of nodes (for example, more than 10,000), the XPATH segments are not displayed in the
    Add XPATH to mask
    drop-down list in the
    Masking
    tab. You must manually enter the XPATH in
    Add XPATH to Mask
    and click the
    Add
    button to proceed with the masking.