Some additional thoughts about your question...
If this is the first time you're setting up a LoadTest run
you could be trying to do too many things too quickly.
Have you studied the basic material about doing loading?
And about DataSynthesis (values from a file into one script)?
And about how parameters are passed into a parametric script?
My concern is that you are attempting to do too large an experiment
at the first try...
I'll put some manual page references below...One suggestion
might be to have a web meeting to help you through this. But I think
it would be valuable to see how much material there is...
We can help you out but we do need a very careful explanation
of what you are trying to do.
Then we can outline a phased set of steps to go through, like
this:
record the test,
perfect the test as a singleton,
parameterize it and confirm that the parameters work,
add in environment variables that affect the entire scenario,
create the LoadTest plan of attack,
figure out which scripts will be run from where and how often,
make some small runs to make sure all the parts are in place,
then populate the files,
and make the final run.....
eValid can do all of that but in thinking about your description
we do have to go step by step...
Best Regards,
*************************************
*************************************
(1) To have one script run repetitively, after adjusting values of parameters
in your script, you can use the powerful eValid Data Synthesis capability
(this capability works in LoadTest runs also):
http://www.e-Valid.com/Products/Documentation.9/Generate/synthesize.data.html(2) There is a built-in capability to pre-specify values for parameters in
an eValid script, described in detail here:
http://www.e-Valid.com/Products/Documentation.9/Technical/environment.variables.html(3) The eValid string substitution facility -- used in both functional
testing AND in server load creation -- is described here:
http://www.e-Valid.com/Products/Documentation.9/Technical/strings.htmlHere's a diagram of this process:
http://www.e-Valid.com/Products/Documentation.9/Support/script.expansion.html(4) Here is a movie-like illustration of eValid doing a very basic, very
simplified LoadTest run:
http://www.e-Valid.com/Products/Documentation.9/Movies/SLB/movie.SLB.html (5) LoadTest Reference/Resource Pages...
Terminology:
http://www.e-Valid.com/Products/Documentation.9/Loading/load.terms.html Command line interface:
http://www.e-Valid.com/Products/Documentation.9/Technical/interface.html Machine adjustments:
http://www.e-Valid.com/Products/Documentation.9/Loading/machine.html Supplemental information:
http://www.e-Valid.com/Products/Documentation.9/Loading/supplemental.html Desk Top Lock/Unlock Advisory Comments
http://www.e-Valid.com/Products/Documentation.9/Loading/lock.html Recovery of CPU data from server:
http://www.e-Valid.com/Products/Documentation.9/Support/IIS.performance.data.html http://www.e-Valid.com/Products/Documentation.9/Support/LINUX.performance.data.html Making playbacks LoadTest safe:
http://www.e-Valid.com/Products/Documentation.9/Loading/loadtest.safe.html*************************************
*************************************