Prepare your Staging Database
Search Knowledge Base by Keyword
The PREPENV (“prepare environment”) action creates the tables and indexes in the Staging Database.
To run PREPENV, open The VIP Server Controller from your desktop or start menu. You must open it as an administrator.
If you have a re-usable Config file for your Subset Actions, load it in The VIP Server Controller. See this article for instructions.
Check and complete all mandatory parameters in the “Flow Cache Server” tab and commit the automated workflows to memory. See this article for instructions.
Next, complete the mandatory parameters in the “Run Flow” tab. In addition to filling out the mandatory fields in the UI, PREPENV generally requires the following Arguments:
parAction – Enter PREPENV to run the PREPENV action:
parAction=PREPENV
parControlExcel – Specify the location of your Excel Configuration spreadsheet. For example:
parControlExcel=C:\Users\VIP1\Documents\Subsetting Documentation 5.0\VIPsubsetStartPoint.xlsx
parDatabaseType – Specify the database type. For example, enter the following argument when working with SQLServer:
parDatabaseType=SQL Server
parReportFile – Specify the name and location to which your Subset Report file will be saved. Include the file name and .txt extension, not just a directory. For example:
parReportFile=C:\Users\VIP1\Documents\Subsetting Documentation 5.0\SubsetReport.txt
parSQLActionsPath – when running any Subset action, you must always specify the location of the SQLActions vip Enter the following arugment:
parSQLActionsPath=C:\VIPTDM\SubsetCloneAndMask\SQLActions.enc.vip
You can also specify any Optional parameters or Arguments at this point. See this Knowledge Base article for a full list of Arguments and example parameters.
See this Knowledge Base article for instructions on parameterising an action.
An example PREPENV action appears as follows in the VIP Server Controller:
Once you have parameterized the PREPENV Action, make sure your Configuration Spreadsheet, Subset Report and Log file are all shut. Next, click “Create File” and then click “Start” to run the action.
In the output dialogue, you will see something like following once the PREPENV Action is complete”:
The Log file will display something like the following after PREPENV is complete:
If you receive an error message in your output dialogue or log, please refer to this article to troubleshoot common issues. You can also run your Action on debug mode for a more detailed log.
Finally, check your Subset Report to check that the PREPENV has run successfully:
Run PREPENV from the Command Line
To run PREPENV from the Command Line, navigate to your Run Directory folder and open the re-usable Subset_2_Prep.cmd script.
Configure all mandatory parameters in the .cmd script:
- Database
- Flowdirectory
- Rundirectory
- Controlspreadsheet
- Outputdirectory
- Action
You can also specify optional parameters at this stage. Use this Knowledge Base article for instructions on setting parameters in your command script.
Make sure your Control Spreadsheet, the Subset Report, and any Log Files are closed.
Run the script.
Check your log file and Subset Report to make sure that the PREPENV completed without errors.
If you notice a mistake or error, you will need to Drop and Re-Register your Tables.
-
-
-
- IEnumerable to Data Reader
- Data Table to List
- Nested String List to Data Table
- List to Data Table
- IEnumerable to List
- List to IEnumerable
- Remove from List
- Exists in List
- Value Exists in Dictionary
- Key Exists in Dictionary
- Remove from Dictionary
- Get from Dictionary
- Clear Dictionary
- Add to Dictionary
- Clear List
- Add to List
- Show all articles ( 1 ) Collapse Articles
-
-
-
-
- Explanation of Remaining Sheets in the Control Spreadsheet (for reference only)
- The ForeignKeys Sheet - Specifying which Foreign Keys to read from the Source Database
- The Tables Sheet: Defining Metadata that will be read from the Source Database
- The ProcessModel sheet – Toggling Subset Rules
- Refining the Control Spreadsheet
- Overview of the Advanced Control Spreadsheet
- Introduction
-
- Drop both Primary and Foreign Keys (The composite DROPKEYS Action)
- Validate Both Primary and Foreign Keys (The composite ValidateKeys Action)
- Add Both Primary and Foreign Keys (The Composite ADDKEYS action)
- Drop Tables
- Truncate Data
- Delete Orphans
- Drop Primary Keys
- Drop Foreign Keys
- Validate that Foreign Keys are Unique
- Validate that Primary Keys are Unique
- Add Foreign Keys
- Add Primary Keys
- Overview of Post-Subset Actions
-
-
- Use Event Hooks to call VIP Flows
- Different Methods for Connecting to Source Databases
- PreProcess Variables and Parameters
- Using SQL Functions to query Databases and Using the Queries in Data Generation Functions
- Summary of the Process to Configure the Test Data Configuration sheet
- How the PreProcessVariables Table is used in the Configuration sheet
- Sample Commerce Configuration Sheet Examples
- Adding Event Hooks in Configuration sheet for custom functionality
- How to Configure the Synthetic Test Data Configuration Control Sheet
-
-
-
-
-
- The UI Recorder
- Test Modeller – Maintenance
- Test Modeller Core (Linux) Optional – Postgres LDAP
- Test Modeller Core (Linux) Optional – SSL Certificate Installation
- Test Modeller Core (Linux) Optional – Active Directory
- Test Modeller Core (Linux) Installation
- Test Modeller: Software Pre-requisites
- Test Modeller : Installation components
- Test Modeller : System requirements (Windows, Linux)
-
-
-
-
-
-
- Common Problems
- Extend Test Modeller (Advanced)
- Edit Code Templates (Advanced)
- Import existing framework / custom page objects (Advanced)
- Execute Tests (Java)
- Generate Automation Code
- Build a Model (Java)
- Scan an Existing Web App
- Configuration (Java)
- Prerequisites (Selenium Java)
- Welcome Selenium (Java)
-
-
-
-
- Generate Optimised Test Cases and Data into Excel
- Implement Naming Conventions
- Page Object Generation
- Intelligent Page Objects
- Customising Page Objects
- Import Custom Code Snippets
- Rule-Based Test Generation
- Trigger Automation Execution from within Test Modeller
- Automation Configuration
- Test Data Automation for Gherkin Specifications
-
-