Can I keep config file, other than "Configs" folder for a LISA project?
Hi VikasDwivedi - I'm curious, what is the use case for wanting to keep a config file somewhere other than in the Configs folder for a project?
From how I understand things, DevTest Workstation and the command-line utilities are designed out-of-the-box to use the Configs folder for config files, and store any assets behind the scenes that may go with the file. I did a little checking, and pretty much everything in Workstation is tied into the Configs folder such as making a config file active (you can only make the file active if the file is in the Configs folder), staging test cases, or editing and adding files to MAR Info files. While you can make new folders and copy and paste config files to the folder, Workstation doesn't recognize those files as config files correctly because the system is tied into Configs folder (Workstation won't let you change the name of the folder because of the system dependencies on the folder being named, Configs). There may be some workaround to this, but from how I understand things, it looks to me you would have the most stable experience keeping your config files in the Configs folder.
I am trying to execute LISA test with the help of LISA invoke.
LISA invoke call is as below -
The requirement is to allow multiple users to invoke LISA test from a web page simultaneously.Different users may want to execute LISA test with different set of values for properties defined in the config file. These config files will be available in a shared network drive.
I want to allow users to pass his/her version of the config file with LISA invoke call .
Retrieving data ...