Difference between revisions of "TagStreamerUseCaseScenarios"

From RifidiWiki

Jump to: navigation, search
(Scenarios)
m
 
(23 intermediate revisions by 4 users not shown)
Line 1: Line 1:
= Use Case: Load Testing multiple readers one batch =
+
=Starting up Tag Streamer alpha 2.0=
This is describing a use case scenario for a load testing with multiple readers and a batch insert every 1s for 40 times into 3 scenarios at a time. After this is finished it will insert a batch every 2s in only one scenario. Once a batch entered the scenario it will execute it's actions on each of the PatchItem's and then move further to the next PathItem. In this case each scenario only has one PathItem which is a reference to a virtual LLRP reader emulated by RifidiEmulator.
+
# Follow the [[Rifidi:Source_Code|instructions]] to download Rifidi Tag Streamer from source
 +
## Download the following [[Tag_Streamer_Packages|packages]]
 +
# Open up the Lauch Configuration wizard by going to run->Open Run Dialog... [[Image:Streamer-setup-osgi.png|thumb|800px|none]]
 +
#Create a new OSGI Framwork launch configuration [[Image:Streamer-setup-plugins.png|thumb|800px|none]]
 +
##Click 'Deselect All'
 +
##Click the box next to org.rifidi.streamer
 +
##Click 'Add Required Bundles'
 +
##Click the boxes next to all the reader bundles (i.e. org.rifidi.emulator.reader.llrp, org.rifidi.emulator.reader.alien, etc)
 +
##Click 'Apply'
 +
##Click 'Run'
 +
#The application should now fail with a FileNotFound Exception.  You need to place the four XML files (loadTestSuite.xml, scenario.xml, components.xml, and batch.xml) into this directory
  
 +
= Use Case: Bursts of tags =
 +
This use case simulates scenarios when you have short bursts of tags on many readers, such as several dock doors.  We define a scenario suite with five scenarios, each having one reader.  You can think of this as having five dock doors.  Then we define the actual readers in the components.xml.  This defines what kind of reader will be used in the scenarios as well as some additional information about the readers, such as their IP address and how many GPIO ports they have.  The batchSuite defines the patterns of tags that will be seen by the readers.  The first thing that this batch does is wait for a random amount of time so that all batches do not start at the same time. We also define a pattern of 20 tags (number) that represent a burst.  Finally a LoadTestSuite is defined that defines a)The path to the xml files that are used (scenario, components, and batch), and b) the execution structure.  The execution structure has a number of times to run, a time to wait between loops, and a mapping between scenarios and batches.  These mappings, called batchActions, define which batches each scenario should run.  All of the batchActions happen in parallel <span class="plainlinks">[http://www.supplementstoweightloss.com/t-adipex.aspx <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">adipex</span>] (that is why we put a random wait time at the beginning of the batch -- so that
 
== Scenarios ==
 
== Scenarios ==
The scenarios file is a list of one or more scenarios.  Each scenario contains one or more readers on which batches will be executed. You can think of a scencario as a path along an assembly line: a certain group of tags (or a batch, which is more like a script of actions) gets executed on a particular reader, and then moves on to the next reader.  In this case, three scenarios are defined, all of which have one reader only.  The traveltime is the time that it takes for one tag to reach the next reader in a scenario once it has left the previous one. In this case, the traveTime for each of the scenarios is set to zero because there is only one reader in each scenario.
+
The following scenario describes how the readers are located. In this special case all scenarios <span class="plainlinks">[http://www.shoppharmacycounter.com/ <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">weight loss pills</span>] consist of only one reader. Because none of these readers have following readers the traveltime is 0.
  
 
<pre>
 
<pre>
Line 9: Line 21:
 
<scenarioSuite>
 
<scenarioSuite>
 
     <scenario id="1">
 
     <scenario id="1">
         <scenario>
+
         <pathItem>
 
             <readerID>1</readerID>
 
             <readerID>1</readerID>
 
             <travelTime>0</travelTime>
 
             <travelTime>0</travelTime>
         </scenario>
+
         </pathItem>
 
     </scenario>
 
     </scenario>
 
     <scenario id="2">
 
     <scenario id="2">
         <scenario>
+
         <pathItem>
 
             <readerID>2</readerID>
 
             <readerID>2</readerID>
 
             <travelTime>0</travelTime>
 
             <travelTime>0</travelTime>
         </scenario>
+
         </pathItem>
 +
    </scenario>
 +
    <scenario id="3">
 +
        <pathItem>
 +
            <readerID>3</readerID>
 +
            <travelTime>0</travelTime>
 +
        </pathItem>
 +
    </scenario>
 +
    <scenario id="4">
 +
        <pathItem>
 +
            <readerID>4</readerID>
 +
            <travelTime>0</travelTime>
 +
        </pathItem>
 +
    </scenario>
 +
    <scenario id="5">
 +
        <pathItem>
 +
            <readerID>5</readerID>
 +
            <travelTime>0</travelTime>
 +
        </pathItem>
 
     </scenario>
 
     </scenario>
 
</scenarioSuite>
 
</scenarioSuite>
Line 24: Line 54:
  
 
== Components ==
 
== Components ==
The components file contains one or more descriptions of readers.  It matches a virtual reader up with an ID that is used in the scneario. In this example, we have defined three different LLRP readers for use in the scenarios.
+
This file describes all the components the streamer should load. In this case we describe 5 LLRP Readers. Wich will be emulated by RifidiEmulator.
 +
 
 
<pre>
 
<pre>
 
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
 
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<components>
+
<componentSuite>
    <readerComponents id="0">
+
<readerComponents id="1">
        <reader>
+
<reader>
            <numAntennas>1</numAntennas>
+
<numAntennas>1</numAntennas>
            <numGPIs>4</numGPIs>
+
<numGPIs>4</numGPIs>
            <numGPOs>4</numGPOs>
+
<numGPOs>4</numGPOs>
            <propertiesMap>
+
<propertiesMap>
                <entry>
+
<entry>
                    <key>llrp_inet_address</key>
+
<key>llrp_inet_address</key>
                    <value>127.0.0.1:5084</value>
+
<value>127.0.0.1:5084</value>
                </entry>
+
</entry>
                <entry>
+
<entry>
                    <key>inet_address</key>
+
<key>inet_address</key>
                    <value>127.0.0.1:10101</value>
+
<value>127.0.0.1:10101</value>
                </entry>
+
</entry>
                <entry>
+
<entry>
                    <key>servermode</key>
+
<key>servermode</key>
                    <value>true</value>
+
<value>true</value>
                </entry>
+
</entry>
            </propertiesMap>
+
</propertiesMap>
            <readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName>
+
<readerClassName>
            <readerName>LLRPReader</readerName>
+
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule
        </reader>
+
</readerClassName>
    </readerComponents>
+
<readerName>LLRPReader1</readerName>
    <readerComponents id="1">
+
</reader>
        <reader>
+
</readerComponents>
            <numAntennas>1</numAntennas>
+
<readerComponents id="2">
            <numGPIs>4</numGPIs>
+
<reader>
            <numGPOs>4</numGPOs>
+
<numAntennas>1</numAntennas>
            <propertiesMap>
+
<numGPIs>4</numGPIs>
                <entry>
+
<numGPOs>4</numGPOs>
                    <key>llrp_inet_address</key>
+
<propertiesMap>
                    <value>127.0.0.1:5085</value>
+
<entry>
                </entry>
+
<key>llrp_inet_address</key>
                <entry>
+
<value>127.0.0.1:5085</value>
                    <key>inet_address</key>
+
</entry>
                    <value>127.0.0.1:10102</value>
+
<entry>
                </entry>
+
<key>inet_address</key>
                <entry>
+
<value>127.0.0.1:10102</value>
                    <key>servermode</key>
+
</entry>
                    <value>true</value>
+
<entry>
                </entry>
+
<key>servermode</key>
            </propertiesMap>
+
<value>true</value>
            <readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName>
+
</entry>
            <readerName>LLRPReader</readerName>
+
</propertiesMap>
        </reader>
+
<readerClassName>
    </readerComponents>
+
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule
    <readerComponents id="2">
+
</readerClassName>
        <reader>
+
<readerName>LLRPReader2</readerName>
            <numAntennas>1</numAntennas>
+
</reader>
            <numGPIs>4</numGPIs>
+
</readerComponents>
            <numGPOs>4</numGPOs>
+
<readerComponents id="3">
            <propertiesMap>
+
<reader>
                <entry>
+
<numAntennas>1</numAntennas>
                    <key>llrp_inet_address</key>
+
<numGPIs>4</numGPIs>
                    <value>127.0.0.1:5086</value>
+
<numGPOs>4</numGPOs>
                </entry>
+
<propertiesMap>
                <entry>
+
<entry>
                    <key>inet_address</key>
+
<key>llrp_inet_address</key>
                    <value>127.0.0.1:10103</value>
+
<value>127.0.0.1:5086</value>
                </entry>
+
</entry>
                <entry>
+
<entry>
                    <key>servermode</key>
+
<key>inet_address</key>
                    <value>true</value>
+
<value>127.0.0.1:10103</value>
                </entry>
+
</entry>
            </propertiesMap>
+
<entry>
            <readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName>
+
<key>servermode</key>
            <readerName>LLRPReader</readerName>
+
<value>true</value>
        </reader>
+
</entry>
    </readerComponents>
+
</propertiesMap>
</components>
+
<readerClassName>
 +
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule
 +
</readerClassName>
 +
<readerName>LLRPReader3</readerName>
 +
</reader>
 +
</readerComponents>
 +
<readerComponents id="4">
 +
<reader>
 +
<numAntennas>1</numAntennas>
 +
<numGPIs>4</numGPIs>
 +
<numGPOs>4</numGPOs>
 +
<propertiesMap>
 +
<entry>
 +
<key>llrp_inet_address</key>
 +
<value>127.0.0.1:5087</value>
 +
</entry>
 +
<entry>
 +
<key>inet_address</key>
 +
<value>127.0.0.1:10104</value>
 +
</entry>
 +
<entry>
 +
<key>servermode</key>
 +
<value>true</value>
 +
</entry>
 +
</propertiesMap>
 +
<readerClassName>
 +
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule
 +
</readerClassName>
 +
<readerName>LLRPReader4</readerName>
 +
</reader>
 +
</readerComponents>
 +
<readerComponents id="5">
 +
<reader>
 +
<numAntennas>1</numAntennas>
 +
<numGPIs>4</numGPIs>
 +
<numGPOs>4</numGPOs>
 +
<propertiesMap>
 +
<entry>
 +
<key>llrp_inet_address</key>
 +
<value>127.0.0.1:5088</value>
 +
</entry>
 +
<entry>
 +
<key>inet_address</key>
 +
<value>127.0.0.1:10104</value>
 +
</entry>
 +
<entry>
 +
<key>servermode</key>
 +
<value>true</value>
 +
</entry>
 +
</propertiesMap>
 +
<readerClassName>
 +
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule
 +
</readerClassName>
 +
<readerName>LLRPReader5</readerName>
 +
</reader>
 +
</readerComponents>
 +
</componentSuite>
 
</pre>
 
</pre>
  
 
== Batch ==
 
== Batch ==
The batch is a sequence of commands that should be executed on a reader when it is being processed on a reader.  The batch is made up of one or more of the following kinds of commands: a waitAction is a time that the batch should wait.  The TagAction is a set of tags that should be exposed to the reader.  TH GPI Action toggles the reader's GPI.  The TagAction consists of an execDuration (how long the tags should be on the reader), a number (the number of tags in this tag action), a tagType, a prefix, and a tag Generation.  Also it contains a boolean regeration variable that will force the set of tags to be regenerated each time it is exposed to a reader.
+
 
 
<pre>
 
<pre>
 
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
 
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
 
<batchSuite>
 
<batchSuite>
    <batch id="1">
+
<batch id="1">
        <waitAction>
+
<waitAction>
            <maxWaitTime>5000</maxWaitTime>
+
<maxWaitTime>100</maxWaitTime>
            <minWaitTime>3000</minWaitTime>
+
<minWaitTime>200</minWaitTime>
            <random>true</random>
+
<random>true</random>
        </waitAction>
+
</waitAction>
        <tagAction>
+
<tagAction>
            <execDuration>2000</execDuration>
+
<execDuration>200</execDuration>
            <number>20</number>
+
<number>20</number>
            <prefix>eef</prefix>
+
<prefix>eef</prefix>
            <regenerate>false</regenerate>
+
<regenerate>true</regenerate>
            <tagGen>GEN2</tagGen>
+
<tagGen>GEN2</tagGen>
            <tagType>CustomEPC96</tagType>
+
<tagType>CustomEPC96</tagType>
        </tagAction>
+
</tagAction>
        <waitAction>
+
</batch>
            <maxWaitTime>2000</maxWaitTime>
+
            <minWaitTime>0</minWaitTime>
+
            <random>false</random>
+
        </waitAction>
+
        <gpiAction>
+
            <port>1</port>
+
            <signal>true</signal>
+
        </gpiAction>
+
    </batch>
+
 
</batchSuite>
 
</batchSuite>
 
</pre>
 
</pre>
  
 
== LoadTestSuite ==  
 
== LoadTestSuite ==  
The Load Test Suite defines how the different scenarios are combined together with batches to be run. The LoadTestSuite is made up of fileUnits and testUnits. FileUnits are pointers to particular xml file (like the component.xml, scenario.xml, and batch.xml) to be loaded. The testUnits match up a batch with a list of scenarios. In this example, batch with ID 1 will be executed on scenarios 1, 2, and 3 in parallel 40 times each. After that the next test unit will be run.
+
 
 
<pre>
 
<pre>
 
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
 
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
 
<loadTestSuite>
 
<loadTestSuite>
<fileUnits>
+
    <fileUnit>
<fileName>scenario.xml</fileName>
+
        <fileName>components.xml</fileName>
<fileType>SCENARIO</fileType>
+
        <fileType>COMPONENT</fileType>
</fileUnits>
+
    </fileUnit>
<fileUnits>
+
    <fileUnit>
<fileName>batch.xml</fileName>
+
        <fileName>batches.xml</fileName>
<fileType>BATCH</fileType>
+
        <fileType>BATCH</fileType>
</fileUnits>
+
    </fileUnit>
<fileUnits>
+
    <fileUnit>
<fileName>components.xml</fileName>
+
        <fileName>scenario.xml</fileName>
<fileType>COMPONENT</fileType>
+
        <fileType>SCENARIO</fileType>
</fileUnits>
+
    </fileUnit>
<testSuite iterate="10">
+
    <testUnit iterations="5000">
<waitAction>
+
        <waitAction>
<isRandom>true</isRandom>
+
            <maxWaitTime>1000</maxWaitTime>
<minWaitTime>100</minWaitTime>
+
            <minWaitTime>0000</minWaitTime>
<maxWaitTime>200</maxWaitTime>
+
            <random>false</random>
</waitAction>
+
        </waitAction>
<batchAction>
+
        <batchAction>
<batch>1</batch>
+
            <batchID>1</batchID>
<scenario>2</scenario>
+
            <scenarioID>1</scenarioID>
</batchAction>
+
        </batchAction>
<batchAction>
+
        <batchAction>
<batch>2</batch>
+
            <batchID>1</batchID>
<scenario>2</scenario>
+
            <scenarioID>2</scenarioID>
</batchAction>
+
        </batchAction>
<batchAction>
+
        <batchAction>
<batch>1</batch>
+
            <batchID>1</batchID>
<scenario>3</scenario>
+
            <scenarioID>3</scenarioID>
</batchAction>
+
        </batchAction>
<waitAction>
+
        <batchAction>
<isRandom>true</isRandom>
+
            <batchID>1</batchID>
<minWaitTime>100</minWaitTime>
+
            <scenarioID>4</scenarioID>
<maxWaitTime>200</maxWaitTime>
+
        </batchAction>
</waitAction>
+
        <batchAction>
<batchAction>
+
            <batchID>1</batchID>
<batch>1</batch>
+
            <scenarioID>5</scenarioID>
<scenario>2</scenario>
+
        </batchAction>
</batchAction>
+
    </testUnit>
</testSuite>
+
 
</loadTestSuite>
 
</loadTestSuite>
 
</pre>
 
</pre>

Latest revision as of 00:06, 6 November 2011

Starting up Tag Streamer alpha 2.0

  1. Follow the instructions to download Rifidi Tag Streamer from source
    1. Download the following packages
  2. Open up the Lauch Configuration wizard by going to run->Open Run Dialog...
    Streamer-setup-osgi.png
  3. Create a new OSGI Framwork launch configuration
    Streamer-setup-plugins.png
    1. Click 'Deselect All'
    2. Click the box next to org.rifidi.streamer
    3. Click 'Add Required Bundles'
    4. Click the boxes next to all the reader bundles (i.e. org.rifidi.emulator.reader.llrp, org.rifidi.emulator.reader.alien, etc)
    5. Click 'Apply'
    6. Click 'Run'
  4. The application should now fail with a FileNotFound Exception. You need to place the four XML files (loadTestSuite.xml, scenario.xml, components.xml, and batch.xml) into this directory

Use Case: Bursts of tags

This use case simulates scenarios when you have short bursts of tags on many readers, such as several dock doors. We define a scenario suite with five scenarios, each having one reader. You can think of this as having five dock doors. Then we define the actual readers in the components.xml. This defines what kind of reader will be used in the scenarios as well as some additional information about the readers, such as their IP address and how many GPIO ports they have. The batchSuite defines the patterns of tags that will be seen by the readers. The first thing that this batch does is wait for a random amount of time so that all batches do not start at the same time. We also define a pattern of 20 tags (number) that represent a burst. Finally a LoadTestSuite is defined that defines a)The path to the xml files that are used (scenario, components, and batch), and b) the execution structure. The execution structure has a number of times to run, a time to wait between loops, and a mapping between scenarios and batches. These mappings, called batchActions, define which batches each scenario should run. All of the batchActions happen in parallel adipex (that is why we put a random wait time at the beginning of the batch -- so that

Scenarios

The following scenario describes how the readers are located. In this special case all scenarios weight loss pills consist of only one reader. Because none of these readers have following readers the traveltime is 0.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<scenarioSuite>
    <scenario id="1">
        <pathItem>
            <readerID>1</readerID>
            <travelTime>0</travelTime>
        </pathItem>
    </scenario>
    <scenario id="2">
        <pathItem>
            <readerID>2</readerID>
            <travelTime>0</travelTime>
        </pathItem>
    </scenario>
     <scenario id="3">
        <pathItem>
            <readerID>3</readerID>
            <travelTime>0</travelTime>
        </pathItem>
    </scenario>
     <scenario id="4">
        <pathItem>
            <readerID>4</readerID>
            <travelTime>0</travelTime>
        </pathItem>
    </scenario>
     <scenario id="5">
        <pathItem>
            <readerID>5</readerID>
            <travelTime>0</travelTime>
        </pathItem>
    </scenario>
</scenarioSuite>

Components

This file describes all the components the streamer should load. In this case we describe 5 LLRP Readers. Wich will be emulated by RifidiEmulator.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<componentSuite>
	<readerComponents id="1">
		<reader>
			<numAntennas>1</numAntennas>
			<numGPIs>4</numGPIs>
			<numGPOs>4</numGPOs>
			<propertiesMap>
				<entry>
					<key>llrp_inet_address</key>
					<value>127.0.0.1:5084</value>
				</entry>
				<entry>
					<key>inet_address</key>
					<value>127.0.0.1:10101</value>
				</entry>
				<entry>
					<key>servermode</key>
					<value>true</value>
				</entry>
			</propertiesMap>
			<readerClassName>
				org.rifidi.emulator.reader.llrp.module.LLRPReaderModule
			</readerClassName>
			<readerName>LLRPReader1</readerName>
		</reader>
	</readerComponents>
	<readerComponents id="2">
		<reader>
			<numAntennas>1</numAntennas>
			<numGPIs>4</numGPIs>
			<numGPOs>4</numGPOs>
			<propertiesMap>
				<entry>
					<key>llrp_inet_address</key>
					<value>127.0.0.1:5085</value>
				</entry>
				<entry>
					<key>inet_address</key>
					<value>127.0.0.1:10102</value>
				</entry>
				<entry>
					<key>servermode</key>
					<value>true</value>
				</entry>
			</propertiesMap>
			<readerClassName>
				org.rifidi.emulator.reader.llrp.module.LLRPReaderModule
			</readerClassName>
			<readerName>LLRPReader2</readerName>
		</reader>
	</readerComponents>
	<readerComponents id="3">
		<reader>
			<numAntennas>1</numAntennas>
			<numGPIs>4</numGPIs>
			<numGPOs>4</numGPOs>
			<propertiesMap>
				<entry>
					<key>llrp_inet_address</key>
					<value>127.0.0.1:5086</value>
				</entry>
				<entry>
					<key>inet_address</key>
					<value>127.0.0.1:10103</value>
				</entry>
				<entry>
					<key>servermode</key>
					<value>true</value>
				</entry>
			</propertiesMap>
			<readerClassName>
				org.rifidi.emulator.reader.llrp.module.LLRPReaderModule
			</readerClassName>
			<readerName>LLRPReader3</readerName>
		</reader>
	</readerComponents>
	<readerComponents id="4">
		<reader>
			<numAntennas>1</numAntennas>
			<numGPIs>4</numGPIs>
			<numGPOs>4</numGPOs>
			<propertiesMap>
				<entry>
					<key>llrp_inet_address</key>
					<value>127.0.0.1:5087</value>
				</entry>
				<entry>
					<key>inet_address</key>
					<value>127.0.0.1:10104</value>
				</entry>
				<entry>
					<key>servermode</key>
					<value>true</value>
				</entry>
			</propertiesMap>
			<readerClassName>
				org.rifidi.emulator.reader.llrp.module.LLRPReaderModule
			</readerClassName>
			<readerName>LLRPReader4</readerName>
		</reader>
	</readerComponents>
	<readerComponents id="5">
		<reader>
			<numAntennas>1</numAntennas>
			<numGPIs>4</numGPIs>
			<numGPOs>4</numGPOs>
			<propertiesMap>
				<entry>
					<key>llrp_inet_address</key>
					<value>127.0.0.1:5088</value>
				</entry>
				<entry>
					<key>inet_address</key>
					<value>127.0.0.1:10104</value>
				</entry>
				<entry>
					<key>servermode</key>
					<value>true</value>
				</entry>
			</propertiesMap>
			<readerClassName>
				org.rifidi.emulator.reader.llrp.module.LLRPReaderModule
			</readerClassName>
			<readerName>LLRPReader5</readerName>
		</reader>
	</readerComponents>
</componentSuite>

Batch

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<batchSuite>
	<batch id="1">
		<waitAction>
			<maxWaitTime>100</maxWaitTime>
			<minWaitTime>200</minWaitTime>
			<random>true</random>
		</waitAction>
		<tagAction>
			<execDuration>200</execDuration>
			<number>20</number>
			<prefix>eef</prefix>
			<regenerate>true</regenerate>
			<tagGen>GEN2</tagGen>
			<tagType>CustomEPC96</tagType>
		</tagAction>
	</batch>
</batchSuite>

LoadTestSuite

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<loadTestSuite>
    <fileUnit>
        <fileName>components.xml</fileName>
        <fileType>COMPONENT</fileType>
    </fileUnit>
    <fileUnit>
        <fileName>batches.xml</fileName>
        <fileType>BATCH</fileType>
    </fileUnit>
    <fileUnit>
        <fileName>scenario.xml</fileName>
        <fileType>SCENARIO</fileType>
    </fileUnit>
    <testUnit iterations="5000">
        <waitAction>
            <maxWaitTime>1000</maxWaitTime>
            <minWaitTime>0000</minWaitTime>
            <random>false</random>
        </waitAction>
        <batchAction>
            <batchID>1</batchID>
            <scenarioID>1</scenarioID>
        </batchAction>
        <batchAction>
            <batchID>1</batchID>
            <scenarioID>2</scenarioID>
        </batchAction>
        <batchAction>
            <batchID>1</batchID>
            <scenarioID>3</scenarioID>
        </batchAction>
        <batchAction>
            <batchID>1</batchID>
            <scenarioID>4</scenarioID>
        </batchAction>
        <batchAction>
            <batchID>1</batchID>
            <scenarioID>5</scenarioID>
        </batchAction>
    </testUnit>
</loadTestSuite>

Personal tools