Edit Login VSI workload and test it without having to restart test scenario

(Short version)

How to on the fly edit VSI workload without having to rerun test:
-Start a one user test with the desired workload; make sure in the Start Test wizard to set test duration to 9999
-Once the test starts on the target kill the vsi.exe in the tray (right click it and do exit)
-On the target open the file at, in a text editor <VSI share>\vsi_logfiles\<name of your currently running test>\<.txt file for the workload>
-Edit and save the workload how you want to
-On the target execute the file: <VSI share>\vsi_binaries\target\logon.cmd
-This will kick the new workload off now
-Continue making edits to the workload if you need to
-Once done editing the workload to your liking then copy the workload from <VSI share>\vsi_logfiles\<name of your currently running test>\<.txt file for the workload> to <VSI share>\vsi_workloads\custom workloads\<.txt file for the workload>
-Before starting new test revert to desired test scenario -- update the user amount and test duration to desired

-------

(Long version)

You will find early on when dealing with Login VSI that being able to repeatedly run a workload without going through the whole test setup over and over is desirable. How is this done?

Normally when you execute a Login VSI test several things happen that we are interested in.

1. A %testname% directory is created under VSIShare\_VSI_Logfiles\
2. A file is created at the root of the VSI Share named !!!_%testname%.IsActiveTest
3. Your command line is sent to the launcher and the session is executed.

For our needs we start the process as we normally would. This way all the items and actions we expect to happen are taken care of by Login VSI. Along the way though we just need to make a few tweaks.

1. While working with your workload I normally put what I am working on in segment 1 if I have multiple segments. This way I can easily run what I am interested in right away. Another method is to develop segments as individual workloads, refine them one by one then combine them for a multi segment workload. This method will also allow you to use mash ups of segments as workloads. 
2. Once you are ready to test your workload setup a test for a single user.
3. When setting up your test you are given the option of how long you want the test to run after the last user has logged on. Normally this would be set to something relevant for the test scenario. For our needs we want this time to be way out in the future. This will keep the test active for a long period of time. I normally use 9999 minutes. If you do not do this your test will time out sooner and you will have to repeat the test setup before continuing.
4. Kick off the test and watch your results from the Launcher. I normally stop the execution of the workload on the target and log the user off after I see what I needed to see.
5. Within the Login VSI Management console grab your command line from under “Connection Configuration” on your “Connection”.
6. From the Launcher open a blank text document to keep notes in. Copy your command line to this document. Now go through the command line and replace the items contained within “{…}” with their actual values. 
7. To execute another session open a command prompt with administrative privileges and execute your updated command line. The test should run as expected. Simply repeat this process as you work through your workload. The Launcher process does not need to be running. 
   • One the configurations of workload segment execution will distribute users to different segments. This is default behavior. User1 to Segment 1, User2 to Segment 2, etc… When testing a workload this can have an undesirable affects. To consistently get your user to start at the segment you want it to you simply delete the “Monitor” and “Results” folders from under  “VSIShare\_VSI_Logfiles\%testname%”
   • As you test and repeat this process you will need to update your workload. Keep in mind when running an active test like this your workload exists in VSIShare\_VSI_Logfiles\%testname%\%workloadname% and not in the default location of VSIShare\_VSI_Workloads\Custom Workloads\.  Update the workload VSIShare\_VSI_Logfiles\%testname%\%workloadname%  and when you have completed your changes copy the workload back to the default location of VSIShare\_VSI_Workloads\Custom Workloads\