Copy the Requisite Files into a Subset folder

As discussed in the process overview, data subsetting is one of Test Data Automation’s high-speed TDM utilities. A generic VIP Workflow performs a range of Subset Actions that are defined in the Control Spreadsheet. The Actions are customisable, with a range of variables that can be defined before execution. The actions and workflows are executed using the VIP Server Controller, a desktop application used to define the parameters and run the automation.

The Control Spreadsheet and VIP Server Controller are used to run and refine a Subset iteratively, working until you are happy with its results. Once the Subset job has been defined, the Actions and associated variables can then be exposed in self-service web forms. This enables other users to trigger the Subset using a simple, self-service web portal.

Note: You can also parameterize actions in a Command Script and execute the actions from the command line rather than the VIP Server Controller. For this, a standard set of editable .CMD scripts are shipped with the VIP Server Controller installation.

The following requisite files are needed to define and perform the Subset Actions. They are stored in two folders. One folder contains the files you need to edit and work with. The other contains the static files used to execute the automation:

1. VIPTDM\SubsetCloneAndMaskRun – This folder contains the configuration files that you should edit. These files are:
   1. A blank Basic Control Spreadsheet that points the VIP workflow to the database that will be modelled and subsetted. This is called “VIPSubsetStartPoint” by default.
   2. A FlowCache.txt – this is used to tell the VIP Server Controller the location of VIP workflows to put “in memory”. This improves the performance of the automation.
   3. The standard scripts used to execute the Subset Actions. These scripts are used to parameterize and execution the Subset Actions if executing Actions from the Command Line instead of the VIP Server Controller.the file name of each script reflects the action it performs. The numeration reflects the typical order in which you would run the actions when iterating Subsets. The scripts are:
      1. Subset1_getmetadata.cmd
      2. Subset2_prepenv.cmd
      3. Subset3_buildmodel.cmd
      4. Subset4_subset.cmd
      5. Subset4_truncatesubset.cmd
2. VIPTDM\SubsetCloneAndMask – This folder contains the static files you will use to execute the automation. These files are:
   1. The automated workflows used to perform the Subset Actions:
      1. SQLSubset.enc.vip
      2. SQLActions.enc.vip
   2. The .DLL Files associated with the automated Workflows.
   3. The .XML files associated with the automation.
   4. TXT Files associated with the automation.

These files are shipped as part of the VIP Server Controller installation. If you followed the defaults when installing the VIP Server Controller, you can locate these two folders under C:\VIPTDM. Otherwise, please navigate to the install location and find the “VIPTDM” folder.

For a Subset, you only need to edit files stored in C:\VIPTDM\SubsetCloneAndMaskRun. This folder also contains the files used to run a date Clone or Mask, which are often performed in conjunction with Subsetting.

It is recommended that you create a folder for each individual Subset. This enables you to easily return to edit individual subsetting jobs. It also avoids unnecessary rework, helping to avoid previously configured Subsets being edited or lost.

You might additionally incorporate a file structure where each Subset folder is stored under individual folders for individual Databases or Schemas.

Start by copying all files from C:\VIPTDM\SubsetCloneAndMaskRun to a new folder: 

The VIP flows are encrypted and you need a valid subsetting license to run them. If you do not have licensed copies of the above files, please email your Curiosity account manager or email info@Curiosity.Software.