VTS includes a number of settings that define certain aspects of how VTS operates.
Note: Micro Focus encourages you to ensure secure configuration and proper hardening of the VTS server—this is not provided by Micro Focus. You can use the useSSL configuration setting.
If you do not implement secure configuration and proper hardening, you may expose the system to increased security risks. You understand and agree to assume all associated risks and hold Micro Focus blameless for the same. It remains at all times solely the responsibility of the customer to assess their own regulatory and business requirements. Micro Focus does not represent or warrant that its products comply with any specific legal or regulatory standards applicable to the customer while conducting the customer's business.
Access the VTS configuration tool
These configuration settings are stored in the configure.json file that is saved with the standard JSON format.
You can use the VTS configuration tool to configure the VTS. From the Windows Start menu, go to, Micro Focus > Tools > Configure Virtual Table Server.
Alternatively, you can update the configure.json file itself. By default, this is located in C:\Program Files\Micro Focus\VTS\web.
Note: If you modify the configuration file to a non-valid format, or add comments to the file, the VTS Service will fail to start.
VTS configuration settings
The configure.json configuration file includes the following settings:
The stored path of the VTS database.
Default: C:/ProgramData/Micro Focus/VTS/db/data
The name of the VTS database. The default name is Default.
Recommended: Do not modify this setting.
The TCP port that is used for Admin UI access to VTS. This port is used by the VTS UI to read and modify data in the VTS table. The default value is 4000.
Note: The port used for Admin UI access must be different from the port used for Vuser script API access.
The default port that Vuser scripts use to access the VTS table using API functions. If you use the VTS UI to change the API access port, the new port number will override the default value.
Specifies whether or not API access to the VTS table should be enabled when the VTS Service service is started.
Enables the VTS diagnosis feature. If set to true, you can access the following URL to view logs, apis, and meta data:
When the data is changed by an API or by another Admin UI, the Admin UI automatically refreshes itself to show the updated data. This is the default behavior. If this is affecting the performance of the load test, set this key to false.
VTS supports multiple instances. Use this setting to configure the maximum number of instances that VTS should support.
When set to true, each column is automatically indexed.
When set to true, VTS will normalize non-strict CSV files when the rows do not have the same separators.
|users||When authentication=Basic, specify the list of users that are registered to access the VTS table from the VTS user interface.
Note: If multiple users are listed, insert a comma between each line in the list, as shown below:
For both Basic or NTLM authentication, you can assign the user roles: full-control administrator, or read-only user.
When authentication is set to Basic, and requireBasicAuthForAPI is set to true, the user name and password are required when accessing VTS data from the API level. The setting does not affect VTS admin UI.
|domain||When authentication is set to NTLM, specify the domain.|
|domaincontroller||When authentication is set to NTLM, specify the domaincontroller.|
Specifies whether or not HTTPS should be used to access the VTS table from the VTS user interface.
By default, useSSL is set to false.
To use SSL communication, set useSSL to true, and define the following properties:
Tip: Instead of copying the key files described above to the same folder as node.exe, you can specify an absolute path to specify the files in another location. For example,
Sets the VTS server language. You can set the following languages:
en, zh-cn, ja, ko, it, es, pt-br, fr, ru
Defines database settings.
VTS maintains a pool of connections, to avoid the resources wasted on TCP handshake and close, and to help restrict the concurrent connections to the database server.
Contains the settings for VTS's logging options.
level. Specifies the level of logging performed:
transports. Specifies certain output options for logging.