http://wiki.rifidi.net/api.php?action=feedcontributions&feedformat=atom&user=AndreasRifidiWiki - User contributions [en]2026-06-03T16:28:12ZUser contributionsMediaWiki 1.23.1http://wiki.rifidi.net/index.php/Development_and_Release_ProcessDevelopment and Release Process2009-03-31T12:37:05Z<p>Andreas: </p>
<hr />
<div>This document describes the development and release processes for the products in the Rifidi Suite as well as various conventions that developers should be following. This document is intended for developers who are fairly familiar with the Rifidi code base, especially with eclipse and OSGi concepts.<br />
=Goals=<br />
# Standardize the development and release processes for Rifidi Developers<br />
# Enable a relatively lightweight release process that is able to be extended later by a fully automatic build tool like maven<br />
# Define a common set of conventions to use when checking in, checking out, and tagging code.<br />
<br />
This document is not intended to be a "how to" guide for eclipse, but rather to define some common operating procedures around how code is developed and released in the Rifidi project<br />
<br />
=Concepts=<br />
==Target Platforms==<br />
===About Target Platforms===<br />
A target platform is the set of base plugins that your application depends on. Normally when you build a project in eclipse that uses eclipse functionality (SWT, JFace, etc), eclipse gets that functionality from the plugins and features folder located in you eclipse installation. Therefore it is using your eclipse base installation as your target platform. However, it is possible to define your own target platform for the application you are building rather than relying on the default one. Doing this is useful for several reasons<br />
# It creates a separation between the plugins you use in your developing environment and the plugins used by your application. This means that you can, for example, upgrade the eclipse you use as your IDE without upgrading the plugins used by your application. Also, you can add plugins to your application without using them in your IDE. For example suppose you want to use the GEF bundles in your application, but you don't want them inside your eclipse development environment.<br />
# A closely related advantage is that you can limit the plugins that are available to your application. If you use the base eclipse installation as your target platform, all of the plugins are available to your application. This makes it easy for application developers to simply add dependencies as they like. However, because an added dependency often means changes to other things, such as build processes, adding bundle dependencies should require some deliberation. Having a target platform simply makes bundle dependencies more explicit.<br />
# It is possible to place more than just eclipse base plugins in the custom target platform. You can put bundles in there that you have built that are required for you application. This means that you could put, for example, tagged, stable versions of all of the plugins in your application in your target platform. Then when you need to modify a plugin, you can check out the source code from svn. Because eclipse will look in your workspace before it looks in your target platform, it will find that plugin first. This means developers only have to check out code for bundles that they want to modify, which forces him to think about the code that he wants to write. It also means that, because the code in the target platform is tagged and stable, that if one developer checks in code with a change in it that breaks another plugin, that other developers can continue developing with the stable bundles in the target platform.<br />
===Target Platforms in Rifidi===<br />
Each major Rifidi project in the Rifidi suite should have its own target platform. For example, there is a target platform called <code>org.rifidi.emulator.target</code>. There should be a directory in the target platform called <code>rifidi</code> where all the bundle binaries that are required for that particular project. In addition there are various target platforms used for deploying products, such as <code>org.rifidi.rcp.target</code>.<br />
<br />
==Bundle Versioning==<br />
All bundles in OSGi have version numbers, with the following form 1.2.3, where 1 is the major version, 2 is the minor version, and 3 is the point version. The Rifidi project uses the following conventions:<br />
# The '''major''' version should be increased only if there is a major API change for the bundle. A major version change usually involve a change that would break another plugin, for example, changing a method signature. A good rule of thumb is that if bundle X depends on bundle Y and bundle X was modified as a result of the changes to bundle Y, then bundle Y had a major API change. For example, suppose bundle Y has a method called <code>foo()</code>. Suppose bundle X, for some reason, needs to pass in a string to <code>foo()</code>. So you modify <code>foo()</code> to become <code>foo(String string)</code>. This was a major change in bundle Y.<br />
# The '''minor''' version should be increased if there is a minor API change. A minor API change is something that would not break existing compatibility with dependent bundles. For example, adding a method signature to a class, or adding more functionality to the bundle in the form of classes is a minor API change. The key difference between a minor and a major API change is that a minor API change will not cause other bundles that depend on it to break.<br />
# The '''point''' version should be increased for small internal changes and bug fixes. These changes do not involve the bundle's API.<br />
<br />
Note that it is not necessary to change the version numbers any time you submit. It is only necessary to modify the version numbers if the changes are relatively well tested and stable. For example, you might want to make some changes then submit the changes back to the trunk for another developer to look at, test, or modify. ''If you don't expect to make any further changes to the code, then you should modify then version number''<br />
<br />
==Dependencies==<br />
In OSGi there are two ways of specifying dependencies. <br />
#'''Require-Bundle''' should be used for dependencies to bundles that contain code which is written for the Rifidi project. Usually, this is anything that begins with <code>org.rifidi.*</code>.<br />
#'''Import-Package''' should be used for for dependencies to bundles that do not contain code that is maintained by the Rifidi project, for example, to third party libraries such as log4j, cajo, or eclipse base plugins such as SWT or GEF. It is also possible to find certain third party libraries that have already been made into a plugin at the eclipse [http://www.eclipse.org/orbit/overview.php eclipse orbit project]. <br />
<br />
The advantage to using Import-Package over Require-Bundle is that Import-Package is more flexible. The plugin is more flexible because it could use any loaded OSGi bundle that exposes that particular plugin with the given version constraints. In addition, because importing packages is more granular than requiring bundles, it makes the developer think a little more about the dependencies his is using.<br />
<br />
In both Require-Bundle and Import-Package dependencies, the minimum version ''must'' be specified. It is also recommended that the maximum version be specified as well. This is because it is possible for more than one bundle with the same name but different versions to be loaded by OSGi during runtime. So if an incorrect version of a bundle is already loaded, but the bundle that requires that bundle does not specify the version it needs, bad things might happen. <br />
<br />
A good way to specify versions is to have the minimum version be inclusive and the maximum version be exclusive. For example, if the minimum version is set to 2.2.0 inclusive and the maximum version is 2.3.0 exclusive, then any version starting with 2.2 is acceptable. This makes sense, because we have adopted a versioning scheme where the minor version number signifies a minor API change.<br />
<br />
==SVN Structure==<br />
There are four repositories used in Rifidi:<br />
* <code>rep-external</code> - main repository for Rifidi development<br />
* <code>rep-internal</code> - repository to hold code that is necessary, but that should not be released<br />
* <code>rep-edge</code><br />
* <code>sandbox</code> - repository to hold projects for playing around with<br />
<br />
<code>rep-external</code> and <code>rep-edge</code> are the main repositories for Rifidi development. They have the following structure:<br />
<br />
*'''org.rifidi.binary'''<br />
*: A project containing all the bundles as binaries for rifidi. It is used so that you don't have to check out the code when developing or releasing<br />
* '''readme''' <br />
*:a project that contains a text file that describes what all the bundles in trunk are used for<br />
* '''rifidi'''<br />
*: The code for the Rifidi project<br />
** '''branches'''<br />
*: If a developer want to add a major feature that requires alot of time, and he wants to check the code into the svn before he is ready to integrate the code back into the trunk, he can check the code into the branches directory<br />
** '''tags'''<br />
**: When a stable version of a bundle is reached, the code should be placed in a sub directory that has the name of the bundle's version. See [[Development and Release Process#Tags| Tags]] for a description of when to create a new tag<br />
*** '''org.rifidi.bundle.a'''<br />
**** 1.0.0 - contains eclipse project<br />
**** 1.1.0 - contains eclipse project<br />
**** 2.0.0 - contains eclipse project<br />
*** '''org.rifidi.bundle.b'''<br />
**** 1.0.0 - contains eclipse project<br />
** '''trunk'''<br />
**: The trunk contains the latest code for each bundle. It might be unstable. All changes to code should be made to the bundles located in the trunk<br />
*** org.rifidi.bundle.a - contains eclipse project<br />
*** org.rifidi.bundle.b - contains eclipse project<br />
<br />
==Tags==<br />
The purpose of tagging a bundle is to save the code at a stable point so that future changes can be reversed if they introduce a bug that older versions did not have. A new tag ''must'' be created in svn when either the major or the minor version number of the plugin is incremented. It is not required to create a new tag when the point version number is incremented, but it is ok to do so.<br />
<br />
==Product File==<br />
A product file defines the required plugins for a particular project. It is used to build the project. It is important to keep this file updated as new plugins are added or old ones are removed.<br />
<br />
=Processes=<br />
This section defines a few procedures that should be followed when developing code for the Rifidi project<br />
==Setting up a development environment==<br />
# Download the target platform for the project you are working with. For example, if you are developing a plugin for emulator, you would download the target platform for emulator<br />
# Download <code>org.rifidi.binary</code><br />
# Download any bundles that you need to modify. For example, if you are making changes to the alien reader, download <code>org.rifidi.emulator.reader.alien</code><br />
# Set the target platform as the target platform for the workspace<br />
# Clean the workspace<br />
<br />
==Modifying an Existing Bundle==<br />
Suppose you have modified an existing bundle and the changes are relatively stable and tested, and you are ready to integrate them back in with the rest of the project.<br />
<br />
# If the changes you have made require a version change make sure that is done<br />
# If you had to change the major or the minor version number, create a new svn tag for the plugin.<br />
# Export the bundle as a binary bundle using the export wizard on the Manifest.MF file for the plugin<br />
# Add the bundle to <code>org.rifidi.binary</code><br />
# Submit bundle changes and target platform changes back to trunk.<br />
<br />
If you have made changes to a bundle but are not ready to integrate them back with the rest of the project, you can do one of two things:<br />
# Submit them back to the trunk, but don't change the version numbers. This is ok to do because everyone else should be using tagged stable bundles in the target platform.<br />
# Create a folder in the branches directory and put it there. Only do this if multiple developers are modifying the same plugin at the same time.<br />
<br />
==Creating a new Bundle==<br />
To create a new bundle called <code>org.rifidi.xyz</code>:<br />
# Create a new plugin project with the name <code>org.rifidi.xyz</code><br />
# In the Manifest.MF file<br />
## Add 'Pramari, LLC' as the provider<br />
## Give the bundle a name such as 'Rifidi xyz'. It is important that the first word is 'Rifidi' so that all bundles created as a part of the Rifidi project are easy to locate when there are alot of bundles installed as part of an eclipse installation.<br />
# Write the code for the plugin<br />
# Follow the steps for [[Development and Release Process#Modifying and Existing Bundle| Modifying and Existing Bundle]]<br />
# If you tagged the bundle and added it to the target platform, then make sure you add the new bundle and its dependencies to the product file<br />
# Add an entry to the readme project at the top level of the svn<br />
<br />
==Releasing a Product==<br />
# Download the rifidi build target platform and set it as the target platform for your workspace<br />
# Download the project that contains the product file for the project you are trying to build<br />
# Export the project using the export wizard</div>Andreashttp://wiki.rifidi.net/index.php/Main_PageMain Page2008-05-07T17:47:01Z<p>Andreas: </p>
<hr />
<div>__NOTOC__ <br />
<div style="width: 100%; margin-top: -0.2em;" id="mp"> <br />
<div style="margin-right: 13.8em;"> <br />
<br />
<div id="search" style="border-bottom: 1px solid rgb(255, 204, 102); margin-bottom: 0.9em; background-color: rgb(240, 247, 255); background-repeat: no-repeat; background-position: right top;"><br />
<div id="book" style="padding: 1em 0pt 0.6em; bakground-repeat: no-repeat background-position: 0% 20%;"><br />
<div style="text-align: center;"><br />
<h1 style="border: medium none ; margin: Opt; padding: Opt; font-size: 175%;"><br />
Welcome&nbsp;to&nbsp;the&nbsp;<b>RIFIDI Community Wiki</b></h1><br />
<p>[[RIFIDI]] is an open source [[RFID Environment Emulation]] tool.</p><br />
<p>'''Please find out how to [[Documentation Guidelines|contribute to the Wiki]] before you begin editing.'''</p><br />
</div><br />
<div style="clear: left; height: 1px; overflow: hidden;">&nbsp;</div><br />
</div><br />
</div><br />
<br />
<div style="float: left; clear: left; width: 50%;"><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<h2 style="border: 0pt none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Help for users</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[FAQ |Frequently Asked Questions]] <br />
</li> <br />
<li style="margin: 0.5em 0pt;"><br />
[[Emulator User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Designer User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Tag Streamer User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Release Features]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Reader Guides]]<br />
</li><br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:userDoc|browse more user documents...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255);margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<h2 style="border: 0pt none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Help for developers</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi roadmap|Rifidi Roadmap]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Documentation Guidelines|Contribute to the Wiki]] <br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:Source Code|Running Rifidi from Source]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Emulator documentation summary | Emulator Documentation]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[designer documentation summary | Designer Documentation]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[tag streamer documentation summary | Tag Streamer Documentation]]<br />
</li> <br />
<li style="margin: 0.5em 0pt;"><br />
[[Developer FAQ]]<br />
</li> <br />
<li syle = "margin 0.5em 0pt;"><br />
[[Style Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Compiling Rifidi with JDK 6.0 update 4]]<br />
</li> <br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:developerDoc|browse more developer documents...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
</div><br />
<br />
<div style="width: 49.9%; float: left;"><br />
<br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-left: 0.9em; margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Project Links</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.rifidi.org Rifidi's Home Page]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://sourceforge.net/projects/rifidi/ Rifidi's Sourceforge Page]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[https://67.207.137.86/svn/rep-external Rifidi Source SVN]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.pramari.com Pramari's Website]<br />
</li><br />
</ul><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-left: 0.9em; margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Idea box</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:implementationIdeas|Implementation Ideas]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:loading|Loading]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Useful Links]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Eclipse Tips]]<br />
</li><br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:ideaBox| browse more ideas...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-left: 0.9em; margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">New Developer Documentation (Proposal)</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[Developers:howtoUseSVN|How to use SVN]]<br />
</li><br />
</ul><br />
</div><br />
</div><br />
<br />
</div><br />
</div></div>Andreashttp://wiki.rifidi.net/index.php/Main_PageMain Page2008-05-07T17:45:37Z<p>Andreas: </p>
<hr />
<div>__NOTOC__ <br />
<div style="width: 100%; margin-top: -0.2em;" id="mp"> <br />
<div style="margin-right: 13.8em;"> <br />
<br />
<div id="search" style="border-bottom: 1px solid rgb(255, 204, 102); margin-bottom: 0.9em; background-color: rgb(240, 247, 255); background-repeat: no-repeat; background-position: right top;"><br />
<div id="book" style="padding: 1em 0pt 0.6em; bakground-repeat: no-repeat background-position: 0% 20%;"><br />
<div style="text-align: center;"><br />
<h1 style="border: medium none ; margin: Opt; padding: Opt; font-size: 175%;"><br />
Welcome&nbsp;to&nbsp;the&nbsp;<b>RIFIDI Community Wiki</b></h1><br />
<p>[[RIFIDI]] is an open source [[RFID Environment Emulation]] tool.</p><br />
<p>'''Please find out how to [[Documentation Guidelines|contribute to the Wiki]] before you begin editing.'''</p><br />
</div><br />
<div style="clear: left; height: 1px; overflow: hidden;">&nbsp;</div><br />
</div><br />
</div><br />
<br />
<div style="float: left; clear: left; width: 50%;"><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<h2 style="border: 0pt none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Help for users</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[FAQ |Frequently Asked Questions]] <br />
</li> <br />
<li style="margin: 0.5em 0pt;"><br />
[[Emulator User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Designer User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Tag Streamer User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Release Features]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Reader Guides]]<br />
</li><br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:userDoc|browse more user documents...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255);margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<h2 style="border: 0pt none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Help for developers</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi roadmap|Rifidi Roadmap]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Documentation Guidelines|Contribute to the Wiki]] <br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:Source Code|Running Rifidi from Source]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Emulator documentation summary | Emulator Documentation]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[designer documentation summary | Designer Documentation]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[tag streamer documentation summary | Tag Streamer Documentation]]<br />
</li> <br />
<li style="margin: 0.5em 0pt;"><br />
[[Developer FAQ]]<br />
</li> <br />
<li syle = "margin 0.5em 0pt;"><br />
[[Style Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Compiling Rifidi with JDK 6.0 update 4]]<br />
</li> <br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:developerDoc|browse more developer documents...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
</div><br />
<br />
<div style="width: 49.9%; float: left;"><br />
<br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-left: 0.9em; margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Project Links</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.rifidi.org Rifidi's Home Page]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://sourceforge.net/projects/rifidi/ Rifidi's Sourceforge Page]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[https://67.207.137.86/svn/rep-external Rifidi Source SVN]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.pramari.com Pramari's Website]<br />
</li><br />
</ul><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-left: 0.9em; margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Idea box</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:implementationIdeas|Implementation Ideas]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:loading|Loading]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:codingIdeas|Coding Ideas]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Useful Links]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Eclipse Tips]]<br />
</li><br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:ideaBox| browse more ideas...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-left: 0.9em; margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">New Developer Documentation (Proposal)</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[Developers:howtoUseSVN|How to use SVN]]<br />
</li><br />
</ul><br />
</div><br />
</div><br />
<br />
</div><br />
</div></div>Andreashttp://wiki.rifidi.net/index.php/Main_PageMain Page2008-05-07T17:28:04Z<p>Andreas: Reverted edits by Andreas (Talk); changed back to last version by Prasith</p>
<hr />
<div>__NOTOC__<br />
<div style="width: 100%; margin-top: -0.2em;" id="mp"><br />
<div style="margin-right: 13.8em;"><br />
<div id="search" style="border-bottom: 1px solid rgb(255, 204, 102); margin-bottom: 0.9em; background-color: rgb(240, 247, 255); background-repeat: no-repeat; background-position: right top;"><br />
<br />
<div id="book" style="padding: 1em 0pt 0.6em; bakground-repeat: no-repeat background-position: 0% 20%;"><br />
<br />
<div style="text-align: center;"><br />
<h1 style="border: medium none ; margin: Opt; padding: Opt; font-size: 175%;"><br />
Welcome&nbsp;to&nbsp;the&nbsp;<b>RIFIDI Community Wiki</b></h1><br />
<p>[[RIFIDI]] is an open source [[RFID Environment Emulation]] tool.</p><br />
<p>'''Please find out how to [[Documentation Guidelines|contribute to the Wiki]] before you begin editing.'''</p><br />
<br />
</div><br />
<div style="clear: left; height: 1px; overflow: hidden;">&nbsp;</div><br />
</div><br />
</div><br />
<br />
<div style="float: left; clear: left; width: 50%;"><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<h2 style="border: 0pt none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Help for users</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[FAQ |Frequently Asked Questions]] <br />
</li> <br />
<li style="margin: 0.5em 0pt;"><br />
[[Emulator User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Designer User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Tag Streamer User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Release Features]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Reader Guides]]<br />
</li><br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:userDoc|browse more user documents...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255);margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: 0pt none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Help for developers</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi roadmap|Rifidi Roadmap]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Documentation Guidelines|Contribute to the Wiki]] <br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:Source Code|Running Rifidi from Source]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Emulator documentation summary | Emulator Documentation]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[designer documentation summary | Designer Documentation]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[tag streamer documentation summary | Tag Streamer Documentation]]<br />
</li> <br />
<li style="margin: 0.5em 0pt;"><br />
[[Developer FAQ]]<br />
</li> <br />
<li syle = "margin 0.5em 0pt;"><br />
[[Style Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Compiling Rifidi with JDK 6.0 update 4]]<br />
</li> <br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:developerDoc|browse more developer documents...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Idea box</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:implementationIdeas|Implementation Ideas]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:loading|Loading]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:codingIdeas|Coding Ideas]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Useful Links]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Eclipse Tips]]<br />
</li><br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:ideaBox| browse more ideas...]]</b><br />
</p><br />
</div><br />
</div><br />
</div><br />
<br />
<div style="width: 49.9%; float: left;"><br />
<div style="border: 1px solid rgb(198, 201, 255); margin-left: 0.9em; margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Project Links</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.rifidi.org Rifidi's Home Page]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://sourceforge.net/projects/rifidi/ Rifidi's Sourceforge Page]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[https://67.207.137.86/svn/rep-external Rifidi Source SVN]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.pramari.com Pramari's Website]<br />
</li><br />
</ul><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-left: 0.9em; margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">General Wiki Information</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[http://meta.wikimedia.org/wiki/Help:Contents User's Guide]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]<br />
</li><br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:wiki|browse more wiki Links...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-left: 0.9em; margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">New Developer Documentation (Proposal)</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[Developers:howtoUseSVN|How to use SVN]]<br />
</li><br />
</ul><br />
</div><br />
</div><br />
<br />
</div></div>Andreashttp://wiki.rifidi.net/index.php/Main_PageMain Page2008-05-07T17:26:56Z<p>Andreas: </p>
<hr />
<div>__NOTOC__<br />
<div style="width: 100%; margin-top: -0.2em;" id="mp"><br />
<div style="margin-right: 13.8em;"><br />
<div id="search" style="border-bottom: 1px solid rgb(255, 204, 102); margin-bottom: 0.9em; background-color: rgb(240, 247, 255); background-repeat: no-repeat; background-position: right top;"><br />
<br />
<div id="book" style="padding: 1em 0pt 0.6em; bakground-repeat: no-repeat background-position: 0% 20%;"><br />
<br />
<div style="text-align: center;"><br />
<h1 style="border: medium none ; margin: Opt; padding: Opt; font-size: 175%;"><br />
Welcome&nbsp;to&nbsp;the&nbsp;<b>RIFIDI Community Wiki</b></h1><br />
<p>[[RIFIDI]] is an open source [[RFID Environment Emulation]] tool.</p><br />
<p>'''Please find out how to [[Documentation Guidelines|contribute to the Wiki]] before you begin editing.'''</p><br />
<br />
</div><br />
<div style="clear: left; height: 1px; overflow: hidden;">&nbsp;</div><br />
</div><br />
</div><br />
<br />
<div style="float: left; clear: left; width: 50%;"><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<h2 style="border: 0pt none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Help for users</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[FAQ |Frequently Asked Questions]] <br />
</li> <br />
<li style="margin: 0.5em 0pt;"><br />
[[Emulator User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Designer User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Tag Streamer User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Release Features]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Reader Guides]]<br />
</li><br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:userDoc|browse more user documents...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255);margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: 0pt none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Help for developers</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi roadmap|Rifidi Roadmap]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Documentation Guidelines|Contribute to the Wiki]] <br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:Source Code|Running Rifidi from Source]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Emulator documentation summary | Emulator Documentation]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[designer documentation summary | Designer Documentation]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[tag streamer documentation summary | Tag Streamer Documentation]]<br />
</li> <br />
<li style="margin: 0.5em 0pt;"><br />
[[Developer FAQ]]<br />
</li> <br />
<li syle = "margin 0.5em 0pt;"><br />
[[Style Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Compiling Rifidi with JDK 6.0 update 4]]<br />
</li> <br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:developerDoc|browse more developer documents...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
<div style="width: 49.9%; float: left;"><br />
<div style="border: 1px solid rgb(198, 201, 255); margin-left: 0.9em; margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Project Links</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.rifidi.org Rifidi's Home Page]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://sourceforge.net/projects/rifidi/ Rifidi's Sourceforge Page]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[https://svn.rifidi.org/svn/rep-external Rifidi Source SVN]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.pramari.com Pramari's Website]<br />
</li><br />
</ul><br />
</div><br />
</div><br />
<br />
<div style="width: 49.9%; float: left;"><br />
<div style="border: 1px solid rgb(198, 201, 255); margin-left: 0.9em; margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Idea box</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:implementationIdeas|Implementation Ideas]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:loading|Loading]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:codingIdeas|Coding Ideas]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Useful Links]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Eclipse Tips]]<br />
</li><br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:ideaBox| browse more ideas...]]</b><br />
</p><br />
</div><br />
</div><br />
</div><br />
<br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-left: 0.9em; margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">New Developer Documentation (Proposal)</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[Developers:howtoUseSVN|How to use SVN]]<br />
</li><br />
</ul><br />
</div><br />
</div><br />
<br />
</div></div>Andreashttp://wiki.rifidi.net/index.php/Main_PageMain Page2008-05-07T17:25:03Z<p>Andreas: </p>
<hr />
<div>__NOTOC__<br />
<div style="width: 100%; margin-top: -0.2em;" id="mp"><br />
<div style="margin-right: 13.8em;"><br />
<div id="search" style="border-bottom: 1px solid rgb(255, 204, 102); margin-bottom: 0.9em; background-color: rgb(240, 247, 255); background-repeat: no-repeat; background-position: right top;"><br />
<br />
<div id="book" style="padding: 1em 0pt 0.6em; bakground-repeat: no-repeat background-position: 0% 20%;"><br />
<br />
<div style="text-align: center;"><br />
<h1 style="border: medium none ; margin: Opt; padding: Opt; font-size: 175%;"><br />
Welcome&nbsp;to&nbsp;the&nbsp;<b>RIFIDI Community Wiki</b></h1><br />
<p>[[RIFIDI]] is an open source [[RFID Environment Emulation]] tool.</p><br />
<p>'''Please find out how to [[Documentation Guidelines|contribute to the Wiki]] before you begin editing.'''</p><br />
<br />
</div><br />
<div style="clear: left; height: 1px; overflow: hidden;">&nbsp;</div><br />
</div><br />
</div><br />
<br />
<div style="float: left; clear: left; width: 50%;"><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<h2 style="border: 0pt none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Help for users</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[FAQ |Frequently Asked Questions]] <br />
</li> <br />
<li style="margin: 0.5em 0pt;"><br />
[[Emulator User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Designer User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Tag Streamer User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Release Features]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Reader Guides]]<br />
</li><br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:userDoc|browse more user documents...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255);margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: 0pt none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Help for developers</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi roadmap|Rifidi Roadmap]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Documentation Guidelines|Contribute to the Wiki]] <br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:Source Code|Running Rifidi from Source]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Emulator documentation summary | Emulator Documentation]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[designer documentation summary | Designer Documentation]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[tag streamer documentation summary | Tag Streamer Documentation]]<br />
</li> <br />
<li style="margin: 0.5em 0pt;"><br />
[[Developer FAQ]]<br />
</li> <br />
<li syle = "margin 0.5em 0pt;"><br />
[[Style Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Compiling Rifidi with JDK 6.0 update 4]]<br />
</li> <br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:developerDoc|browse more developer documents...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Idea box</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:implementationIdeas|Implementation Ideas]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:loading|Loading]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:codingIdeas|Coding Ideas]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Useful Links]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Eclipse Tips]]<br />
</li><br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:ideaBox| browse more ideas...]]</b><br />
</p><br />
</div><br />
</div><br />
</div><br />
<br />
<div style="width: 49.9%; float: left;"><br />
<div style="border: 1px solid rgb(198, 201, 255); margin-left: 0.9em; margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Project Links</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.rifidi.org Rifidi's Home Page]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://sourceforge.net/projects/rifidi/ Rifidi's Sourceforge Page]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[https://svn.rifidi.org/svn/rep-external Rifidi Source SVN]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.pramari.com Pramari's Website]<br />
</li><br />
</ul><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-left: 0.9em; margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">General Wiki Information</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[http://meta.wikimedia.org/wiki/Help:Contents User's Guide]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]<br />
</li><br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:wiki|browse more wiki Links...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-left: 0.9em; margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">New Developer Documentation (Proposal)</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[Developers:howtoUseSVN|How to use SVN]]<br />
</li><br />
</ul><br />
</div><br />
</div><br />
<br />
</div></div>Andreashttp://wiki.rifidi.net/index.php/Tag_Streamer_User%27s_Guide_1.1Tag Streamer User's Guide 1.12008-04-30T21:49:23Z<p>Andreas: /* Run TestSuite form Command Line */</p>
<hr />
<div>=Purpose=<br />
Tag Streamer is a load testing tool for edge servers. It allows the user to create multiple virtual readers, chain them together in some way, and add batches of tags to the readers based on patterns. Furthermore, because the readers can exist on different physical hosts, Tag Streamer can distribute its load among several machines. The Tag Streamer UI allows users to rapidly construct the necessary xml files for a test suite. In addition, it allows the user to easily run test suites.<br />
<br />
=Getting Started=<br />
This section will help you get started running Tag Streamer 1.1<br />
==Requirements==<br />
*Microsoft Windows 2000/XP/2003 or Linux (Ubuntu, Red Hat, SuSe)<br />
*Sun Java Runtime Environment 1.6 update 4 or greater (Tag Streamer 2.0 will not work with previous versions of the JRE)<br />
==Installation==<br />
There are two ways to run Tag Streamer:<br />
*Download the release from sourceforge (http://sourceforge.net/project/showfiles.php?group_id=170933)<br />
** Double click on the installer and click next until it is installed<br />
** Double click on the executable to run Tag Streamer<br />
*Download the latest code from our external [[Rifidi:Source_Code | svn]]<br />
** Once the code is downloaded into eclipse, right click on the Tag Streamer product file and select Run As->Eclipse Application<br />
<br />
=Tag Streamer Concepts=<br />
==Test Suite==<br />
A Test Suite is a collection of four elements that define a particular simulation run of Tag Streamer. Conceptually, a Test Suite represents a particular configuration of readers and tag load that the user would like simulate. For example, a test suite could represent the receiving dock doors at a distribution center; the distribution center has four dock doors that are independent; tags seen by reader at dock door 1 will not be seen by the reader at dock door 2. In addition tags are seen in bursts, as workers unload the trucks with fork lifts. All this information is captured within a Test Suite.<br />
<br />
A Test Suite can be completely created within Tag Streamer and saved as an XML. In addition, a user can load a previously saved Test Suite, edit it and save it again.<br />
<br />
===Components===<br />
Components are the emulated devices in a test suite simulation. At this time the only components are virtual RFID readers, but in the future there could be other kinds of components that could act in the simulation, such as electric eyes, barriers, or push arms. the important thing about components are that they represent a ''physical'' configuration for the objec; the component defines configuration information for the reader such as its IP, port, number of antennas and GPI/O ports, etc. It does not contain any information about how the reader is used.<br />
===Scenarios===<br />
Scenarios define a linear flow path of components. For example a scenario having two readers in it could represent an assembly line with two readers where tags seen by reader 1 will be seen by reader 2 at some later time. Scenarios are made up of ''path items'', where each path item has a component (i.e. reader) and also a travel time to the next component in the scenario. This allows us to specify the number of milliseconds that it would tags to travel from reader 1 to reader 2.<br />
===Batches===<br />
Batches are a sequence of patterns of actions that happen on a reader. For example, a batch cause 20 C1G2 tags to be shown to a reader for 500 milliseconds, then wait for 5 seconds, then cause a GPI port to go high for 5 seconds. The important thing to note about batches is that they define a pattern that can be applied to any reader. In other words, batches do ''not'' define on which reader they are applied. This information is left up the the Test Unit.<br />
There are three basic units called ''actions''<br />
;Tag Action<br />
:The tag action defines a pattern of tags that is shown to a reader. For example, 10 Gen 1 tags are placed in the reader's field of view for 5 seconds. Currently, every time that a tag action executes, the tags are regenerated according to the defined pattern. This means that if <tt>Reader1</tt> and <tt>Reader2</tt> both see a particular tag action, they will see different tags (i.e. the ids will be different).<br />
;GPI Action<br />
:The GPI action will set a certain GPI port either high or low for a certain amount of time. For example a GPI Action might be to set GPI port 3 high for 10 seconds.<br />
;Wait Action<br />
:A wait Action is simply a wait time between actions.<br />
<br />
The other important aspect about batches is that they are ''sequences'' of actions. That is, a particular batch can have an arbitrary number of actions inside of it that are executed in order. For example, a batch can have a GPI action followed by a tag action followed by another GPI action.<br />
<br />
===Test Unit===<br />
The Test Unit combines the previous three elements into a runnable simulation. It short, it simply makes the connection between scenarios and batches. Each batch-scenario pair is run in parallel. For example, if a user defines two scenarios and two batches, the Test Unit associates a batch with a scenario. Then, when this test unit is run, it will start both batch-scenario pairs at the same time.<br />
<br />
In addition the Test Unit defines the number of iterations that batches should execute on a scenario. For example, a batch may run on the scenario just once; in this case the simulation would be finished when the last action in the batch executes on the final reader in the scenario. In another case, the user may set the number of runs to infinity, so that the batch keeps executing on the scenario.<br />
<br />
==Interaction between elements==<br />
//TODO: insert a diagram depicting how the four elements work together<br />
<br />
=Using Tag Streamer=<br />
This section will give step-by-step instructions on how to use Tag Streamer.<br />
==Components==<br />
Components are the descriptions of physical readers. It gives information such as IP, number of antennas, etc.<br />
===Create===<br />
# Click the "New Item" icon ([[Image:AddItem.gif]]).<br />
# Select "new Component Wizard"<br />
# Select a type of reader and an unused Component ID in the New Component Wizard<br />
# Finish creating the reader<br />
<br />
{| border="0" style="background:transparent;"<br />
|-<br />
|<br />
[[Image:Ts-component-select.png|300px|thumb|left|Select new component wizard]]<br />
||<br />
[[Image:Ts-component-new.png|300px|thumb|left|Select a type of reader]]<br />
||<br />
[[Image:Ts-component-new-alien.png|300px|thumb|left| select properties for the reader]]<br />
|}<br />
<br />
===Edit===<br />
To edit existing components:<br />
# Select the component you wish to edit on the tree on the left.<br />
# Change the settings in the right pane<br />
[[Image:ts-component-edit.png|300px|thumb|none|Edit Components]]<br />
<br />
==Scenarios==<br />
Scenarios are paths of components along which batches flow. For example, if we have three readers (reader_A, reader_B, and reader_C), we can define a scenario as <br />
<pre> reader_C -> reader_A -> reader_B</pre><br />
which means that tags will be initially seen by reader_C, then by reader_A, and finally by reader_A.<br />
===Create===<br />
# Click the "New Item" icon ([[Image:AddItem.gif]]).<br />
# Select "new Scenario Wizard"<br />
# Add Components to the scenario<br />
## The component ID is the ID number of the component you wish to add<br />
## The travel time is the amount of time after the batch items have finished executing on the reader before they appear on the next reader<br />
## The Antenna is the antenna number that tags should be added to when they enter this component<br />
<br />
{| border="0" style="background:transparent;"<br />
|-<br />
|<br />
[[Image:Ts-scenario-select.png|300px|thumb|left|Select new scenario wizard]]<br />
||<br />
[[Image:Ts-scenario-new.png|300px|thumb|left|Add components to the scenario]]<br />
|}<br />
===Edit===<br />
To edit existing scenarios:<br />
# Select the scenario you wish to edit on the tree on the left.<br />
# Change the settings in the right pane<br />
[[Image:ts-scenario-edit.png|300px|thumb|none|Edit Scenario]]<br />
==Batches==<br />
A batch is a pattern of actions that will act on a component. The available pattern types are:<br />
#Tag Patterns, called Tag Actions<br />
#GPI Patterns, called GPI Actions<br />
#Wait Patterns, called Wait Actoin<br />
===Create===<br />
# Click the "New Item" icon ([[Image:AddItem.gif]]).<br />
# Select "new Batch Wizard"<br />
# Add Actions to the Batch (at least one Tag, GPI, or Wait action is required)<br />
<br />
<br />
{| border="0" style="background:transparent;"<br />
|-<br />
|<br />
[[Image:Ts-batch-new.png|300px|thumb|left|Select new batch wizard]]<br />
||<br />
[[Image:Ts-batch-tagAction.png|300px|thumb|left|Add tag actions to the batch]]<br />
||<br />
|[[Image:Ts-batch-GPIAction.png|300px|thumb|left|Add GPI actions to the batch]]<br />
||<br />
|[[Image:Ts-batch-waitAction.png|300px|thumb|left|Add wait actions to the batch]]<br />
|}<br />
===Edit===<br />
To edit existing batches<br />
# Select the batch you wish to edit on the tree on the left.<br />
# Change the settings in the right pane<br />
# Make sure to click the save button after you finish editing<br />
[[Image:ts-batch-edit.png|300px|thumb|none|Edit Batches]]<br />
==Test Unit==<br />
Test Units match up scenarios to batches and are the "executable" part of a Tag Streamer file. <br />
===Create===<br />
# Click the "New Item" icon ([[Image:AddItem.gif]]).<br />
# Select "new Test Unit Wizard"<br />
# Add at least one batch-scenario pair<br />
# Optionally add wait actions so that the batch will pause before moving on to the next batch-scenario pair<br />
# Select the number of repetitions (anywhere from 1 to infinity)<br />
# If you want wait times before or after the test unit begins execution, fill in the pre and post wait times.<br />
<br />
{| border="0" style="background:transparent;"<br />
|-<br />
|<br />
[[Image:Ts-testunit-select.png|300px|thumb|left|Select new test unit wizard]]<br />
||<br />
[[Image:Ts-testunit-new.png|300px|thumb|left|Add a batch-scenario pair]]<br />
|}<br />
===Edit===<br />
To edit existing Test Units:<br />
# Select the test unit you wish to edit on the tree on the left.<br />
# Change the settings in the right pane<br />
# Make sure to click the save button after you change settings<br />
[[Image:ts-testunit-edit.png|300px|thumb|none|Edit Test Unit]]<br />
===Save===<br />
If you wish to save the test suite that you made for future use: <br />
# Click File->Save Test Suite<br />
# Choose a file name and a directory<br />
<br />
===Load===<br />
If you wish to load a previously saved Test Suite:<br />
# Click File->Load<br />
# Select the test suite file (xml) that you wish to load<br />
<br />
==Run Test Suite==<br />
To run a test suite:<br />
#Highlight the test unit that you wish to run in the tree on the right<br />
#Click the run button() at the top ([[Image:Ts-Start.png]])<br />
[[Image:ts-testunit-start.png|300px|thumb|none|Start Test Unit]]<br />
<br />
=== Run a TestSuite from command line ===<br />
<br />
Since version 1.1 of Rifidi TagStreamer it is also possible to run a previously created TestSuite File (XML) via command line. There are two arguments you need to specify for the execution these are the TestSuite save file and the ID of the TestSuite you want to execute.<br />
<br />
For Windows:<br />
<pre><br />
TagStreamer.exe [Filename] [#ID of TestUnit]<br />
</pre><br />
for example<br />
<pre><br />
TagStreamer.exe C:/temp/streamer.xml 1<br />
</pre><br />
<br />
=Sample Test Suites=<br />
==Assembly Line==<br />
==Dock Door==</div>Andreashttp://wiki.rifidi.net/index.php/Tag_Streamer_User%27s_Guide_1.1Tag Streamer User's Guide 1.12008-04-30T21:44:50Z<p>Andreas: /* Run Test Suite */</p>
<hr />
<div>=Purpose=<br />
Tag Streamer is a load testing tool for edge servers. It allows the user to create multiple virtual readers, chain them together in some way, and add batches of tags to the readers based on patterns. Furthermore, because the readers can exist on different physical hosts, Tag Streamer can distribute its load among several machines. The Tag Streamer UI allows users to rapidly construct the necessary xml files for a test suite. In addition, it allows the user to easily run test suites.<br />
<br />
=Getting Started=<br />
This section will help you get started running Tag Streamer 1.1<br />
==Requirements==<br />
*Microsoft Windows 2000/XP/2003 or Linux (Ubuntu, Red Hat, SuSe)<br />
*Sun Java Runtime Environment 1.6 update 4 or greater (Tag Streamer 2.0 will not work with previous versions of the JRE)<br />
==Installation==<br />
There are two ways to run Tag Streamer:<br />
*Download the release from sourceforge (http://sourceforge.net/project/showfiles.php?group_id=170933)<br />
** Double click on the installer and click next until it is installed<br />
** Double click on the executable to run Tag Streamer<br />
*Download the latest code from our external [[Rifidi:Source_Code | svn]]<br />
** Once the code is downloaded into eclipse, right click on the Tag Streamer product file and select Run As->Eclipse Application<br />
<br />
=Tag Streamer Concepts=<br />
==Test Suite==<br />
A Test Suite is a collection of four elements that define a particular simulation run of Tag Streamer. Conceptually, a Test Suite represents a particular configuration of readers and tag load that the user would like simulate. For example, a test suite could represent the receiving dock doors at a distribution center; the distribution center has four dock doors that are independent; tags seen by reader at dock door 1 will not be seen by the reader at dock door 2. In addition tags are seen in bursts, as workers unload the trucks with fork lifts. All this information is captured within a Test Suite.<br />
<br />
A Test Suite can be completely created within Tag Streamer and saved as an XML. In addition, a user can load a previously saved Test Suite, edit it and save it again.<br />
<br />
===Components===<br />
Components are the emulated devices in a test suite simulation. At this time the only components are virtual RFID readers, but in the future there could be other kinds of components that could act in the simulation, such as electric eyes, barriers, or push arms. the important thing about components are that they represent a ''physical'' configuration for the objec; the component defines configuration information for the reader such as its IP, port, number of antennas and GPI/O ports, etc. It does not contain any information about how the reader is used.<br />
===Scenarios===<br />
Scenarios define a linear flow path of components. For example a scenario having two readers in it could represent an assembly line with two readers where tags seen by reader 1 will be seen by reader 2 at some later time. Scenarios are made up of ''path items'', where each path item has a component (i.e. reader) and also a travel time to the next component in the scenario. This allows us to specify the number of milliseconds that it would tags to travel from reader 1 to reader 2.<br />
===Batches===<br />
Batches are a sequence of patterns of actions that happen on a reader. For example, a batch cause 20 C1G2 tags to be shown to a reader for 500 milliseconds, then wait for 5 seconds, then cause a GPI port to go high for 5 seconds. The important thing to note about batches is that they define a pattern that can be applied to any reader. In other words, batches do ''not'' define on which reader they are applied. This information is left up the the Test Unit.<br />
There are three basic units called ''actions''<br />
;Tag Action<br />
:The tag action defines a pattern of tags that is shown to a reader. For example, 10 Gen 1 tags are placed in the reader's field of view for 5 seconds. Currently, every time that a tag action executes, the tags are regenerated according to the defined pattern. This means that if <tt>Reader1</tt> and <tt>Reader2</tt> both see a particular tag action, they will see different tags (i.e. the ids will be different).<br />
;GPI Action<br />
:The GPI action will set a certain GPI port either high or low for a certain amount of time. For example a GPI Action might be to set GPI port 3 high for 10 seconds.<br />
;Wait Action<br />
:A wait Action is simply a wait time between actions.<br />
<br />
The other important aspect about batches is that they are ''sequences'' of actions. That is, a particular batch can have an arbitrary number of actions inside of it that are executed in order. For example, a batch can have a GPI action followed by a tag action followed by another GPI action.<br />
<br />
===Test Unit===<br />
The Test Unit combines the previous three elements into a runnable simulation. It short, it simply makes the connection between scenarios and batches. Each batch-scenario pair is run in parallel. For example, if a user defines two scenarios and two batches, the Test Unit associates a batch with a scenario. Then, when this test unit is run, it will start both batch-scenario pairs at the same time.<br />
<br />
In addition the Test Unit defines the number of iterations that batches should execute on a scenario. For example, a batch may run on the scenario just once; in this case the simulation would be finished when the last action in the batch executes on the final reader in the scenario. In another case, the user may set the number of runs to infinity, so that the batch keeps executing on the scenario.<br />
<br />
==Interaction between elements==<br />
//TODO: insert a diagram depicting how the four elements work together<br />
<br />
=Using Tag Streamer=<br />
This section will give step-by-step instructions on how to use Tag Streamer.<br />
==Components==<br />
Components are the descriptions of physical readers. It gives information such as IP, number of antennas, etc.<br />
===Create===<br />
# Click the "New Item" icon ([[Image:AddItem.gif]]).<br />
# Select "new Component Wizard"<br />
# Select a type of reader and an unused Component ID in the New Component Wizard<br />
# Finish creating the reader<br />
<br />
{| border="0" style="background:transparent;"<br />
|-<br />
|<br />
[[Image:Ts-component-select.png|300px|thumb|left|Select new component wizard]]<br />
||<br />
[[Image:Ts-component-new.png|300px|thumb|left|Select a type of reader]]<br />
||<br />
[[Image:Ts-component-new-alien.png|300px|thumb|left| select properties for the reader]]<br />
|}<br />
<br />
===Edit===<br />
To edit existing components:<br />
# Select the component you wish to edit on the tree on the left.<br />
# Change the settings in the right pane<br />
[[Image:ts-component-edit.png|300px|thumb|none|Edit Components]]<br />
<br />
==Scenarios==<br />
Scenarios are paths of components along which batches flow. For example, if we have three readers (reader_A, reader_B, and reader_C), we can define a scenario as <br />
<pre> reader_C -> reader_A -> reader_B</pre><br />
which means that tags will be initially seen by reader_C, then by reader_A, and finally by reader_A.<br />
===Create===<br />
# Click the "New Item" icon ([[Image:AddItem.gif]]).<br />
# Select "new Scenario Wizard"<br />
# Add Components to the scenario<br />
## The component ID is the ID number of the component you wish to add<br />
## The travel time is the amount of time after the batch items have finished executing on the reader before they appear on the next reader<br />
## The Antenna is the antenna number that tags should be added to when they enter this component<br />
<br />
{| border="0" style="background:transparent;"<br />
|-<br />
|<br />
[[Image:Ts-scenario-select.png|300px|thumb|left|Select new scenario wizard]]<br />
||<br />
[[Image:Ts-scenario-new.png|300px|thumb|left|Add components to the scenario]]<br />
|}<br />
===Edit===<br />
To edit existing scenarios:<br />
# Select the scenario you wish to edit on the tree on the left.<br />
# Change the settings in the right pane<br />
[[Image:ts-scenario-edit.png|300px|thumb|none|Edit Scenario]]<br />
==Batches==<br />
A batch is a pattern of actions that will act on a component. The available pattern types are:<br />
#Tag Patterns, called Tag Actions<br />
#GPI Patterns, called GPI Actions<br />
#Wait Patterns, called Wait Actoin<br />
===Create===<br />
# Click the "New Item" icon ([[Image:AddItem.gif]]).<br />
# Select "new Batch Wizard"<br />
# Add Actions to the Batch (at least one Tag, GPI, or Wait action is required)<br />
<br />
<br />
{| border="0" style="background:transparent;"<br />
|-<br />
|<br />
[[Image:Ts-batch-new.png|300px|thumb|left|Select new batch wizard]]<br />
||<br />
[[Image:Ts-batch-tagAction.png|300px|thumb|left|Add tag actions to the batch]]<br />
||<br />
|[[Image:Ts-batch-GPIAction.png|300px|thumb|left|Add GPI actions to the batch]]<br />
||<br />
|[[Image:Ts-batch-waitAction.png|300px|thumb|left|Add wait actions to the batch]]<br />
|}<br />
===Edit===<br />
To edit existing batches<br />
# Select the batch you wish to edit on the tree on the left.<br />
# Change the settings in the right pane<br />
# Make sure to click the save button after you finish editing<br />
[[Image:ts-batch-edit.png|300px|thumb|none|Edit Batches]]<br />
==Test Unit==<br />
Test Units match up scenarios to batches and are the "executable" part of a Tag Streamer file. <br />
===Create===<br />
# Click the "New Item" icon ([[Image:AddItem.gif]]).<br />
# Select "new Test Unit Wizard"<br />
# Add at least one batch-scenario pair<br />
# Optionally add wait actions so that the batch will pause before moving on to the next batch-scenario pair<br />
# Select the number of repetitions (anywhere from 1 to infinity)<br />
# If you want wait times before or after the test unit begins execution, fill in the pre and post wait times.<br />
<br />
{| border="0" style="background:transparent;"<br />
|-<br />
|<br />
[[Image:Ts-testunit-select.png|300px|thumb|left|Select new test unit wizard]]<br />
||<br />
[[Image:Ts-testunit-new.png|300px|thumb|left|Add a batch-scenario pair]]<br />
|}<br />
===Edit===<br />
To edit existing Test Units:<br />
# Select the test unit you wish to edit on the tree on the left.<br />
# Change the settings in the right pane<br />
# Make sure to click the save button after you change settings<br />
[[Image:ts-testunit-edit.png|300px|thumb|none|Edit Test Unit]]<br />
===Save===<br />
If you wish to save the test suite that you made for future use: <br />
# Click File->Save Test Suite<br />
# Choose a file name and a directory<br />
<br />
===Load===<br />
If you wish to load a previously saved Test Suite:<br />
# Click File->Load<br />
# Select the test suite file (xml) that you wish to load<br />
<br />
==Run Test Suite==<br />
To run a test suite:<br />
#Highlight the test unit that you wish to run in the tree on the right<br />
#Click the run button() at the top ([[Image:Ts-Start.png]])<br />
[[Image:ts-testunit-start.png|300px|thumb|none|Start Test Unit]]<br />
<br />
=== Run TestSuite form Command Line ===<br />
<br />
Since version 1.1 of Rifidi TagStreamer it is also possible to run a saved XML TestSuite via command line. All you need to do is start RifidiStreamer Executable and give two arguments.<br />
<br />
For Windows:<br />
<pre><br />
TagStreamer.exe [Filename] [#ID of TestUnit]<br />
</pre><br />
for example<br />
<pre><br />
TagStreamer.exe C:/temp/streamer.xml 1<br />
</pre><br />
<br />
=Sample Test Suites=<br />
==Assembly Line==<br />
==Dock Door==</div>Andreashttp://wiki.rifidi.net/index.php/Rifidi:Source_CodeRifidi:Source Code2008-04-28T22:05:29Z<p>Andreas: /* Reporting Bugs */</p>
<hr />
<div>[[category:developerDoc]]<br />
If you are interested in running the latest and greatest, bleeding edge Emulator or if you want to have a look at the source code, you will need to follow the instructions on this page. However, please keep in mind that the code in this repository is not guaranteed to be stable. If you are interested in our latest stable release, visit our sourceforge page: http://sourceforge.net/projects/rifidi/.<br />
<br />
=Downloading the Code=<br />
<br />
Our code is hosted at https://67.207.137.86/svn/rep-external. The svn repository allows anonymous read access. Because the svn repository is the same one that developers submit to, it contains the latest Rifidi code.<br />
<br />
==Prerequisites==<br />
<br />
The Rifidi Emulator is written in java and consists of Eclipse plugins. At this point it must be compiled and built inside of the eclipse environment. <br />
<br />
===Install Eclipse===<br />
<br />
* If you do not already have eclipse, or if you have a different version, you will need to get this version<br />
** Go to http://www.eclipse.org/downloads/ and download the "Eclipse for RCP/Plug-in Developers" version of Eclipse to a convenient location.<br />
** Unzip the package.<br />
** Double click on the execution file to get it started [[Image:Rifidi_from_source-1-opening_eclipse.png |none|thumb|800px|Double click on the executable to open up eclipse]]<br />
* If you have not used eclipse before, you will be required to select a workspace when eclipse is opening.<br />
** After eclipse opens go to the workbench[[Image:Rifidi_from_source-2-wokbench.png |none|thumb|800px|Open up the workbench]]<br />
* If you have an existing workspace, you will need to create a new one.<br />
** Go to file -> switch workspace -> other [[Image:Rifidi_from_source-3-switch_workspace.png |none|thumb|800px|Open up the workbench]] <br />
** Select a new directory for your Rifidi workspace.<br />
<br />
<br />
===Install Subclipse===<br />
<br />
Subclipse is an eclipse plugin that manages svn commands.<br />
<br />
* Follow the instructions at http://subclipse.tigris.org/install.html.<br />
* In step 6 of the above instructions, don't install the Optional Integrations. Only the subclipse plugin is needed<br />
<br />
==Add Repository==<br />
<br />
* Open the 'SVN Repository Exploring' perspective<br />
** Window -> Open Perspective -> Other [[Image:Rifidi_from_source-4-svn_rep_explore1.png |none|thumb|800px|Open up the perspective picker]]<br />
** SVN Repository Exploring [[Image:Rifidi_from_source-5-svn_rep_explore2.png |none|thumb|400px|Open up the SVN Repository Explorer]]<br />
* Add the rifidi repository<br />
** Click 'Add SVN Repository' button<br />
** Add 'https://67.207.137.86/svn/rep-external'[[Image:Rifidi_from_source-6-add_rep.png |none|400px|thumb|Add the repository]]<br />
<br />
==Check Out Code==<br />
<br />
* Check out all the projects in the rifidi/trunk folder of the repository<br />
** Highlight the folders you would like to check out.<br />
*** To run the Emulator check out these [[Emulator Packages |packages]]<br />
*** To run the Designer check out these [[Designer Packages |packages]]<br />
*** To run the Tag Streamer check out these [[Tag Streamer Packages |packages]]<br />
** Right click them and select checkout [[Image:Rifidi_from_source-7-checkout1.png |none|800px|thumb|Select the projects]]<br />
** Select Finish. [[Image:Rifidi_from_source-8-checkout2.png |none|400px|thumb|Checkout projects]]<br />
<br />
=Running Rifidi=<br />
<br />
The last step to get Rifidi Running you need to change the Runtime Configuration<br />
<br />
* Switch to the Java perspective in the same way that you switched to the repository exploring view [[Image:Rifidi_from_source-9-java_view.png |none|400px|thumb|Run Rifidi]]<br />
* Right click on Rifidi.product in the org.rifidi.ide project<br />
* Click on "Run as eclipse application" [[Image:Rifidi_from_source-10_run_eclipse.png |none|thumb|800px|Run Rifidi]]<br />
* If you get an error, click no and perform the following instructions:<br />
** Run -> Open Run Dialog -> Eclipse Application -> Rifidi.product<br />
** Goto the Tab Plug-ins<br />
** click the Button "Add Required Plug-ins" [[Image:Rifidi_from_source-11_add_plugins.png |none|thumb|600px|Add required plugins]]<br />
** check any plugins specifically required for the application to run (for example, the emulator requires the readers to be included)<br />
** click the Button "Validate Plug-ins" to make sure everything is set up correctly<br />
** click the Button "Apply"<br />
** click the Button "Run" and start the Project <br />
* From now on, you can start Rifidi via the green triangle button at the top of eclipse<br />
<br />
=Updating the code=<br />
<br />
Now that you have downloaded the code into an eclipse workspace, it is easy to get changes to the code as soon as we add them to the svn. <br />
<br />
To update the code:<br />
<br />
* Open up the Team Synchronizing Perspective in eclipse<br />
* Click the button that says "Synchronize".<br />
* Select all projects.<br />
* Install any updates by selecting all the updates show, right clicking and choosing 'update'<br />
<br />
Now that you have the new code, just hit the green run button on the toolbar at the top (Eclipse automatically compiles the code for you, so you don't have to worry about that).<br />
<br />
=Switching Branches=<br />
If you need to run code from another branch or tag, please see [[Switching Branches]].<br />
<br />
=Reporting Bugs=<br />
<br />
To report bugs, please use the forum at<br />
<br />
http://forums.rifidi.org<br />
<br />
For more information, please subscribe to and contact us via our mailing list:<br />
<br />
http://sourceforge.net/mail/?group_id=170933,<br />
<br />
or drop by our IRC channel:<br />
<br />
<nowiki>#rifidi on irc.freenode.org.</nowiki><br />
<br />
You can also visit us online at http://www.rifidi.org</div>Andreashttp://wiki.rifidi.net/index.php/Rifidi:Source_CodeRifidi:Source Code2008-04-28T22:05:04Z<p>Andreas: /* Reporting Bugs */</p>
<hr />
<div>[[category:developerDoc]]<br />
If you are interested in running the latest and greatest, bleeding edge Emulator or if you want to have a look at the source code, you will need to follow the instructions on this page. However, please keep in mind that the code in this repository is not guaranteed to be stable. If you are interested in our latest stable release, visit our sourceforge page: http://sourceforge.net/projects/rifidi/.<br />
<br />
=Downloading the Code=<br />
<br />
Our code is hosted at https://67.207.137.86/svn/rep-external. The svn repository allows anonymous read access. Because the svn repository is the same one that developers submit to, it contains the latest Rifidi code.<br />
<br />
==Prerequisites==<br />
<br />
The Rifidi Emulator is written in java and consists of Eclipse plugins. At this point it must be compiled and built inside of the eclipse environment. <br />
<br />
===Install Eclipse===<br />
<br />
* If you do not already have eclipse, or if you have a different version, you will need to get this version<br />
** Go to http://www.eclipse.org/downloads/ and download the "Eclipse for RCP/Plug-in Developers" version of Eclipse to a convenient location.<br />
** Unzip the package.<br />
** Double click on the execution file to get it started [[Image:Rifidi_from_source-1-opening_eclipse.png |none|thumb|800px|Double click on the executable to open up eclipse]]<br />
* If you have not used eclipse before, you will be required to select a workspace when eclipse is opening.<br />
** After eclipse opens go to the workbench[[Image:Rifidi_from_source-2-wokbench.png |none|thumb|800px|Open up the workbench]]<br />
* If you have an existing workspace, you will need to create a new one.<br />
** Go to file -> switch workspace -> other [[Image:Rifidi_from_source-3-switch_workspace.png |none|thumb|800px|Open up the workbench]] <br />
** Select a new directory for your Rifidi workspace.<br />
<br />
<br />
===Install Subclipse===<br />
<br />
Subclipse is an eclipse plugin that manages svn commands.<br />
<br />
* Follow the instructions at http://subclipse.tigris.org/install.html.<br />
* In step 6 of the above instructions, don't install the Optional Integrations. Only the subclipse plugin is needed<br />
<br />
==Add Repository==<br />
<br />
* Open the 'SVN Repository Exploring' perspective<br />
** Window -> Open Perspective -> Other [[Image:Rifidi_from_source-4-svn_rep_explore1.png |none|thumb|800px|Open up the perspective picker]]<br />
** SVN Repository Exploring [[Image:Rifidi_from_source-5-svn_rep_explore2.png |none|thumb|400px|Open up the SVN Repository Explorer]]<br />
* Add the rifidi repository<br />
** Click 'Add SVN Repository' button<br />
** Add 'https://67.207.137.86/svn/rep-external'[[Image:Rifidi_from_source-6-add_rep.png |none|400px|thumb|Add the repository]]<br />
<br />
==Check Out Code==<br />
<br />
* Check out all the projects in the rifidi/trunk folder of the repository<br />
** Highlight the folders you would like to check out.<br />
*** To run the Emulator check out these [[Emulator Packages |packages]]<br />
*** To run the Designer check out these [[Designer Packages |packages]]<br />
*** To run the Tag Streamer check out these [[Tag Streamer Packages |packages]]<br />
** Right click them and select checkout [[Image:Rifidi_from_source-7-checkout1.png |none|800px|thumb|Select the projects]]<br />
** Select Finish. [[Image:Rifidi_from_source-8-checkout2.png |none|400px|thumb|Checkout projects]]<br />
<br />
=Running Rifidi=<br />
<br />
The last step to get Rifidi Running you need to change the Runtime Configuration<br />
<br />
* Switch to the Java perspective in the same way that you switched to the repository exploring view [[Image:Rifidi_from_source-9-java_view.png |none|400px|thumb|Run Rifidi]]<br />
* Right click on Rifidi.product in the org.rifidi.ide project<br />
* Click on "Run as eclipse application" [[Image:Rifidi_from_source-10_run_eclipse.png |none|thumb|800px|Run Rifidi]]<br />
* If you get an error, click no and perform the following instructions:<br />
** Run -> Open Run Dialog -> Eclipse Application -> Rifidi.product<br />
** Goto the Tab Plug-ins<br />
** click the Button "Add Required Plug-ins" [[Image:Rifidi_from_source-11_add_plugins.png |none|thumb|600px|Add required plugins]]<br />
** check any plugins specifically required for the application to run (for example, the emulator requires the readers to be included)<br />
** click the Button "Validate Plug-ins" to make sure everything is set up correctly<br />
** click the Button "Apply"<br />
** click the Button "Run" and start the Project <br />
* From now on, you can start Rifidi via the green triangle button at the top of eclipse<br />
<br />
=Updating the code=<br />
<br />
Now that you have downloaded the code into an eclipse workspace, it is easy to get changes to the code as soon as we add them to the svn. <br />
<br />
To update the code:<br />
<br />
* Open up the Team Synchronizing Perspective in eclipse<br />
* Click the button that says "Synchronize".<br />
* Select all projects.<br />
* Install any updates by selecting all the updates show, right clicking and choosing 'update'<br />
<br />
Now that you have the new code, just hit the green run button on the toolbar at the top (Eclipse automatically compiles the code for you, so you don't have to worry about that).<br />
<br />
=Switching Branches=<br />
If you need to run code from another branch or tag, please see [[Switching Branches]].<br />
<br />
=Reporting Bugs=<br />
<br />
To report bugs, please use the forum at<br />
<br />
http://forums.wiki.org<br />
<br />
For more information, please subscribe to and contact us via our mailing list:<br />
<br />
http://sourceforge.net/mail/?group_id=170933,<br />
<br />
or drop by our IRC channel:<br />
<br />
<nowiki>#rifidi on irc.freenode.org.</nowiki><br />
<br />
You can also visit us online at http://www.rifidi.org</div>Andreashttp://wiki.rifidi.net/index.php/Rifidi:Source_CodeRifidi:Source Code2008-04-28T22:04:28Z<p>Andreas: /* Reporting Bugs */</p>
<hr />
<div>[[category:developerDoc]]<br />
If you are interested in running the latest and greatest, bleeding edge Emulator or if you want to have a look at the source code, you will need to follow the instructions on this page. However, please keep in mind that the code in this repository is not guaranteed to be stable. If you are interested in our latest stable release, visit our sourceforge page: http://sourceforge.net/projects/rifidi/.<br />
<br />
=Downloading the Code=<br />
<br />
Our code is hosted at https://67.207.137.86/svn/rep-external. The svn repository allows anonymous read access. Because the svn repository is the same one that developers submit to, it contains the latest Rifidi code.<br />
<br />
==Prerequisites==<br />
<br />
The Rifidi Emulator is written in java and consists of Eclipse plugins. At this point it must be compiled and built inside of the eclipse environment. <br />
<br />
===Install Eclipse===<br />
<br />
* If you do not already have eclipse, or if you have a different version, you will need to get this version<br />
** Go to http://www.eclipse.org/downloads/ and download the "Eclipse for RCP/Plug-in Developers" version of Eclipse to a convenient location.<br />
** Unzip the package.<br />
** Double click on the execution file to get it started [[Image:Rifidi_from_source-1-opening_eclipse.png |none|thumb|800px|Double click on the executable to open up eclipse]]<br />
* If you have not used eclipse before, you will be required to select a workspace when eclipse is opening.<br />
** After eclipse opens go to the workbench[[Image:Rifidi_from_source-2-wokbench.png |none|thumb|800px|Open up the workbench]]<br />
* If you have an existing workspace, you will need to create a new one.<br />
** Go to file -> switch workspace -> other [[Image:Rifidi_from_source-3-switch_workspace.png |none|thumb|800px|Open up the workbench]] <br />
** Select a new directory for your Rifidi workspace.<br />
<br />
<br />
===Install Subclipse===<br />
<br />
Subclipse is an eclipse plugin that manages svn commands.<br />
<br />
* Follow the instructions at http://subclipse.tigris.org/install.html.<br />
* In step 6 of the above instructions, don't install the Optional Integrations. Only the subclipse plugin is needed<br />
<br />
==Add Repository==<br />
<br />
* Open the 'SVN Repository Exploring' perspective<br />
** Window -> Open Perspective -> Other [[Image:Rifidi_from_source-4-svn_rep_explore1.png |none|thumb|800px|Open up the perspective picker]]<br />
** SVN Repository Exploring [[Image:Rifidi_from_source-5-svn_rep_explore2.png |none|thumb|400px|Open up the SVN Repository Explorer]]<br />
* Add the rifidi repository<br />
** Click 'Add SVN Repository' button<br />
** Add 'https://67.207.137.86/svn/rep-external'[[Image:Rifidi_from_source-6-add_rep.png |none|400px|thumb|Add the repository]]<br />
<br />
==Check Out Code==<br />
<br />
* Check out all the projects in the rifidi/trunk folder of the repository<br />
** Highlight the folders you would like to check out.<br />
*** To run the Emulator check out these [[Emulator Packages |packages]]<br />
*** To run the Designer check out these [[Designer Packages |packages]]<br />
*** To run the Tag Streamer check out these [[Tag Streamer Packages |packages]]<br />
** Right click them and select checkout [[Image:Rifidi_from_source-7-checkout1.png |none|800px|thumb|Select the projects]]<br />
** Select Finish. [[Image:Rifidi_from_source-8-checkout2.png |none|400px|thumb|Checkout projects]]<br />
<br />
=Running Rifidi=<br />
<br />
The last step to get Rifidi Running you need to change the Runtime Configuration<br />
<br />
* Switch to the Java perspective in the same way that you switched to the repository exploring view [[Image:Rifidi_from_source-9-java_view.png |none|400px|thumb|Run Rifidi]]<br />
* Right click on Rifidi.product in the org.rifidi.ide project<br />
* Click on "Run as eclipse application" [[Image:Rifidi_from_source-10_run_eclipse.png |none|thumb|800px|Run Rifidi]]<br />
* If you get an error, click no and perform the following instructions:<br />
** Run -> Open Run Dialog -> Eclipse Application -> Rifidi.product<br />
** Goto the Tab Plug-ins<br />
** click the Button "Add Required Plug-ins" [[Image:Rifidi_from_source-11_add_plugins.png |none|thumb|600px|Add required plugins]]<br />
** check any plugins specifically required for the application to run (for example, the emulator requires the readers to be included)<br />
** click the Button "Validate Plug-ins" to make sure everything is set up correctly<br />
** click the Button "Apply"<br />
** click the Button "Run" and start the Project <br />
* From now on, you can start Rifidi via the green triangle button at the top of eclipse<br />
<br />
=Updating the code=<br />
<br />
Now that you have downloaded the code into an eclipse workspace, it is easy to get changes to the code as soon as we add them to the svn. <br />
<br />
To update the code:<br />
<br />
* Open up the Team Synchronizing Perspective in eclipse<br />
* Click the button that says "Synchronize".<br />
* Select all projects.<br />
* Install any updates by selecting all the updates show, right clicking and choosing 'update'<br />
<br />
Now that you have the new code, just hit the green run button on the toolbar at the top (Eclipse automatically compiles the code for you, so you don't have to worry about that).<br />
<br />
=Switching Branches=<br />
If you need to run code from another branch or tag, please see [[Switching Branches]].<br />
<br />
=Reporting Bugs=<br />
<br />
To report bugs, please use the bug tracker on our sourceforge page, or send a note out on our mailing list.<br />
For more information<br />
<br />
http://forums.wiki.org<br />
<br />
For more information, please subscribe to and contact us via our mailing list:<br />
<br />
http://sourceforge.net/mail/?group_id=170933,<br />
<br />
or drop by our IRC channel:<br />
<br />
<nowiki>#rifidi on irc.freenode.org.</nowiki><br />
<br />
You can also visit us online at http://www.rifidi.org</div>Andreashttp://wiki.rifidi.net/index.php/Help:ContentsHelp:Contents2008-04-28T22:03:15Z<p>Andreas: </p>
<hr />
<div>*[[Rifidi User's Guide]]<br />
<br />
*[[FAQ |Frequently Asked Questions]] <br />
<br />
*[[Documentation Guidelines|Contribute to the Wiki]] <br />
<br />
*[[Rifidi:Source Code|Running Rifidi from Source]]<br />
<br />
*[[:Category:developerDoc|Developer Documentation]]<br />
<br />
<br />
'''If you need more help feel free to contact us:'''<br />
<br />
'''Forum:'''<br />
http://forums.rifidi.org<br />
<br />
'''Email Lists:'''<br />
http://sourceforge.net/mail/?group_id=170933<br />
<br />
'''IRC channel:''' <br />
#rifidi on irc.freenode.org.<br />
<br />
<br />
<br />
'''You can also visit us online at http://www.rifidi.org'''.<br />
<br />
[[Category:help]]</div>Andreashttp://wiki.rifidi.net/index.php/Designer_User%27s_GuideDesigner User's Guide2008-04-28T21:24:43Z<p>Andreas: /* Requirements */</p>
<hr />
<div>[[category:userDoc]]<br />
<br />
=Requirements=<br />
*Microsoft Windows 2000/XP/2003 or Linux (Ubuntu, Red Hat, SuSe)<br />
*Sun Java Runtime Environment > 1.6 (J2SE 6.0)<br />
** If you are having trouble running Designer 1.0 or 1.1, please see [[Specifying JRE 5 |Workaround for JRE 1.6 Issue]]<br />
<br />
=Installation=<br />
Designer is completely written in Java so installation is very easy. Additionally, Designer is packaged in a standard installer.<br />
<br />
# Download the latest version of Rifidi Emulator from http://sourceforge.net/projects/rifidi/<br />
# Double click to run the install. Follow the on screen instructions.<br />
<br />
=Launching Rifidi Designer=<br />
<br />
*Windows Users: Simply click the shortcut located in the Rifidi folder in the Start Menu/Programs folder.<br />
*Linux Users: Double click the executable file located in the installation directory.<br />
<br />
=Getting Started - Example Designer Simulation=<br />
==Create Layout==<br />
#Once the program is loaded, the main UI will be present. [[Image:DesignerHome.png |none|thumb|800px|The Rifidi Designer UI]]<br />
#To create a new layout, click the 'file' and 'new layout'. <br />
#Enter in a layout name, select size of the room (64x64 or 256x256 square feet) and click 'Finish'.[[Image:DesignerNewLayoutWizard.png |none|thumb|400px|Create New Layout]] <br />
#A new empty layout will be displayed in the UI ready for use [[Image:DesignerNewLayout.png |none|thumb|800px|New Layout]]<br />
<br />
==Add a Conveyor==<br />
#Click on the 'Components' Tab to view the library of all available components to add to a layout.[[Image:DesignerComponentView.png |none|thumb|800px|The Rifidi Designer UI]]<br />
#If the list is not expanded already, Click on the '+' next to RFID Base Models to expand the list. [[Image:DesignerComponentViewExpanded.png |none|thumb|800px|The Rifidi Designer UI]]<br />
#Highlight the 'Conveyor' component and drag and drop to the 'Layout Designer'<br />
#Enter a name for the component and the feet per second. (Example 1 ft/sec) [[Image:DesignerConveyorWizard.png |none|thumb|800px|The Rifidi Designer UI]]<br />
#You will now see the component displayed in the 'Layout Designer'. ''Note: For placement refer to the Component Placement Section''<br />
<br />
==Add a Push Arm==<br />
#Click on the 'Components' Tab to view the library of all available components to add to a layout.<br />
#If the list is not expanded already, Click on the '+' next to RFID Base Models to expand the list.<br />
#Highlight the 'Push Arm' component and drag and drop to the 'Layout Designer'<br />
#Enter a name for the component, the seconds per push and click 'Finish'. (Example: 1 sec/push)<br />
#You will now see the component displayed in the 'Layout Designer'. ''Note: For placement refer to the Component Placement Section''<br />
<br />
==Add a Gate==<br />
#Click on the 'Components' Tab to view the library of all available components to add to a layout.<br />
#If the list is not expanded already, Click on the '+' next to RFID Base Models to expand the list.<br />
#Highlight the 'Gate' component and drag and drop to the 'Layout Designer'<br />
#Enter a name for the component, select a reader type and click 'Next'. <br />
#Enter a name for the reader and click 'Finish'.<br />
#You will now see the component displayed in the 'Layout Designer'. ''Note: For placement refer to the Component Placement Section''<br />
<br />
==Add a Box Producer==<br />
#Click on the 'Components' Tab to view the library of all available components to add to a layout.<br />
#If the list is not expanded already, Click on the '+' next to RFID Base Models to expand the list.<br />
#Highlight the 'Producer' component and drag and drop to the 'Layout Designer'<br />
#Enter a name for the component, seconds per box and click 'Finish'. (Example: 5 sec/box)<br />
#You will now see the component displayed in the 'Layout Designer'. ''Note: For placement refer to the Component Placement Section''<br />
<br />
==Component Placement==<br />
===Conveyor Placement===<br />
#In the Layout Designer View, click on the conveyor. ''Note: Yellow arrows will show the direction of the conveyor''<br />
#Move the conveyor to the desired location by holding the left mouse button down. ''Note: The area below the component will be highlighted in green when placement is valid and red when placement is invalid.''<br />
#Release the left mouse button once the desired location has been reached.<br />
#If placement is valid the component will move to the new location and if placement is invalid the component will move to the prior valid location<br />
<br />
===Box Producer Placement===<br />
#In the Layout Designer View, click on the Box Producer. <br />
#Move the producer to the desired location by holding the left mouse button down. ''Note: The area below the component will be highlighted.''<br />
#Once the producer is over the end of the conveyor, release the left mouse button to finish placement.<br />
<br />
===Push Arm Placement===<br />
#In the Layout Designer View, click on the Push Arm. <br />
#Move the gate to the desired location by holding the left mouse button down. ''Note: The area below the component will be highlighted.''<br />
#Once the push arm is next to the right end of the conveyor, release the left mouse button.<br />
#To finalize the placement, verify the push arm is pointed in the direction to push over the conveyor (Look for shaded area to be over conveyor). If not then you can rotate the component by 90 degrees by clicking on the component and then clicking on the rotate 90 degrees button in the toolbar. ''Note: Click twice to turn the component in the opposite direction.<br />
''<br />
<br />
===Gate Placement===<br />
#In the Layout Designer View, click on the Gate. <br />
#Verify the space between the gate's legs can fit over the conveyor based on the conveyor's placement. If not then click on the gate and rotate 90 degrees by clicking on the 90 degree rotate button in the toolbar.<br />
#Move the gate to the desired location by holding the left mouse button down. ''Note: The area below the component will be highlighted in green when placement is valid and red when placement is invalid.''<br />
#Once the gate is over the center of the conveyor, release the left mouse button.<br />
<br />
==Assign a Data Producer to a Producer component==<br />
#Click on the Layout Navigator tab. <br />
#Click on the '+' next to Ungrouped Components to expand the ungrouped components list if not expanded already.<br />
#Click on the '+' next to Data Producer to expand the data producer list if not expanded already.<br />
#In the Data Producer list click on the desired tag data to be associated with the box producer. (Example: DOD tags)<br />
#Hold the left mouse button down on the desired data producer and drag and drop onto the Box Producer located in the ungrouped components list.<br />
#You have now associated a Data Producer to the Box Producer which is a necessary step for the simulation to generate the desired tag data format.<br />
<br />
==Create a Group==<br />
#Click on the Layout Navigator tab. <br />
#Right click on Grouped Components<br />
#In the right click menu, click on create group<br />
#In the create group wizard, enter in a group name (example: group1)<br />
#You will now see the new group listed under Grouped Components<br />
<br />
==Add Components to Group==<br />
#Click on the Layout Navigator tab. <br />
#Click on the '+' next to Ungrouped Components to expand the ungrouped components list if not expanded already.<br />
#Click on the '+' next to Grouped Components to expand the grouped list if not expanded already.<br />
#In the Ungrouped Components list, click on the conveyor component (Example: conveyor1).<br />
#Hold the left mouse button down on the conveyor component and drag and drop into the Group (Example: group1)<br />
#Repeat steps 2 - 4 for each or the remaining ungrouped components<br />
#Once all the steps have been completed, you will now have all the components assigned to a group. (Example: group1) Now you can move the components around in a group in the Layout Designer instead of having to move each component seperately. There are other benefits of groups which will be described in later sections.<br />
<br />
==Turn On Components==<br />
There are two ways to turn on components:<br />
<br />
#Click on the Layout Navigator tab if not already selected. <br />
#Click on the '+' next to Grouped Components to expand the grouped list if not expanded already.<br />
#Click on the '+' next to the group name (Example: group1) to expand the group if not expanded already.<br />
#Right click on the conveyor component<br />
#In the conveyor component right click menu, click on turn On<br />
#Repeat steps 3-4 for each component in the group<br />
<br />
or the short cut is to:<br />
<br />
#Click on the Layout Navigator tab if not already selected. <br />
#Click on the '+' next to Grouped Components to expand the grouped list if not expanded already.<br />
#Click on the '+' next to the group name (Example: group1) to expand the group if not expanded already.<br />
#Right click on group (Example: group1)<br />
#In the group right click menu, click on Turn On<br />
#This will Turn On all the components assigned to tha group<br />
<br />
You can now connect to the virtual reader (Alien, AWID, Symbol, LLRP) you created with a client such as telnet, client library, middleware or EdgeServer.<br />
<br />
==Start Simulation==<br />
#On the Designer Toolbar, you can now click on the play button to start the simultaion<br />
#Once you start the simultaion you should now see boxes being produced and the conveyor and push arm moving at their defined rates.<br />
#The client connected to the virtual reader should now report tags as the boxes pass through the gate's aetenna.<br />
<br />
==Pause Simulation==<br />
#On the Designer Toolbar, you can now click on the Pause button to start the simultaion<br />
#Once you pause the simultaion you should now see boxes being produced and the conveyor and push arm moving pause, left in the previous state.<br />
#The client connected to the virtual reader will continue to be connected.<br />
<br />
==Reset Simulation==<br />
#On the Designer Toolbar, you can now click on the reset button to start the simultaion<br />
#Once you reset the simultaion you should now see boxes being produced, the conveyor and push arm moving be reset<br />
#The client connected to the virtual reader will continue to be connected.<br />
<br />
==Turn Off Components==<br />
There are two ways to Turn Off components:<br />
<br />
#Click on the Layout Navigator tab if not already selected. <br />
#Click on the '+' next to Grouped Components to expand the grouped list if not expanded already.<br />
#Click on the '+' next to the group name (Example: group1) to expand the group if not expanded already.<br />
#Right click on the conveyor component<br />
#In the conveyor component right click menu, click on Turn Off<br />
#Repeat steps 3-4 for each component in the group<br />
<br />
or the short cut is to:<br />
<br />
#Click on the Layout Navigator tab if not already selected. <br />
#Click on the '+' next to Grouped Components to expand the grouped list if not expanded already.<br />
#Click on the '+' next to the group name (Example: group1) to expand the group if not expanded already.<br />
#Right click on group (Example: group1)<br />
#In the group right click menu, click on Turn Off<br />
#This will Turn Off all the components assigned to the group<br />
<br />
The client should now disconnect from the virtual reader as if the device has been powered off<br />
<br />
==Properties==<br />
===Edit Conveyor Speed===<br />
==Add Components to Group==<br />
#Click on the Layout Navigator tab. <br />
#Click on the '+' next to Grouped Components to expand the grouped list if not expanded already.<br />
#Click on the '+' next to the group (Example: groups1) to expand the assigned grouped component list if not expanded already.<br />
#Click on the conveyor component.<br />
#At the bottom below the Layout Designer view you will now see the conveyor component's property view.<br />
#Click on the speed property and change the value.<br />
#The next time you Turn On the components (if not on already) and play the simulation you will see the new speed.<br />
<br />
<br />
===Edit Box Producer Rate===<br />
#Click on the Layout Navigator tab. <br />
#Click on the '+' next to Grouped Components to expand the grouped list if not expanded already.<br />
#Click on the '+' next to the group (Example: groups1) to expand the assigned grouped component list if not expanded already.<br />
#Click on the box producer component.<br />
#At the bottom below the Layout Designer view you will now see the box producer component's property view.<br />
#Click on the rate property and change the value.<br />
#The next time you Turn On the components (if not on already) and play the simulation you will see the new rate.<br />
<br />
=Layouts=<br />
==Create Layout==<br />
#Once the program is loaded, the main UI will be present. [[Image:DesignerHome.PNG |none|thumb|800px|The Rifidi Designer GUI]]<br />
#To create a new layout, click the 'file' and 'new layout'. <br />
#Enter in a layout name, select size of the room (64x64 or 256x256 square feet) and click 'Finish'.[[Image:DesignerCreateLayout.png |none|thumb|400px|Create New Layout]] <br />
#A new empty layout will be displayed in the UI ready for use [[Image:DesignerNewLayout.png |none|thumb|800px|New Layout]]<br />
<br />
==Open Layout==<br />
# Once the program is loaded, the main UI will be present. [[Image:DesignerHome.png |none|thumb|800px|The Rifidi Designer UI]]<br />
<br />
=Components=<br />
<br />
<br />
==Turn on Components==<br />
==Turn off Components==<br />
==Rename Components==<br />
==Delete Components==<br />
<br />
=Placement=<br />
==Moving Components==<br />
==Rotating 90 Degrees==<br />
<br />
=Layout Navigation=<br />
==UnGrouped Components==<br />
==Grouped Components==<br />
===Create Group===<br />
===Add Components===<br />
===Rename Group===<br />
===Delete Group===<br />
<br />
==Generated Components==<br />
==Data Producers==<br />
<br />
<br />
<br />
=MiniMap=<br />
==Navigation==<br />
==Zoom in/Zoom out==<br />
<br />
=Camera=<br />
==Camera Views==<br />
==Zoom in/Zoom out==<br />
<br />
<br />
<br />
=Quickstart Video=<br />
A video of these installation steps can be seen here: http://www.rifidi.org/rifidipackage/rif_out.html</div>Andreashttp://wiki.rifidi.net/index.php/Developer_FAQDeveloper FAQ2008-04-15T01:30:23Z<p>Andreas: /* How do I build an emulator for a reader? */</p>
<hr />
<div>== How do I get and build Rifidi? ==<br />
<br />
You can either download Rifidi form the sourceforge page (http://sourceforge.net/projects/rifidi/) or you can download the source code from our subversion server. If you decide to download the source code we recommend to use Eclipse as Development environment. There is also a howto for eclipse available at our wiki ([[Rifidi:Source Code|Running Rifidi from Source]]).<br />
<br />
== How do I build an emulator for a reader? ==<br />
<br />
A good start would be to look here : [[Emulator documentation summary | Emulator Documentation]]<br />
<br />
If you don't find the information you are looking for feel free to contact us. We try to help as far as we can.<br />
<br />
== How do I submit a new reader back to the project? ==<br />
<br />
Well, we are not supporting anonymous code commit to our svn server. But if you are interested in contributing code, feel free to contact us.<br />
<br />
== How do I submit a bug fix or new feature back to the project? ==<br />
<br />
Well, we are not supporting anonymous code commit to our svn server. But if you are interested in contributing code, feel free to contact us.</div>Andreashttp://wiki.rifidi.net/index.php/Developer_FAQDeveloper FAQ2008-04-15T01:28:22Z<p>Andreas: /* How do I submit a bug fix or new feature back to the project? */</p>
<hr />
<div>== How do I get and build Rifidi? ==<br />
<br />
You can either download Rifidi form the sourceforge page (http://sourceforge.net/projects/rifidi/) or you can download the source code from our subversion server. If you decide to download the source code we recommend to use Eclipse as Development environment. There is also a howto for eclipse available at our wiki ([[Rifidi:Source Code|Running Rifidi from Source]]).<br />
<br />
== How do I build an emulator for a reader? ==<br />
<br />
== How do I submit a new reader back to the project? ==<br />
<br />
Well, we are not supporting anonymous code commit to our svn server. But if you are interested in contributing code, feel free to contact us.<br />
<br />
== How do I submit a bug fix or new feature back to the project? ==<br />
<br />
Well, we are not supporting anonymous code commit to our svn server. But if you are interested in contributing code, feel free to contact us.</div>Andreashttp://wiki.rifidi.net/index.php/Developer_FAQDeveloper FAQ2008-04-15T01:28:12Z<p>Andreas: /* How do I submit a bug fix or new feature back to the project? */</p>
<hr />
<div>== How do I get and build Rifidi? ==<br />
<br />
You can either download Rifidi form the sourceforge page (http://sourceforge.net/projects/rifidi/) or you can download the source code from our subversion server. If you decide to download the source code we recommend to use Eclipse as Development environment. There is also a howto for eclipse available at our wiki ([[Rifidi:Source Code|Running Rifidi from Source]]).<br />
<br />
== How do I build an emulator for a reader? ==<br />
<br />
== How do I submit a new reader back to the project? ==<br />
<br />
Well, we are not supporting anonymous code commit to our svn server. But if you are interested in contributing code, feel free to contact us.<br />
<br />
== How do I submit a bug fix or new feature back to the project? ==<br />
<br />
Well, we are not supporting anonymous code commit to our svn server. But if you are interested in contributing code, feel free to contact</div>Andreashttp://wiki.rifidi.net/index.php/Developer_FAQDeveloper FAQ2008-04-15T01:27:34Z<p>Andreas: /* How do I submit a new reader back to the project? */</p>
<hr />
<div>== How do I get and build Rifidi? ==<br />
<br />
You can either download Rifidi form the sourceforge page (http://sourceforge.net/projects/rifidi/) or you can download the source code from our subversion server. If you decide to download the source code we recommend to use Eclipse as Development environment. There is also a howto for eclipse available at our wiki ([[Rifidi:Source Code|Running Rifidi from Source]]).<br />
<br />
== How do I build an emulator for a reader? ==<br />
<br />
== How do I submit a new reader back to the project? ==<br />
<br />
Well, we are not supporting anonymous code commit to our svn server. But if you are interested in contributing code, feel free to contact us.<br />
<br />
== How do I submit a bug fix or new feature back to the project? ==</div>Andreashttp://wiki.rifidi.net/index.php/Developer_FAQDeveloper FAQ2008-04-15T01:25:16Z<p>Andreas: /* How do I get and build Rifidi? */</p>
<hr />
<div>== How do I get and build Rifidi? ==<br />
<br />
You can either download Rifidi form the sourceforge page (http://sourceforge.net/projects/rifidi/) or you can download the source code from our subversion server. If you decide to download the source code we recommend to use Eclipse as Development environment. There is also a howto for eclipse available at our wiki ([[Rifidi:Source Code|Running Rifidi from Source]]).<br />
<br />
== How do I build an emulator for a reader? ==<br />
<br />
== How do I submit a new reader back to the project? ==<br />
<br />
== How do I submit a bug fix or new feature back to the project? ==</div>Andreashttp://wiki.rifidi.net/index.php/Developer_FAQDeveloper FAQ2008-04-15T01:24:37Z<p>Andreas: /* How do I get and build Rifidi? */</p>
<hr />
<div>== How do I get and build Rifidi? ==<br />
<br />
You can either download Rifidi form the sourceforge page (http://sourceforge.net/projects/rifidi/) or you can download the source code from our subversion server. If you decide to download the source code we recommend to use Eclipse as Development environment. There is also a howto for eclipse available at our wiki : [[Source_Code| Running rifidi from source code]].<br />
<br />
== How do I build an emulator for a reader? ==<br />
<br />
== How do I submit a new reader back to the project? ==<br />
<br />
== How do I submit a bug fix or new feature back to the project? ==</div>Andreashttp://wiki.rifidi.net/index.php/Main_PageMain Page2008-04-15T01:18:23Z<p>Andreas: </p>
<hr />
<div>__NOTOC__<br />
<div style="width: 100%; margin-top: -0.2em;" id="mp"><br />
<div style="margin-right: 13.8em;"><br />
<div id="search" style="border-bottom: 1px solid rgb(255, 204, 102); margin-bottom: 0.9em; background-color: rgb(240, 247, 255); background-repeat: no-repeat; background-position: right top;"><br />
<br />
<div id="book" style="padding: 1em 0pt 0.6em; bakground-repeat: no-repeat background-position: 0% 20%;"><br />
<br />
<div style="text-align: center;"><br />
<h1 style="border: medium none ; margin: Opt; padding: Opt; font-size: 175%;"><br />
Welcome&nbsp;to&nbsp;the&nbsp;<b>RIFIDI Community Wiki</b></h1><br />
<p>[[RIFIDI]] is an open source [[RFID Environment Emulation]] tool.</p><br />
<p>'''Please find out how to [[Documentation Guidelines|contribute to the Wiki]] before you begin editing.'''</p><br />
<br />
</div><br />
<div style="clear: left; height: 1px; overflow: hidden;">&nbsp;</div><br />
</div><br />
</div><br />
<br />
<div style="float: left; clear: left; width: 50%;"><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<h2 style="border: 0pt none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Help for users</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[FAQ |Frequently Asked Questions]] <br />
</li> <br />
<li style="margin: 0.5em 0pt;"><br />
[[Emulator User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Designer User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Tag Streamer User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Release Features]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Reader Guides]]<br />
</li><br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:userDoc|browse more user documents...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255);margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: 0pt none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Help for developers</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi roadmap|Rifidi Roadmap]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Documentation Guidelines|Contribute to the Wiki]] <br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:Source Code|Running Rifidi from Source]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Emulator documentation summary | Emulator Documentation]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[designer documentation summary | Designer Documentation]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[tag streamer documentation summary | Tag Streamer Documentation]]<br />
</li> <br />
<li style="margin: 0.5em 0pt;"><br />
[[Developer FAQ]]<br />
</li> <br />
<li syle = "margin 0.5em 0pt;"><br />
[[Style Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Compiling Rifidi with JDK 6.0 update 4]]<br />
</li> <br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:developerDoc|browse more developer documents...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Idea box</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:implementationIdeas|Implementation Ideas]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:codingIdeas|Coding Ideas]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Useful Links]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Eclipse Tips]]<br />
</li><br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:ideaBox| browse more ideas...]]</b><br />
</p><br />
</div><br />
</div><br />
</div><br />
<br />
<div style="width: 49.9%; float: left;"><br />
<div style="border: 1px solid rgb(198, 201, 255); margin-left: 0.9em; margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Project Links</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[http://rifidi.org Rifidi's Home Page]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://sourceforge.net/projects/rifidi/ Rifidi's Sourceforge Page]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://rifidi.googlecode.com Rifidi Source SVN]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.pramari.com Pramari's Website]<br />
</li><br />
</ul><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-left: 0.9em; margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">General Wiki Information</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[http://meta.wikimedia.org/wiki/Help:Contents User's Guide]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]<br />
</li><br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:wiki|browse more wiki Links...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
<br />
</div></div>Andreashttp://wiki.rifidi.net/index.php/Main_PageMain Page2008-04-15T01:18:12Z<p>Andreas: </p>
<hr />
<div>__NOTOC__<br />
<div style="width: 100%; margin-top: -0.2em;" id="mp"><br />
<div style="margin-right: 13.8em;"><br />
<div id="search" style="border-bottom: 1px solid rgb(255, 204, 102); margin-bottom: 0.9em; background-color: rgb(240, 247, 255); background-repeat: no-repeat; background-position: right top;"><br />
<br />
<div id="book" style="padding: 1em 0pt 0.6em; bakground-repeat: no-repeat background-position: 0% 20%;"><br />
<br />
<div style="text-align: center;"><br />
<h1 style="border: medium none ; margin: Opt; padding: Opt; font-size: 175%;"><br />
Welcome&nbsp;to&nbsp;the&nbsp;<b>RIFIDI Community Wiki</b></h1><br />
<p>[[RIFIDI]] is an open source [[RFID Environment Emulation]] tool.</p><br />
<p>'''Please find out how to [[Documentation Guidelines|contribute to the Wiki]] before you begin editing.'''</p><br />
<br />
</div><br />
<div style="clear: left; height: 1px; overflow: hidden;">&nbsp;</div><br />
</div><br />
</div><br />
<br />
<div style="float: left; clear: left; width: 50%;"><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<h2 style="border: 0pt none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Help for users</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[FAQ |Frequently Asked Questions]] <br />
</li> <br />
<li style="margin: 0.5em 0pt;"><br />
[[Emulator User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Designer User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Tag Streamer User's Guide]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Release Features]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Reader Guides]]<br />
</li><br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:userDoc|browse more user documents...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255);margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: 0pt none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Help for developers</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi roadmap|Rifidi Roadmap]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Documentation Guidelines|Contribute to the Wiki]] <br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:Source Code|Running Rifidi from Source]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Emulator documentation summary | Emulator Documentation]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[designer documentation summary | Designer Documentation]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[tag streamer documentation summary | Tag Streamer Documentation]]<br />
</li> <br />
<li style="margin: 0.5em 0pt;"><br />
[[Developer FAQ]]<br />
</li> <br />
<li syle = "margin 0.5em 0pt;"><br />
[[Style Guide]]<br />
</li> <br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:developerDoc|browse more developer documents...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Idea box</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:implementationIdeas|Implementation Ideas]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Rifidi:codingIdeas|Coding Ideas]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Useful Links]]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[[Eclipse Tips]]<br />
</li><br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:ideaBox| browse more ideas...]]</b><br />
</p><br />
</div><br />
</div><br />
</div><br />
<br />
<div style="width: 49.9%; float: left;"><br />
<div style="border: 1px solid rgb(198, 201, 255); margin-left: 0.9em; margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">Project Links</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[http://rifidi.org Rifidi's Home Page]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://sourceforge.net/projects/rifidi/ Rifidi's Sourceforge Page]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://rifidi.googlecode.com Rifidi Source SVN]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.pramari.com Pramari's Website]<br />
</li><br />
</ul><br />
</div><br />
</div><br />
<br />
<div style="border: 1px solid rgb(198, 201, 255); margin-left: 0.9em; margin-bottom: 0.9em; background-color: rgb(240, 247, 255);"><br />
<div style="padding: 0.6em;"><br />
<h2 style="border: medium none ; margin: 0pt; padding: 0pt; font-size: 130%; font-weight: bold;">General Wiki Information</h2><br />
<ul style="font-size: 95%; position: relative;"><br />
<li style="margin: 0.5em 0pt;"><br />
[http://meta.wikimedia.org/wiki/Help:Contents User's Guide]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]<br />
</li><br />
<li style="margin: 0.5em 0pt;"><br />
[http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]<br />
</li><br />
</ul><br />
<p style="border-top: 1px solid rgb(198, 201, 255); text-align: right; margin-bottom: 0pt; padding-top: 0.2em; margin-top: 0.8em;"><br />
<b>[[:Category:wiki|browse more wiki Links...]]</b><br />
</p><br />
</div><br />
</div><br />
<br />
<br />
</div></div>Andreashttp://wiki.rifidi.net/index.php/Designer_PackagesDesigner Packages2008-04-13T23:25:30Z<p>Andreas: </p>
<hr />
<div>Packages needed for to run the emulator from source:<br />
<br />
Packages from trunk:<br />
*org.rifidi.dependencies<br />
*org.rifidi.designer.library.basemodels<br />
*org.rifidi.designer.rcp<br />
*org.rifidi.designer.rcp.gpioeditor<br />
*org.rifidi.emulator<br />
*org.rifidi.emulator.reader.alien<br />
*org.rifidi.emulator.reader.awid<br />
*org.rifidi.emulator.reader.epc<br />
*org.rifidi.emulator.reader.llrp<br />
*org.rifidi.emulator.reader.symbol<br />
*org.rifidi.jmeswt<br />
*org.rifidi.log4j<br />
*org.rifidi.ui.common<br />
*org.rifidi.streamer<br />
*org.rifidi.streamer.xml<br />
*org.rifidi.services<br />
*org.rifidi.services.tags</div>Andreashttp://wiki.rifidi.net/index.php/Designer_PackagesDesigner Packages2008-04-13T23:24:43Z<p>Andreas: </p>
<hr />
<div>Packages needed for to run the emulator from source:<br />
<br />
Packages from trunk:<br />
*org.rifidi.dependencies<br />
*org.rifidi.designer.library.basemodels<br />
*org.rifidi.designer.rcp<br />
*org.rifidi.designer.rcp.gpioeditor<br />
*org.rifidi.emulator<br />
*org.rifidi.emulator.reader.alien<br />
*org.rifidi.emulator.reader.awid<br />
*org.rifidi.emulator.reader.epc<br />
*org.rifidi.emulator.reader.llrp<br />
*org.rifidi.emulator.reader.symbol<br />
*org.rifidi.jmeswt<br />
*org.rifidi.log4j<br />
*org.rifidi.ui.common<br />
*org.rifidi.streamer<br />
*org.rifidi.streamer.xml<br />
*org.rifidi.services</div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-13T21:30:03Z<p>Andreas: /* Scenarios */</p>
<hr />
<div>=Starting up Tag Streamer alpha 2.0=<br />
# Follow the [[Rifidi:Source_Code|instructions]] to download Rifidi Tag Streamer from source<br />
## Download the following [[Tag_Streamer_Packages|packages]]<br />
# Open up the Lauch Configuration wizard by going to run-><br />
#Create a new OSGI Framwork launch configuration<br />
<br />
= Use Case: Load Testing multiple readers one batch =<br />
<br />
== Scenarios ==<br />
The following scenario describes how the readers are located. In this special case all scenarios consist of only one reader. Because none of these readers have following readers the traveltime is 0.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarioSuite><br />
<scenario id="1"><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="2"><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="3"><br />
<pathItem><br />
<readerID>3</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="4"><br />
<pathItem><br />
<readerID>4</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="5"><br />
<pathItem><br />
<readerID>5</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarioSuite><br />
</pre><br />
<br />
== Components ==<br />
This file describes all the components the streamer should load. In this case we describe 5 LLRP Readers. Wich will be emulated by RifidiEmulator.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<componentSuite><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader1</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader2</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="3"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader3</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="4"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5087</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10104</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader4</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="5"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5088</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10104</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader5</readerName><br />
</reader><br />
</readerComponents><br />
</componentSuite><br />
</pre><br />
<br />
== Batch ==<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batchSuite><br />
<batch id="1"><br />
<waitAction><br />
<maxWaitTime>100</maxWaitTime><br />
<minWaitTime>200</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<tagAction><br />
<execDuration>200</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<regenerate>true</regenerate><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
</tagAction><br />
</batch><br />
</batchSuite><br />
</pre><br />
<br />
== LoadTestSuite == <br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnit><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnit><br />
<fileUnit><br />
<fileName>batches.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnit><br />
<fileUnit><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnit><br />
<testUnit iterations="5000"><br />
<waitAction><br />
<maxWaitTime>1000</maxWaitTime><br />
<minWaitTime>0000</minWaitTime><br />
<random>false</random><br />
</waitAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>1</scenarioID><br />
</batchAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>2</scenarioID><br />
</batchAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>3</scenarioID><br />
</batchAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>4</scenarioID><br />
</batchAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>5</scenarioID><br />
</batchAction><br />
</testUnit><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-13T21:28:42Z<p>Andreas: /* Components */</p>
<hr />
<div>=Starting up Tag Streamer alpha 2.0=<br />
# Follow the [[Rifidi:Source_Code|instructions]] to download Rifidi Tag Streamer from source<br />
## Download the following packages<br />
#<br />
<br />
= Use Case: Load Testing multiple readers one batch =<br />
<br />
== Scenarios ==<br />
The following scenario describes how the readers are located. In this special case all scenarios consist of only one reader.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarioSuite><br />
<scenario id="1"><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="2"><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="3"><br />
<pathItem><br />
<readerID>3</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="4"><br />
<pathItem><br />
<readerID>4</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="5"><br />
<pathItem><br />
<readerID>5</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarioSuite><br />
</pre><br />
<br />
== Components ==<br />
This file describes all the components the streamer should load. In this case we describe 5 LLRP Readers. Wich will be emulated by RifidiEmulator.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<componentSuite><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader1</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader2</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="3"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader3</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="4"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5087</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10104</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader4</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="5"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5088</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10104</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader5</readerName><br />
</reader><br />
</readerComponents><br />
</componentSuite><br />
</pre><br />
<br />
== Batch ==<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batchSuite><br />
<batch id="1"><br />
<waitAction><br />
<maxWaitTime>100</maxWaitTime><br />
<minWaitTime>200</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<tagAction><br />
<execDuration>200</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<regenerate>true</regenerate><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
</tagAction><br />
</batch><br />
</batchSuite><br />
</pre><br />
<br />
== LoadTestSuite == <br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnit><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnit><br />
<fileUnit><br />
<fileName>batches.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnit><br />
<fileUnit><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnit><br />
<testUnit iterations="5000"><br />
<waitAction><br />
<maxWaitTime>1000</maxWaitTime><br />
<minWaitTime>0000</minWaitTime><br />
<random>false</random><br />
</waitAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>1</scenarioID><br />
</batchAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>2</scenarioID><br />
</batchAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>3</scenarioID><br />
</batchAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>4</scenarioID><br />
</batchAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>5</scenarioID><br />
</batchAction><br />
</testUnit><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-13T21:27:38Z<p>Andreas: /* Scenarios */</p>
<hr />
<div>=Starting up Tag Streamer alpha 2.0=<br />
# Follow the [[Rifidi:Source_Code|instructions]] to download Rifidi Tag Streamer from source<br />
## Download the following packages<br />
#<br />
<br />
= Use Case: Load Testing multiple readers one batch =<br />
<br />
== Scenarios ==<br />
The following scenario describes how the readers are located. In this special case all scenarios consist of only one reader.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarioSuite><br />
<scenario id="1"><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="2"><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="3"><br />
<pathItem><br />
<readerID>3</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="4"><br />
<pathItem><br />
<readerID>4</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="5"><br />
<pathItem><br />
<readerID>5</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarioSuite><br />
</pre><br />
<br />
== Components ==<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<componentSuite><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader1</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader2</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="3"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader3</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="4"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5087</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10104</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader4</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="5"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5088</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10104</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader5</readerName><br />
</reader><br />
</readerComponents><br />
</componentSuite><br />
</pre><br />
<br />
== Batch ==<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batchSuite><br />
<batch id="1"><br />
<waitAction><br />
<maxWaitTime>100</maxWaitTime><br />
<minWaitTime>200</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<tagAction><br />
<execDuration>200</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<regenerate>true</regenerate><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
</tagAction><br />
</batch><br />
</batchSuite><br />
</pre><br />
<br />
== LoadTestSuite == <br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnit><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnit><br />
<fileUnit><br />
<fileName>batches.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnit><br />
<fileUnit><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnit><br />
<testUnit iterations="5000"><br />
<waitAction><br />
<maxWaitTime>1000</maxWaitTime><br />
<minWaitTime>0000</minWaitTime><br />
<random>false</random><br />
</waitAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>1</scenarioID><br />
</batchAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>2</scenarioID><br />
</batchAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>3</scenarioID><br />
</batchAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>4</scenarioID><br />
</batchAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>5</scenarioID><br />
</batchAction><br />
</testUnit><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-13T21:22:05Z<p>Andreas: /* LoadTestSuite */</p>
<hr />
<div>=Starting up Tag Streamer alpha 2.0=<br />
# Follow the [[Rifidi:Source_Code|instructions]] to download Rifidi Tag Streamer from source<br />
## Download the following packages<br />
#<br />
<br />
= Use Case: Load Testing multiple readers one batch =<br />
<br />
== Scenarios ==<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarioSuite><br />
<scenario id="1"><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="2"><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="3"><br />
<pathItem><br />
<readerID>3</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="4"><br />
<pathItem><br />
<readerID>4</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="5"><br />
<pathItem><br />
<readerID>5</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarioSuite><br />
</pre><br />
<br />
== Components ==<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<componentSuite><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader1</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader2</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="3"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader3</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="4"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5087</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10104</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader4</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="5"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5088</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10104</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader5</readerName><br />
</reader><br />
</readerComponents><br />
</componentSuite><br />
</pre><br />
<br />
== Batch ==<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batchSuite><br />
<batch id="1"><br />
<waitAction><br />
<maxWaitTime>100</maxWaitTime><br />
<minWaitTime>200</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<tagAction><br />
<execDuration>200</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<regenerate>true</regenerate><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
</tagAction><br />
</batch><br />
</batchSuite><br />
</pre><br />
<br />
== LoadTestSuite == <br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnit><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnit><br />
<fileUnit><br />
<fileName>batches.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnit><br />
<fileUnit><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnit><br />
<testUnit iterations="5000"><br />
<waitAction><br />
<maxWaitTime>1000</maxWaitTime><br />
<minWaitTime>0000</minWaitTime><br />
<random>false</random><br />
</waitAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>1</scenarioID><br />
</batchAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>2</scenarioID><br />
</batchAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>3</scenarioID><br />
</batchAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>4</scenarioID><br />
</batchAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>5</scenarioID><br />
</batchAction><br />
</testUnit><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-13T21:08:31Z<p>Andreas: /* Batch */</p>
<hr />
<div>=Starting up Tag Streamer alpha 2.0=<br />
# Follow the [[Rifidi:Source_Code|instructions]] to download Rifidi Tag Streamer from source<br />
## Download the following packages<br />
#<br />
<br />
= Use Case: Load Testing multiple readers one batch =<br />
<br />
== Scenarios ==<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarioSuite><br />
<scenario id="1"><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="2"><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="3"><br />
<pathItem><br />
<readerID>3</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="4"><br />
<pathItem><br />
<readerID>4</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="5"><br />
<pathItem><br />
<readerID>5</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarioSuite><br />
</pre><br />
<br />
== Components ==<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<componentSuite><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader1</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader2</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="3"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader3</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="4"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5087</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10104</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader4</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="5"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5088</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10104</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader5</readerName><br />
</reader><br />
</readerComponents><br />
</componentSuite><br />
</pre><br />
<br />
== Batch ==<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batchSuite><br />
<batch id="1"><br />
<waitAction><br />
<maxWaitTime>100</maxWaitTime><br />
<minWaitTime>200</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<tagAction><br />
<execDuration>200</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<regenerate>true</regenerate><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
</tagAction><br />
</batch><br />
</batchSuite><br />
</pre><br />
<br />
== LoadTestSuite == <br />
<br />
<pre><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-13T21:06:10Z<p>Andreas: /* Scenarios */</p>
<hr />
<div>=Starting up Tag Streamer alpha 2.0=<br />
# Follow the [[Rifidi:Source_Code|instructions]] to download Rifidi Tag Streamer from source<br />
## Download the following packages<br />
#<br />
<br />
= Use Case: Load Testing multiple readers one batch =<br />
<br />
== Scenarios ==<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarioSuite><br />
<scenario id="1"><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="2"><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="3"><br />
<pathItem><br />
<readerID>3</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="4"><br />
<pathItem><br />
<readerID>4</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="5"><br />
<pathItem><br />
<readerID>5</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarioSuite><br />
</pre><br />
<br />
== Components ==<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<componentSuite><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader1</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader2</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="3"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader3</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="4"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5087</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10104</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader4</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="5"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5088</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10104</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader5</readerName><br />
</reader><br />
</readerComponents><br />
</componentSuite><br />
</pre><br />
<br />
== Batch ==<br />
<br />
<pre><br />
</pre><br />
<br />
== LoadTestSuite == <br />
<br />
<pre><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-13T21:05:02Z<p>Andreas: /* Components */</p>
<hr />
<div>=Starting up Tag Streamer alpha 2.0=<br />
<br />
= Use Case: Load Testing multiple readers one batch =<br />
<br />
== Scenarios ==<br />
<br />
<pre><br />
</pre><br />
<br />
== Components ==<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<componentSuite><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader1</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader2</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="3"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader3</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="4"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5087</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10104</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader4</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="5"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5088</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10104</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName><br />
org.rifidi.emulator.reader.llrp.module.LLRPReaderModule<br />
</readerClassName><br />
<readerName>LLRPReader5</readerName><br />
</reader><br />
</readerComponents><br />
</componentSuite><br />
</pre><br />
<br />
== Batch ==<br />
<br />
<pre><br />
</pre><br />
<br />
== LoadTestSuite == <br />
<br />
<pre><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-12T18:30:30Z<p>Andreas: /* Scenarios */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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.<br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarioSuite><br />
<scenario id="1"><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario id="2"><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarioSuite><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<componentSuite><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader2</readerName><br />
</reader><br />
</readerComponents><br />
</componentSuite><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batchSuite><br />
<batch id="1"><br />
<waitAction><br />
<maxWaitTime>5000</maxWaitTime><br />
<minWaitTime>3000</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<tagAction><br />
<execDuration>2000</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<regenerate>false</regenerate><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
</tagAction><br />
<waitAction><br />
<maxWaitTime>2000</maxWaitTime><br />
<minWaitTime>0</minWaitTime><br />
<random>false</random><br />
</waitAction><br />
<gpiAction><br />
<port>1</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
</batchSuite><br />
</pre><br />
<br />
== LoadTestSuite == <br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnit><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnit><br />
<fileUnit><br />
<fileName>batches.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnit><br />
<fileUnit><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnit><br />
<testUnit iterations="10"><br />
<waitAction><br />
<maxWaitTime>5000</maxWaitTime><br />
<minWaitTime>3000</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>1</scenarioID><br />
</batchAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>2</scenarioID><br />
</batchAction><br />
<waitAction><br />
<maxWaitTime>5000</maxWaitTime><br />
<minWaitTime>3000</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>1</scenarioID><br />
</batchAction><br />
</testUnit><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-12T18:25:48Z<p>Andreas: /* LoadTestSuite */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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.<br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarioSuite><br />
<scenario id="1"><br />
<scenario><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</scenario><br />
</scenario><br />
<scenario id="2"><br />
<scenario><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</scenario><br />
</scenario><br />
</scenarioSuite><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<componentSuite><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader2</readerName><br />
</reader><br />
</readerComponents><br />
</componentSuite><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batchSuite><br />
<batch id="1"><br />
<waitAction><br />
<maxWaitTime>5000</maxWaitTime><br />
<minWaitTime>3000</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<tagAction><br />
<execDuration>2000</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<regenerate>false</regenerate><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
</tagAction><br />
<waitAction><br />
<maxWaitTime>2000</maxWaitTime><br />
<minWaitTime>0</minWaitTime><br />
<random>false</random><br />
</waitAction><br />
<gpiAction><br />
<port>1</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
</batchSuite><br />
</pre><br />
<br />
== LoadTestSuite == <br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnit><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnit><br />
<fileUnit><br />
<fileName>batches.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnit><br />
<fileUnit><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnit><br />
<testUnit iterations="10"><br />
<waitAction><br />
<maxWaitTime>5000</maxWaitTime><br />
<minWaitTime>3000</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>1</scenarioID><br />
</batchAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>2</scenarioID><br />
</batchAction><br />
<waitAction><br />
<maxWaitTime>5000</maxWaitTime><br />
<minWaitTime>3000</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>1</scenarioID><br />
</batchAction><br />
</testUnit><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-12T18:25:01Z<p>Andreas: /* LoadTestSuite */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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.<br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarioSuite><br />
<scenario id="1"><br />
<scenario><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</scenario><br />
</scenario><br />
<scenario id="2"><br />
<scenario><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</scenario><br />
</scenario><br />
</scenarioSuite><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<componentSuite><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader2</readerName><br />
</reader><br />
</readerComponents><br />
</componentSuite><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batchSuite><br />
<batch id="1"><br />
<waitAction><br />
<maxWaitTime>5000</maxWaitTime><br />
<minWaitTime>3000</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<tagAction><br />
<execDuration>2000</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<regenerate>false</regenerate><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
</tagAction><br />
<waitAction><br />
<maxWaitTime>2000</maxWaitTime><br />
<minWaitTime>0</minWaitTime><br />
<random>false</random><br />
</waitAction><br />
<gpiAction><br />
<port>1</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
</batchSuite><br />
</pre><br />
<br />
== LoadTestSuite == <br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnit><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnit><br />
<fileUnit><br />
<fileName>batches.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnit><br />
<fileUnit><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnit><br />
<testUnit iterations="10"><br />
<waitAction><br />
<maxWaitTime>5000</maxWaitTime><br />
<minWaitTime>3000</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>1</scenarioID><br />
</batchAction><br />
<batchAction><br />
<batchID>1</batchID><br />
<scenarioID>2</scenarioID><br />
</batchAction><br />
</testUnit><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-12T03:34:05Z<p>Andreas: /* Components */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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.<br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarioSuite><br />
<scenario id="1"><br />
<scenario><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</scenario><br />
</scenario><br />
<scenario id="2"><br />
<scenario><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</scenario><br />
</scenario><br />
</scenarioSuite><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<componentSuite><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader2</readerName><br />
</reader><br />
</readerComponents><br />
</componentSuite><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batchSuite><br />
<batch id="1"><br />
<waitAction><br />
<maxWaitTime>5000</maxWaitTime><br />
<minWaitTime>3000</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<tagAction><br />
<execDuration>2000</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<regenerate>false</regenerate><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
</tagAction><br />
<waitAction><br />
<maxWaitTime>2000</maxWaitTime><br />
<minWaitTime>0</minWaitTime><br />
<random>false</random><br />
</waitAction><br />
<gpiAction><br />
<port>1</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
</batchSuite><br />
</pre><br />
<br />
== LoadTestSuite == <br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnits><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>batch.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnits><br />
<testSuite iterate="10"><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>2</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>3</scenario><br />
</batchAction><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
</testSuite><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-12T03:31:55Z<p>Andreas: /* Components */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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.<br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarioSuite><br />
<scenario id="1"><br />
<scenario><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</scenario><br />
</scenario><br />
<scenario id="2"><br />
<scenario><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</scenario><br />
</scenario><br />
</scenarioSuite><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<componentSuite><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
</componentSuite><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batchSuite><br />
<batch id="1"><br />
<waitAction><br />
<maxWaitTime>5000</maxWaitTime><br />
<minWaitTime>3000</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<tagAction><br />
<execDuration>2000</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<regenerate>false</regenerate><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
</tagAction><br />
<waitAction><br />
<maxWaitTime>2000</maxWaitTime><br />
<minWaitTime>0</minWaitTime><br />
<random>false</random><br />
</waitAction><br />
<gpiAction><br />
<port>1</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
</batchSuite><br />
</pre><br />
<br />
== LoadTestSuite == <br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnits><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>batch.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnits><br />
<testSuite iterate="10"><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>2</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>3</scenario><br />
</batchAction><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
</testSuite><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-11T19:54:36Z<p>Andreas: /* Scenarios */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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.<br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarioSuite><br />
<scenario id="1"><br />
<scenario><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</scenario><br />
</scenario><br />
<scenario id="2"><br />
<scenario><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</scenario><br />
</scenario><br />
</scenarioSuite><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<components><br />
<readerComponents id="0"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
</components><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batchSuite><br />
<batch id="1"><br />
<waitAction><br />
<maxWaitTime>5000</maxWaitTime><br />
<minWaitTime>3000</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<tagAction><br />
<execDuration>2000</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<regenerate>false</regenerate><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
</tagAction><br />
<waitAction><br />
<maxWaitTime>2000</maxWaitTime><br />
<minWaitTime>0</minWaitTime><br />
<random>false</random><br />
</waitAction><br />
<gpiAction><br />
<port>1</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
</batchSuite><br />
</pre><br />
<br />
== LoadTestSuite == <br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnits><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>batch.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnits><br />
<testSuite iterate="10"><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>2</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>3</scenario><br />
</batchAction><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
</testSuite><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-11T19:53:21Z<p>Andreas: /* Scenarios */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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.<br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarioSuite><br />
<scenario id="1"><br />
<pathItems><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItems><br />
</scenario><br />
<scenario id="2"><br />
<pathItems><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItems><br />
</scenario><br />
</scenarioSuite><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<components><br />
<readerComponents id="0"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
</components><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batchSuite><br />
<batch id="1"><br />
<waitAction><br />
<maxWaitTime>5000</maxWaitTime><br />
<minWaitTime>3000</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<tagAction><br />
<execDuration>2000</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<regenerate>false</regenerate><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
</tagAction><br />
<waitAction><br />
<maxWaitTime>2000</maxWaitTime><br />
<minWaitTime>0</minWaitTime><br />
<random>false</random><br />
</waitAction><br />
<gpiAction><br />
<port>1</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
</batchSuite><br />
</pre><br />
<br />
== LoadTestSuite == <br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnits><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>batch.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnits><br />
<testSuite iterate="10"><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>2</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>3</scenario><br />
</batchAction><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
</testSuite><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-11T19:49:16Z<p>Andreas: /* Batch */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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.<br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarios><br />
<scenario><br />
<id>1</id><br />
<pathItem><br />
<readerID>0</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>2</id><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>3</id><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarios><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<components><br />
<readerComponents id="0"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
</components><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batchSuite><br />
<batch id="1"><br />
<waitAction><br />
<maxWaitTime>5000</maxWaitTime><br />
<minWaitTime>3000</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<tagAction><br />
<execDuration>2000</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<regenerate>false</regenerate><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
</tagAction><br />
<waitAction><br />
<maxWaitTime>2000</maxWaitTime><br />
<minWaitTime>0</minWaitTime><br />
<random>false</random><br />
</waitAction><br />
<gpiAction><br />
<port>1</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
</batchSuite><br />
</pre><br />
<br />
== LoadTestSuite == <br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnits><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>batch.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnits><br />
<testSuite iterate="10"><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>2</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>3</scenario><br />
</batchAction><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
</testSuite><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-11T17:11:30Z<p>Andreas: /* Batch */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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.<br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarios><br />
<scenario><br />
<id>1</id><br />
<pathItem><br />
<readerID>0</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>2</id><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>3</id><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarios><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<components><br />
<readerComponents id="0"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
</components><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batch id="1"><br />
<waitAction><br />
<maxWaitTime>0</maxWaitTime><br />
<minWaitTime>1000</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<tagAction><br />
<execDuration>200</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<regenerate>false</regenerate><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
</tagAction><br />
<waitAction><br />
<maxWaitTime>2000</maxWaitTime><br />
<minWaitTime>1000</minWaitTime><br />
<random>false</random><br />
</waitAction><br />
<gpiAction><br />
<port>0</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
<br />
</pre><br />
<br />
== LoadTestSuite == <br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnits><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>batch.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnits><br />
<testSuite iterate="10"><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>2</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>3</scenario><br />
</batchAction><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
</testSuite><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-11T17:11:21Z<p>Andreas: /* Batch */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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.<br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarios><br />
<scenario><br />
<id>1</id><br />
<pathItem><br />
<readerID>0</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>2</id><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>3</id><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarios><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<components><br />
<readerComponents id="0"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
</components><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batch id="1"><br />
<waitAction><br />
<maxWaitTime>0</maxWaitTime><br />
<minWaitTime>1000</minWaitTime><br />
<random>true</random><br />
</waitAction><br />
<tagAction><br />
<execDuration>200</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<regenerate>false</regenerate><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
</tagAction><br />
<waitAction><br />
<maxWaitTime>2000</maxWaitTime><br />
<minWaitTime>1000</minWaitTime><br />
<random>false</random><br />
</waitAction><br />
<gpiAction><br />
<port>0</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
<br />
</pre><br />
<br />
== LoadTestSuite == <br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnits><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>batch.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnits><br />
<testSuite iterate="10"><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>2</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>3</scenario><br />
</batchAction><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
</testSuite><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-08T22:11:33Z<p>Andreas: /* LoadTestSuite */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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.<br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarios><br />
<scenario><br />
<id>1</id><br />
<pathItem><br />
<readerID>0</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>2</id><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>3</id><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarios><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<components><br />
<readerComponents id="0"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
</components><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batch id="1"><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<tagAction><br />
<execDuration>200</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
<regenerate>false</regenerate><br />
</tagAction><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<gpiAction><br />
<port>0</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
</pre><br />
<br />
== LoadTestSuite == <br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnits><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>batch.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnits><br />
<testSuite iterate="10"><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>2</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>3</scenario><br />
</batchAction><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
</testSuite><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-08T22:10:37Z<p>Andreas: /* Batch */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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.<br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarios><br />
<scenario><br />
<id>1</id><br />
<pathItem><br />
<readerID>0</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>2</id><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>3</id><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarios><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<components><br />
<readerComponents id="0"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
</components><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batch id="1"><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<tagAction><br />
<execDuration>200</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
<regenerate>false</regenerate><br />
</tagAction><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<gpiAction><br />
<port>0</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
</pre><br />
<br />
== LoadTestSuite == <br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnits><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>batch.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnits><br />
<testSuite iterate="10"><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>2</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>3</scenario><br />
</batchAction><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
</testSuite><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-08T22:09:20Z<p>Andreas: /* LoadTestSuite */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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.<br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarios><br />
<scenario><br />
<id>1</id><br />
<pathItem><br />
<readerID>0</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>2</id><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>3</id><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarios><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<components><br />
<readerComponents id="0"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
</components><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batch id="1"><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<tagAction><br />
<execDuration>200</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
<regenerate>false</regenerate><br />
</tagAction><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<gpiAction><br />
<port>0</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
</pre><br />
<br />
== 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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnits><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>batch.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnits><br />
<testSuite iterate="10"><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>2</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>3</scenario><br />
</batchAction><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
</testSuite><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-08T22:08:03Z<p>Andreas: /* Batch */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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.<br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarios><br />
<scenario><br />
<id>1</id><br />
<pathItem><br />
<readerID>0</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>2</id><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>3</id><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarios><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<components><br />
<readerComponents id="0"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
</components><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batch id="1"><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<tagAction><br />
<execDuration>200</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
<regenerate>false</regenerate><br />
</tagAction><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<gpiAction><br />
<port>0</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
</pre><br />
<br />
== LoadTestSuite ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnits><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>batch.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnits><br />
<testSuite iterate="10"><br />
<waitAction>1000</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>2</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>3</scenario><br />
</batchAction><br />
<waitAction>2000</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
</testSuite><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-08T22:06:41Z<p>Andreas: /* Batch */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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.<br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarios><br />
<scenario><br />
<id>1</id><br />
<pathItem><br />
<readerID>0</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>2</id><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>3</id><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarios><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<components><br />
<readerComponents id="0"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
</components><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batch id="1"><br />
<waitAction><br />
<isRandom>true</isRandom><br />
<minWaitTime>100</minWaitTime><br />
<maxWaitTime>200</maxWaitTime><br />
</waitAction><br />
<tagAction><br />
<execDuration>200</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
<regenerate>false</regenerate><br />
</tagAction><br />
<waitAction><br />
<waitTime>100</waitTime><br />
</waitAction><br />
<gpiAction><br />
<port>0</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
</pre><br />
<br />
== LoadTestSuite ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnits><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>batch.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnits><br />
<testSuite iterate="10"><br />
<waitAction>1000</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>2</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>3</scenario><br />
</batchAction><br />
<waitAction>2000</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
</testSuite><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-08T21:41:03Z<p>Andreas: /* LoadTestSuite */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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.<br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarios><br />
<scenario><br />
<id>1</id><br />
<pathItem><br />
<readerID>0</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>2</id><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>3</id><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarios><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<components><br />
<readerComponents id="0"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
</components><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batch id="1"><br />
<waitAction><br />
<waitTime>100</waitTime><br />
</waitAction><br />
<tagAction><br />
<execDuration>200</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
<regenerate>false</regenerate><br />
</tagAction><br />
<waitAction><br />
<waitTime>100</waitTime><br />
</waitAction><br />
<gpiAction><br />
<port>0</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
</pre><br />
<br />
== LoadTestSuite ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnits><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>batch.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnits><br />
<testSuite iterate="10"><br />
<waitAction>1000</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>2</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>3</scenario><br />
</batchAction><br />
<waitAction>2000</waitAction><br />
<batchAction><br />
<batch>1</batch><br />
<scenario>2</scenario><br />
</batchAction><br />
</testSuite><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-06T21:10:14Z<p>Andreas: /* LoadTestSuite */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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.<br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarios><br />
<scenario><br />
<id>1</id><br />
<pathItem><br />
<readerID>0</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>2</id><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>3</id><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarios><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<components><br />
<readerComponents id="0"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
</components><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batch id="1"><br />
<waitAction><br />
<waitTime>100</waitTime><br />
</waitAction><br />
<tagAction><br />
<execDuration>200</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
<regenerate>false</regenerate><br />
</tagAction><br />
<waitAction><br />
<waitTime>100</waitTime><br />
</waitAction><br />
<gpiAction><br />
<port>0</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
</pre><br />
<br />
== LoadTestSuite ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnits><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>batch.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnits><br />
<testUnit><br />
<loop>40</loop><br />
<batchID>1</batchID><br />
<rampTime>1000</rampTime><br />
<scenarios><br />
<id>1</id><br />
<id>2</id><br />
<id>3</id><br />
</scenarios><br />
</testUnit><br />
<testUnit><br />
<batchID>1</batchID><br />
<rampTime>2000</rampTime><br />
<count>10</count><br />
<scenarios><br />
<id>1</id><br />
</scenarios><br />
</testUnit><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-06T20:13:05Z<p>Andreas: /* Use Case: Load Testing multiple readers one batch */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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.<br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarios><br />
<scenario><br />
<id>1</id><br />
<pathItem><br />
<readerID>0</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>2</id><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>3</id><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarios><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<components><br />
<readerComponents id="0"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
</components><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batch id="1"><br />
<waitAction><br />
<waitTime>100</waitTime><br />
</waitAction><br />
<tagAction><br />
<execDuration>200</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
<regenerate>false</regenerate><br />
</tagAction><br />
<waitAction><br />
<waitTime>100</waitTime><br />
</waitAction><br />
<gpiAction><br />
<port>0</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
</pre><br />
<br />
== LoadTestSuite ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnits><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>batch.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnits><br />
<testUnit><br />
<batchID>1</batchID><br />
<rampTime>1000</rampTime><br />
<count>40</count><br />
<scenarios><br />
<id>1</id><br />
<id>2</id><br />
<id>3</id><br />
</scenarios><br />
</testUnit><br />
<testUnit><br />
<batchID>1</batchID><br />
<rampTime>2000</rampTime><br />
<count>10</count><br />
<scenarios><br />
<id>1</id><br />
</scenarios><br />
</testUnit><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-06T20:11:31Z<p>Andreas: /* Use Case: Load Testing multiple readers one batch */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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. After a batch entered the scenario it will execute it's actions on each of the patchItems and then move further to the next PathItem. In this case each scenario only has one pathItem which is a reference to a reader.<br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarios><br />
<scenario><br />
<id>1</id><br />
<pathItem><br />
<readerID>0</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>2</id><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>3</id><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarios><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<components><br />
<readerComponents id="0"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
</components><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batch id="1"><br />
<waitAction><br />
<waitTime>100</waitTime><br />
</waitAction><br />
<tagAction><br />
<execDuration>200</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
<regenerate>false</regenerate><br />
</tagAction><br />
<waitAction><br />
<waitTime>100</waitTime><br />
</waitAction><br />
<gpiAction><br />
<port>0</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
</pre><br />
<br />
== LoadTestSuite ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnits><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>batch.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnits><br />
<testUnit><br />
<batchID>1</batchID><br />
<rampTime>1000</rampTime><br />
<count>40</count><br />
<scenarios><br />
<id>1</id><br />
<id>2</id><br />
<id>3</id><br />
</scenarios><br />
</testUnit><br />
<testUnit><br />
<batchID>1</batchID><br />
<rampTime>2000</rampTime><br />
<count>10</count><br />
<scenarios><br />
<id>1</id><br />
</scenarios><br />
</testUnit><br />
</loadTestSuite><br />
</pre></div>Andreashttp://wiki.rifidi.net/index.php/TagStreamerUseCaseScenariosTagStreamerUseCaseScenarios2008-02-06T20:09:04Z<p>Andreas: /* Use Case: Load Testing multiple readers one batch */</p>
<hr />
<div>= Use Case: Load Testing multiple readers one batch =<br />
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. After a batch entered the scenario it will execute it's actions on each of the pathUnits. In this case each scenario only has one pathItem which is a reference to a reader. <br />
<br />
== Scenarios ==<br />
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.<br />
<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<scenarios><br />
<scenario><br />
<id>1</id><br />
<pathItem><br />
<readerID>0</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>2</id><br />
<pathItem><br />
<readerID>1</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
<scenario><br />
<id>3</id><br />
<pathItem><br />
<readerID>2</readerID><br />
<travelTime>0</travelTime><br />
</pathItem><br />
</scenario><br />
</scenarios><br />
</pre><br />
<br />
== Components ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<components><br />
<readerComponents id="0"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5084</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10101</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="1"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5085</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10102</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
<readerComponents id="2"><br />
<reader><br />
<numAntennas>1</numAntennas><br />
<numGPIs>4</numGPIs><br />
<numGPOs>4</numGPOs><br />
<propertiesMap><br />
<entry><br />
<key>llrp_inet_address</key><br />
<value>127.0.0.1:5086</value><br />
</entry><br />
<entry><br />
<key>inet_address</key><br />
<value>127.0.0.1:10103</value><br />
</entry><br />
<entry><br />
<key>servermode</key><br />
<value>true</value><br />
</entry><br />
</propertiesMap><br />
<readerClassName>org.rifidi.emulator.reader.llrp.module.LLRPReaderModule</readerClassName><br />
<readerName>LLRPReader</readerName><br />
</reader><br />
</readerComponents><br />
</components><br />
</pre><br />
<br />
== Batch ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<batch id="1"><br />
<waitAction><br />
<waitTime>100</waitTime><br />
</waitAction><br />
<tagAction><br />
<execDuration>200</execDuration><br />
<number>20</number><br />
<prefix>eef</prefix><br />
<tagGen>GEN2</tagGen><br />
<tagType>CustomEPC96</tagType><br />
<regenerate>false</regenerate><br />
</tagAction><br />
<waitAction><br />
<waitTime>100</waitTime><br />
</waitAction><br />
<gpiAction><br />
<port>0</port><br />
<signal>true</signal><br />
</gpiAction><br />
</batch><br />
</pre><br />
<br />
== LoadTestSuite ==<br />
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.<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><br />
<loadTestSuite><br />
<fileUnits><br />
<fileName>scenario.xml</fileName><br />
<fileType>SCENARIO</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>batch.xml</fileName><br />
<fileType>BATCH</fileType><br />
</fileUnits><br />
<fileUnits><br />
<fileName>components.xml</fileName><br />
<fileType>COMPONENT</fileType><br />
</fileUnits><br />
<testUnit><br />
<batchID>1</batchID><br />
<rampTime>1000</rampTime><br />
<count>40</count><br />
<scenarios><br />
<id>1</id><br />
<id>2</id><br />
<id>3</id><br />
</scenarios><br />
</testUnit><br />
<testUnit><br />
<batchID>1</batchID><br />
<rampTime>2000</rampTime><br />
<count>10</count><br />
<scenarios><br />
<id>1</id><br />
</scenarios><br />
</testUnit><br />
</loadTestSuite><br />
</pre></div>Andreas