Thomas Moore admin
- Thomas Moore
- Last Active
- Admin, Staff
When you're using java in CTP Extension Tool scripts, you will need to make sure the classpath is set for the SOAtest/Virtualize instance that is connecting to CTP, and not CTP itself.
If you go to the API Testing page, click on the three dots on the right and create a folder on the server of your choice called "system_jars". Once the folder is created, click on it in the tree view and again click on the three dots on the right and choose upload file. Upload the jars that you wish to add to your classpath, and you should be ready to go.
Hope this helps!1
May I ask if we could take a step back and ask why you want to parameterize the filepath? One of the things that I immediately thought when I saw your question was wondering if you wanted to be able to change which excel sheet you were pointing to depending on the environment.
If this is the case, you can do this quite easily by using multiple datasources, a data group, and environments.
To do so, first you will want to create one excel datasource for each excel file you would be referencing. Then, create a single data group datasource and add each of the excel datasources in it. Once you have that, you can define the active datasource as a parameterized value, as shown in the screenshot below.
Finally, create a number of environments equal to the number of excel files you want to reference, and define the datasource parameterized value you defined above in each environment. In my case, I created a variable called "datasource" in the two environments, with the values of DS1 and DS2, one in each environment.
Now if I switch between the two environments, I get the values for each datasource respectively in my message client.
Let me know if this is the type of functionality you are looking for
Hope this helps!1
No problem I approved the original post, but when I saw that you added in the stuff in two separate posts, I deleted the original. No harm done!1
I am making this forum post to help out new users install Virtualize Community Edition on Windows, Linux, or Mac.
Windows (UI installation):
After downloading the installer linked from the initial email, execute the exe by double-clicking on the .exe file.
Click run on the popup that appears.
Choose your language for installation.
Click Next, then read through the End User License Agreement, then accept the agreement.
Select your installation directory, the default being
C:\Program Files\Parasfot\SOAtest & Virtualize\9.10
Choose Full installation. When only using Community Edition, the pydev option is not necessary.
Setup the location for the program's shortcuts, defaulted to
Parasoft\SOATest & Virtualize\9.10
If you wish, install the Root CA for https functional tests.
Note: This is only necessary for SOAtest functionality, not for Virtualize Community Edition.
If you wish, install a Desktop icon or quick launch icon.
Click install. Once the installation is finished, click Finish.
Mac/Linux (Terminal installation):
Open up your terminal and navigate into the Downloads folder.
Unpackage the download with
tar zxvf parasoft_soavirt_9.10.1_linux_x86_64.tar.gz
Run the installer with
Choose your installation language.
Enter in an installation location. The recommended installation location is
After the installation finishes, read through the additional information for starting up Virtualize from the command line. Once you have finished, press Enter.
Hope this helps!
The 11k hits per day is calculated by Virtualize. This number is incremented every time a Virtual Asset is invoked, and traffic passing through the proxy does not increment your hit count.
If you would like to know your current amount of hits on your Virtualize server, that number is shown once every 30 seconds in the console view if there has been a change. Additionally, you can double click on the Local machine node in the Virtualize Server view, and this will display your current number of hits as well.
Hope this helps!