RifidiWiki - User contributions [en]

How to Package Rifidi Edge

2014-11-04T04:15:22Z

Matt:

=Introduction=
These are the prerequisites and steps for packaing the Rifidi Edge SDK, Deb, Server Only Zip and Windows Installer

It is best to export the versions in this order for release:
1. Deb
2. Server only
3. Windows Installer
4. SDK

You will need a windows and linux machine (or virtual machine) to export and test. Dropbox is invaluable for this purpose, as it allows you to easily share the files across different machines.

=Deb=
==Prerequisites==
1. You need to be on linux to build the Deb.
2. The docs, jars, bundles,info, rifidiserver.ini and rifidi-server linux executable must all be correct before release. Check them all before and after you export the deb or you will need to export it again.
3. bundles.info is very easy to get wrong. Test the deb as soon as you export it for the first time, and make sure all the bundles you are expecting to show up show up with the "ss" command. Debug and fix any that aren't working, fix the bundles.info in the SDK and rebuild.
4. Make sure the version numbers are incremented in "SDK/version.txt", "SDK/rifidi/usr/local/sbin/rifidi/version.txt", and "SDK/rifidi/debian/DEBIAN/control".
5. Make sure all your changes are checked in, as building the deb requires disconnecting the SDK from SVN.
==Steps==
1. Make sure you have a new, fully updated SDK in your workspace.
2. Disconnect the SDK project from SVN. Delete the SVN metadata. If all the exported documents are way too big, you forgot to do this step.
3. Navigate to the SDK folder in the terminal and type 'sh build.sh'. DO NOT use sudo.
4. The deb will show up in sdk/rifidi/debian/Debian-packages
5. Immediately move the deb out of the Debian-packages and install it via "sudo dpkg -i (deb)". Test it and make sure everything is correct. If you need to change anything, you'll probably need to hook up the SDK to SVN again (or delete and re-download it from SVN).
=Server Only Zip=
==Prerequisites==
1. You'll need a debian package you are satisfied is working correctly to make the zip.
==Steps==
1. Open the deb with an archive tool and extract the "rifidi" folder.
2. Zip up the folder to a 7zip file with the name "RifidiEdge-XXX-server_only.7z", where XXX is the version number, like "3.1.0".
=Windows Installer=
==Prerequisites==
1. You need to be on windows to make the windows installer.
2. You need the "/install" folder from the edge SVN.
3. You need Inno Setup.
4. You'll need the "client" folder from a previous windows install, and the contents of the zip file in a folder called "server". Put them in the same folder, and modify the inno file in the install directory to point to that folder. Also make sure the inno install file is pointed at the installer assets, and make sure the version in the inno install file is correct.
==Steps==
1. Once the inno file is pointed at the correct place, compile and build the Inno file from Inno Setup.
2. Test the installer and make sure everything is working.
=SDK=
==Prerequisites==
1. You need the SDK folder from when you built the deb.
2. Make sure the debian file itself isn't in the SDK, as it will make the SDK much too large.
3. Make sure you don't have anything non-standard in the RifidiHome folder, and make sure the launch file and launch file VM args are correct.
4. Make sure the SDK is disconnected from SVN.

==Steps==
1. Make sure the SDK is working, then zip it up. It is ready for release.

How to Package Rifidi Edge

2014-11-04T03:46:02Z

Matt:

=Introduction=
These are the prerequisites and steps for packaing the Rifidi Edge SDK, Deb, Server Only Zip and Windows Installer

It is best to export the versions in this order for release:
1. Deb
2. Server only
3. Windows Installer
4. SDK

You will need a windows and linux machine (or virtual machine) to export and test. Dropbox is invaluable for this purpose, as it allows you to easily share the files across different machines.

=Deb=
==Prerequisites==
1. You need to be on linux to build the Deb.
2. The docs, jars, bundles,info, rifidiserver.ini and rifidi-server linux executable must all be correct before release. Check them all before and after you export the deb or you will need to export it again.
3. bundles.info is very easy to get wrong. Test the deb as soon as you export it for the first time, and make sure all the bundles you are expecting to show up show up with the "ss" command. Debug and fix any that aren't working, fix the bundles.info in the SDK and rebuild.
4. Make sure the version numbers are incremented in "SDK/version.txt", "SDK/rifidi/usr/local/sbin/rifidi/version.txt", and "SDK/rifidi/debian/DEBIAN/control".
5. Make sure all your changes are checked in, as building the deb requires disconnecting the SDK from SVN.
==Steps==
1. Make sure you have a new, fully updated SDK in your workspace.
2. Disconnect the SDK project from SVN. Delete the SVN metadata. If all the exported documents are way too big, you forgot to do this step.
3. Navigate to the SDK folder in the terminal and type 'sh build.sh'. DO NOT use sudo.
4. The deb will show up in sdk/rifidi/debian/Debian-packages
5. Immediately move the deb out of the Debian-packages and install it via "sudo dpkg -i (deb)". Test it and make sure everything is correct. If you need to change anything, you'll probably need to hook up the SDK to SVN again (or delete and re-download it from SVN).
=Server Only Zip=
==Prerequisites==
1. You'll need a debian package you are satisfied is working correctly to make the zip.
==Steps==
1. Open the deb with an archive tool and extract the "rifidi" folder.
2. Zip up the folder to a 7zip file with the name "RifidiEdge-XXX-server_only.7z", where XXX is the version number, like "3.1.0".
=Windows Installer=
==Prerequisites==
1. You need to be on windows to make the windows installer.
2. You need the installer
==Steps==
=SDK=
==Prerequisites==
All you need is a workspace with the SDK
==Steps==

How to Package Rifidi Edge

2014-11-04T03:36:10Z

Matt:

How to Package Rifidi Edge

2014-11-04T03:08:00Z

Matt:

How to Package Rifidi Edge

2014-11-04T02:54:38Z

Matt: /* Introduction */

=Introduction=
These are the prerequisites and steps for packaing the Rifidi Edge SDK, Deb, Server Only Zip and Windows Installer

=SDK=
==Prerequisites==
==Steps==
=Deb=
==Prerequisites==
==Steps==
=Server Only Zip=
==Prerequisites==
==Steps==
=Windows Installer=
==Prerequisites==
==Steps==

LLRP Tag Encoding

2014-10-26T17:33:33Z

Matt: /* LLRP Encode Single Shot Commands */

=LLRP Tag Encoding Options=
==LLRP Encode Command==
LLRP Encode Command is used to encode a new Tag with the following operations:
<pre>
Order: operationCode
1 - LLRPAccessPasswordWrite
2 - LLRPEPCWrite
3 - LLRPKillPasswordWrite
4 - LLRPEPCLock
5 - LLRPKillPasswordLock
6 - LLRPAccessPasswordLock
</pre>
What are EPC, Kill Password, Access Password:
*EPC is the GEN2 EPC ID for a Tag
*Kill Password is used to set the password necessary to kill/destroy a tag for future use (by default there is no password (value(0))
*Access Password is used to perform tag writes such as EPC, Kill Password, Access Password (by default there is no password (value(0))
*C1G2Write and C1G2Lock are the LLRP Access Spec operations used

*Command
llrpencode/{readerID}/{sessionID}/{tag}- Performs all LLRP Encoding operations for a New RFID Tag

*Example
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666
*Prerequisites
# Only one tag can be present(This is Not a Bulk encoding operation)
# Must be a LLRP reader
# Must be a valid readerID and sessionID
# tag must be evenly divide by 4 (word in hex) and tag must be able to support length
# access password and kill password must be evenly divide by 4 (4 or 8 characters/1 or 2 words) or 0
# Only one encoding session per reader can be active at one time

===Global Settings via Edge_Server_Configuration===
Global Properties below need to be set for LLRP encode based on ones requirements
*Note: All MQTT (if set), timeout tagmask and epctarget always come form Global Variables
*Note: These are set globally using the Rifidi Edge Configuration [[Edge_Server_Configuration]]
<pre>
-Dorg.rifidi.llrp.encode.targetepc=000000000000000000000000 - (Hex Value) Sets the EPC Tag Data to perform operation on (Must be even block of 4 charaters and size depends on Tag - typical is 24 characters) - default if not set is 000000000000000000000000
-Dorg.rifidi.llrp.encode.tagmask=000000000000000000000000 - (Hex Value) Sets the Tag Mask to perform operation on (0 is wildcard match, F is Exact Match) (Must be even block of 4 characters and size depends on Tag - typical is 24 characters) - default if not set is 000000000000000000000000
-Dorg.rifidi.llrp.encode.timeout=5000 - Sets the duration of time to attempt operation (O is infinite until operation occurs, set in milliseconds)
-Dorg.rifidi.llrp.encode.accesspwd=0 - Access Password (Hex Value) (8 Characters or value of 0) - default if not set is 0
-Dorg.rifidi.llrp.encode.oldaccesspwd=0 - Old Access Password (Hex Value) (8 Characters or value of 0) - default if not set is 0 Note: used when setting new access password
-Dorg.rifidi.llrp.encode.killpwd=0 - Kill Password (Hex Value) (8 Characters or value of 0) - default if not set is 0
-Dorg.rifidi.llrp.encode.killpwdlockprivilege=Read_Write - If Set Performs a Kill Password Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) - default if not set is Read_Write
-Dorg.rifidi.llrp.encode.accesspwdlockprivilege=Read_Write - If Set Performs a Access Password Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) default if not set is Read_Write
-Dorg.rifidi.llrp.encode.epclockprivilege=Read_Write - If Set Performs a EPC Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) - default if not set is Read_Write
-Dorg.rifidi.llrp.encode.mqttbroker -- mqtt broker url (if set, received response of encode operation is posted to this queue in asynchronous mode). Mqttqos and mqttclientid must be set too in order to post to queue
-Dorg.rifidi.llrp.encode.mqttqos -- Quality of service level for mqtt, example: 2
-Dorg.rifidi.llrp.encode.mqttclientid -- Client id to publish messages on queue

</pre>

Note: These are optional Global variables for MQTT. If these are set then llrpencode command operations response to sent asynchronously to a topic
*topic naming convention {readerId}/encode with result of encoding operations

<pre>
-Dorg.rifidi.llrp.encode.mqttqos=2
-Dorg.rifidi.llrp.encode.mqttbroker=tcp://localhost:1883
-Dorg.rifidi.llrp.encode.mqttclientid=llrpEncodeId
</pre>

===Encode Response===

Response: Success
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Success</message>
</response>
</pre>

Response: Fail
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Fail</message>
<Description> LLRP Message Returned goes here such as Tag mask and Tag data not matching - such</Description>
</response>

Note: Some types of Fail responses could be
# More than one tag
# Not a LLLRP reader
# Not a valid session
# Invalid access spec request
# Encoding session already active

</pre>

===Encode Operations Response===
If MQTT Variables defined Globally (above) then operations result response will be sent to MQTT topic
*Topic naming convention: {readerID}/encode

Success Message
<pre>

<encodeMessage>
<status>Success</Status>
</encodeMessage>
</pre>
Fail Message
<pre>

<encodeMessage>
<status>Fail</status>
<operationList>
<operation>LLRPEPCWrite:Sucess</operation>
<operation>LLRPKillPasswordWrite:Sucess</operation>
<operation>LLRPAccessPasswordWrite:Sucess</operation>
<operation>LLRPEPCLock:No_Response_From_Tag</operation>
<operation>LLRPKillPaswordLock: Success</operation>
<operation>LLRPAccessPaswordLock: Success</operation>
</operationList>
</encodeMessage>
</pre>

Full List of Return Failure Codes:
<pre>

Insufficient_Power

No_Response_From_Tag

Nonspecific_Reader_Error

Nonspecific_Tag_Error

Tag_Memory_Locked_Error

Tag_Memory_Overrun_Error
</pre>

==LLRP Encode Single Shot Commands==
These are used to perform single operations and override Global properties therefore all values must be supplied in request
Note: All MQTT (if set), timeout tagmask and epctarget always come form Global Variables
*Command
/llrpencode/{readerID}/{sessionID}/{tag}/{operationCode}/{properties}

List of operationCodes
LLRPEPCWrite
LLRPKillPasswordWrite
LLRPAccessPasswordWrite
LLRPEPCLock
LLRPKillPasswordLock
LLRPAccessPasswordLock
*Example LLRPECWrite - Used to Write a EPC ID
http://localhost:8111/llrpencode/LLRP_1/1/000000000001111111111268/LLRPEPCWrite/accesspwd=12345678

*Example LLRPKillPasswordWrite - Used to Write a Kill Password
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPKillPasswordWrite/accesspwd=12345678;killpwd=87654321

*Example LLRPAccessPasswordWrite - Used to Write a Access Password
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPAccessPasswordWrite/oldaccesspwd=12345678;accesspwd=98765432

*Example LLRPEPCLock - Set EPC Lock Priveledge
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPEPCLock/accesspwd=98765432;privilege=Read_Write

*Example LLRPKillPasswordLock - Set Kill Password Lock Privilege
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPKillPasswordLock/accesspwd=98765432;privilege=Read_Write

*Example LLRPAccessPasswordLock - Set Access Password Lock Privilege
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPAccessPasswordLock/accesspwd=98765432;privilege=Read_Write
===Single Shot Encode Operations Response===
If MQTT Variables defined Globally (above) then operations result response will be sent to MQTT topic otherwise response is synchronous
*Topic naming convention: {readerID}/encode

===Encode Single Shot Response===

Response: Success
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Success</message>
</response>
</pre>

Response: Fail
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Fail</message>
<Description> LLRP Message Returned goes here such as Tag mask and Tag data not matching - such</Description>
</response>

Note: Some types of Fail responses could be
# More than one tag
# Not a LLLRP reader
# Not a valid session
# Invalid access spec request
# Encoding session already active

</pre>

Success Message
<pre>

<encodeMessage>
<status>Success</Status>
</encodeMessage>
</pre>
Fail Message
<pre>

<encodeMessage>
<status>Fail</status>
<operationList>
<operation>LLRPEPCLock:No_Response_From_Tag</operation>
</operationList>
</encodeMessage>
</pre>

Full List of Return Failure Codes:
<pre>

Insufficient_Power

No_Response_From_Tag

Nonspecific_Reader_Error

Nonspecific_Tag_Error

Tag_Memory_Locked_Error

Tag_Memory_Overrun_Error
</pre>

LLRP Tag Encoding

2014-10-26T17:33:01Z

Matt: /* LLRP Encode Single Shot Commands */

=LLRP Tag Encoding Options=
==LLRP Encode Command==
LLRP Encode Command is used to encode a new Tag with the following operations:
<pre>
Order: operationCode
1 - LLRPAccessPasswordWrite
2 - LLRPEPCWrite
3 - LLRPKillPasswordWrite
4 - LLRPEPCLock
5 - LLRPKillPasswordLock
6 - LLRPAccessPasswordLock
</pre>
What are EPC, Kill Password, Access Password:
*EPC is the GEN2 EPC ID for a Tag
*Kill Password is used to set the password necessary to kill/destroy a tag for future use (by default there is no password (value(0))
*Access Password is used to perform tag writes such as EPC, Kill Password, Access Password (by default there is no password (value(0))
*C1G2Write and C1G2Lock are the LLRP Access Spec operations used

*Command
llrpencode/{readerID}/{sessionID}/{tag}- Performs all LLRP Encoding operations for a New RFID Tag

*Example
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666
*Prerequisites
# Only one tag can be present(This is Not a Bulk encoding operation)
# Must be a LLRP reader
# Must be a valid readerID and sessionID
# tag must be evenly divide by 4 (word in hex) and tag must be able to support length
# access password and kill password must be evenly divide by 4 (4 or 8 characters/1 or 2 words) or 0
# Only one encoding session per reader can be active at one time

===Global Settings via Edge_Server_Configuration===
Global Properties below need to be set for LLRP encode based on ones requirements
*Note: All MQTT (if set), timeout tagmask and epctarget always come form Global Variables
*Note: These are set globally using the Rifidi Edge Configuration [[Edge_Server_Configuration]]
<pre>
-Dorg.rifidi.llrp.encode.targetepc=000000000000000000000000 - (Hex Value) Sets the EPC Tag Data to perform operation on (Must be even block of 4 charaters and size depends on Tag - typical is 24 characters) - default if not set is 000000000000000000000000
-Dorg.rifidi.llrp.encode.tagmask=000000000000000000000000 - (Hex Value) Sets the Tag Mask to perform operation on (0 is wildcard match, F is Exact Match) (Must be even block of 4 characters and size depends on Tag - typical is 24 characters) - default if not set is 000000000000000000000000
-Dorg.rifidi.llrp.encode.timeout=5000 - Sets the duration of time to attempt operation (O is infinite until operation occurs, set in milliseconds)
-Dorg.rifidi.llrp.encode.accesspwd=0 - Access Password (Hex Value) (8 Characters or value of 0) - default if not set is 0
-Dorg.rifidi.llrp.encode.oldaccesspwd=0 - Old Access Password (Hex Value) (8 Characters or value of 0) - default if not set is 0 Note: used when setting new access password
-Dorg.rifidi.llrp.encode.killpwd=0 - Kill Password (Hex Value) (8 Characters or value of 0) - default if not set is 0
-Dorg.rifidi.llrp.encode.killpwdlockprivilege=Read_Write - If Set Performs a Kill Password Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) - default if not set is Read_Write
-Dorg.rifidi.llrp.encode.accesspwdlockprivilege=Read_Write - If Set Performs a Access Password Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) default if not set is Read_Write
-Dorg.rifidi.llrp.encode.epclockprivilege=Read_Write - If Set Performs a EPC Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) - default if not set is Read_Write
-Dorg.rifidi.llrp.encode.mqttbroker -- mqtt broker url (if set, received response of encode operation is posted to this queue in asynchronous mode). Mqttqos and mqttclientid must be set too in order to post to queue
-Dorg.rifidi.llrp.encode.mqttqos -- Quality of service level for mqtt, example: 2
-Dorg.rifidi.llrp.encode.mqttclientid -- Client id to publish messages on queue

</pre>

Note: These are optional Global variables for MQTT. If these are set then llrpencode command operations response to sent asynchronously to a topic
*topic naming convention {readerId}/encode with result of encoding operations

<pre>
-Dorg.rifidi.llrp.encode.mqttqos=2
-Dorg.rifidi.llrp.encode.mqttbroker=tcp://localhost:1883
-Dorg.rifidi.llrp.encode.mqttclientid=llrpEncodeId
</pre>

===Encode Response===

Response: Success
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Success</message>
</response>
</pre>

Response: Fail
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Fail</message>
<Description> LLRP Message Returned goes here such as Tag mask and Tag data not matching - such</Description>
</response>

Note: Some types of Fail responses could be
# More than one tag
# Not a LLLRP reader
# Not a valid session
# Invalid access spec request
# Encoding session already active

</pre>

===Encode Operations Response===
If MQTT Variables defined Globally (above) then operations result response will be sent to MQTT topic
*Topic naming convention: {readerID}/encode

Success Message
<pre>

<encodeMessage>
<status>Success</Status>
</encodeMessage>
</pre>
Fail Message
<pre>

<encodeMessage>
<status>Fail</status>
<operationList>
<operation>LLRPEPCWrite:Sucess</operation>
<operation>LLRPKillPasswordWrite:Sucess</operation>
<operation>LLRPAccessPasswordWrite:Sucess</operation>
<operation>LLRPEPCLock:No_Response_From_Tag</operation>
<operation>LLRPKillPaswordLock: Success</operation>
<operation>LLRPAccessPaswordLock: Success</operation>
</operationList>
</encodeMessage>
</pre>

Full List of Return Failure Codes:
<pre>

Insufficient_Power

No_Response_From_Tag

Nonspecific_Reader_Error

Nonspecific_Tag_Error

Tag_Memory_Locked_Error

Tag_Memory_Overrun_Error
</pre>

==LLRP Encode Single Shot Commands==
These are used to perform single operations and override Global properties therefore all values must be supplied in request
Note: All MQTT (if set), timeout tagmask and epctarget always come form Global Variables
*Command
/llrpencode/{readerID}/{sessionID}/{tag}/{operationCode}/{properties}

List of operationCodes
LLRPEPCWrite
LLRPKillPasswordWrite
LLRPAccessPasswordWrite
LLRPEPCLock
LLRPKillPasswordLock
LLRPAccessPasswordLock
*Example LLRPECWrite - Used to Write a EPC ID
http://localhost:8111/llrpencode/LLRP_1/1/000000000001111111111268/LLRPEPCWrite/accesspwd=12345678

*Example LLRPKillPasswordWrite - Used to Write a Kill Password
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPKillPasswordWrite/accesspwd=12345678;killpwd=87654321

*Example LLRPAccessPasswordWrite - Used to Write a Access Password
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPAccessPasswordWrite/oldaccesspwd=12345678;accesspwd=98765432

*Example LLRPEPCLock - Set EPC Lock Priveledge
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPEPCLock/accesspwd=98765432;epclockprivilege=Read_Write

*Example LLRPKillPasswordLock - Set Kill Password Lock Privilege
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPKillPasswordLock/accesspwd=98765432;privilege=Read_Write

*Example LLRPAccessPasswordLock - Set Access Password Lock Privilege
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPAccessPasswordLock/accesspwd=98765432;privilege=Read_Write
===Single Shot Encode Operations Response===
If MQTT Variables defined Globally (above) then operations result response will be sent to MQTT topic otherwise response is synchronous
*Topic naming convention: {readerID}/encode

===Encode Single Shot Response===

Response: Success
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Success</message>
</response>
</pre>

Response: Fail
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Fail</message>
<Description> LLRP Message Returned goes here such as Tag mask and Tag data not matching - such</Description>
</response>

Note: Some types of Fail responses could be
# More than one tag
# Not a LLLRP reader
# Not a valid session
# Invalid access spec request
# Encoding session already active

</pre>

Success Message
<pre>

<encodeMessage>
<status>Success</Status>
</encodeMessage>
</pre>
Fail Message
<pre>

<encodeMessage>
<status>Fail</status>
<operationList>
<operation>LLRPEPCLock:No_Response_From_Tag</operation>
</operationList>
</encodeMessage>
</pre>

Full List of Return Failure Codes:
<pre>

Insufficient_Power

No_Response_From_Tag

Nonspecific_Reader_Error

Nonspecific_Tag_Error

Tag_Memory_Locked_Error

Tag_Memory_Overrun_Error
</pre>

LLRP Tag Encoding

2014-10-26T17:32:08Z

Matt: /* LLRP Encode Single Shot Commands */

=LLRP Tag Encoding Options=
==LLRP Encode Command==
LLRP Encode Command is used to encode a new Tag with the following operations:
<pre>
Order: operationCode
1 - LLRPAccessPasswordWrite
2 - LLRPEPCWrite
3 - LLRPKillPasswordWrite
4 - LLRPEPCLock
5 - LLRPKillPasswordLock
6 - LLRPAccessPasswordLock
</pre>
What are EPC, Kill Password, Access Password:
*EPC is the GEN2 EPC ID for a Tag
*Kill Password is used to set the password necessary to kill/destroy a tag for future use (by default there is no password (value(0))
*Access Password is used to perform tag writes such as EPC, Kill Password, Access Password (by default there is no password (value(0))
*C1G2Write and C1G2Lock are the LLRP Access Spec operations used

*Command
llrpencode/{readerID}/{sessionID}/{tag}- Performs all LLRP Encoding operations for a New RFID Tag

*Example
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666
*Prerequisites
# Only one tag can be present(This is Not a Bulk encoding operation)
# Must be a LLRP reader
# Must be a valid readerID and sessionID
# tag must be evenly divide by 4 (word in hex) and tag must be able to support length
# access password and kill password must be evenly divide by 4 (4 or 8 characters/1 or 2 words) or 0
# Only one encoding session per reader can be active at one time

===Global Settings via Edge_Server_Configuration===
Global Properties below need to be set for LLRP encode based on ones requirements
*Note: All MQTT (if set), timeout tagmask and epctarget always come form Global Variables
*Note: These are set globally using the Rifidi Edge Configuration [[Edge_Server_Configuration]]
<pre>
-Dorg.rifidi.llrp.encode.targetepc=000000000000000000000000 - (Hex Value) Sets the EPC Tag Data to perform operation on (Must be even block of 4 charaters and size depends on Tag - typical is 24 characters) - default if not set is 000000000000000000000000
-Dorg.rifidi.llrp.encode.tagmask=000000000000000000000000 - (Hex Value) Sets the Tag Mask to perform operation on (0 is wildcard match, F is Exact Match) (Must be even block of 4 characters and size depends on Tag - typical is 24 characters) - default if not set is 000000000000000000000000
-Dorg.rifidi.llrp.encode.timeout=5000 - Sets the duration of time to attempt operation (O is infinite until operation occurs, set in milliseconds)
-Dorg.rifidi.llrp.encode.accesspwd=0 - Access Password (Hex Value) (8 Characters or value of 0) - default if not set is 0
-Dorg.rifidi.llrp.encode.oldaccesspwd=0 - Old Access Password (Hex Value) (8 Characters or value of 0) - default if not set is 0 Note: used when setting new access password
-Dorg.rifidi.llrp.encode.killpwd=0 - Kill Password (Hex Value) (8 Characters or value of 0) - default if not set is 0
-Dorg.rifidi.llrp.encode.killpwdlockprivilege=Read_Write - If Set Performs a Kill Password Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) - default if not set is Read_Write
-Dorg.rifidi.llrp.encode.accesspwdlockprivilege=Read_Write - If Set Performs a Access Password Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) default if not set is Read_Write
-Dorg.rifidi.llrp.encode.epclockprivilege=Read_Write - If Set Performs a EPC Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) - default if not set is Read_Write
-Dorg.rifidi.llrp.encode.mqttbroker -- mqtt broker url (if set, received response of encode operation is posted to this queue in asynchronous mode). Mqttqos and mqttclientid must be set too in order to post to queue
-Dorg.rifidi.llrp.encode.mqttqos -- Quality of service level for mqtt, example: 2
-Dorg.rifidi.llrp.encode.mqttclientid -- Client id to publish messages on queue

</pre>

Note: These are optional Global variables for MQTT. If these are set then llrpencode command operations response to sent asynchronously to a topic
*topic naming convention {readerId}/encode with result of encoding operations

<pre>
-Dorg.rifidi.llrp.encode.mqttqos=2
-Dorg.rifidi.llrp.encode.mqttbroker=tcp://localhost:1883
-Dorg.rifidi.llrp.encode.mqttclientid=llrpEncodeId
</pre>

===Encode Response===

Response: Success
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Success</message>
</response>
</pre>

Response: Fail
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Fail</message>
<Description> LLRP Message Returned goes here such as Tag mask and Tag data not matching - such</Description>
</response>

Note: Some types of Fail responses could be
# More than one tag
# Not a LLLRP reader
# Not a valid session
# Invalid access spec request
# Encoding session already active

</pre>

===Encode Operations Response===
If MQTT Variables defined Globally (above) then operations result response will be sent to MQTT topic
*Topic naming convention: {readerID}/encode

Success Message
<pre>

<encodeMessage>
<status>Success</Status>
</encodeMessage>
</pre>
Fail Message
<pre>

<encodeMessage>
<status>Fail</status>
<operationList>
<operation>LLRPEPCWrite:Sucess</operation>
<operation>LLRPKillPasswordWrite:Sucess</operation>
<operation>LLRPAccessPasswordWrite:Sucess</operation>
<operation>LLRPEPCLock:No_Response_From_Tag</operation>
<operation>LLRPKillPaswordLock: Success</operation>
<operation>LLRPAccessPaswordLock: Success</operation>
</operationList>
</encodeMessage>
</pre>

Full List of Return Failure Codes:
<pre>

Insufficient_Power

No_Response_From_Tag

Nonspecific_Reader_Error

Nonspecific_Tag_Error

Tag_Memory_Locked_Error

Tag_Memory_Overrun_Error
</pre>

==LLRP Encode Single Shot Commands==
These are used to perform single operations and override Global properties therefore all values must be supplied in request
Note: All MQTT (if set), timeout tagmask and epctarget always come form Global Variables
*Command
/llrpencode/{readerID}/{sessionID}/{tag}/{operationCode}/{properties}

List of operationCodes
LLRPEPCWrite
LLRPKillPasswordWrite
LLRPAccessPasswordWrite
LLRPEPCLock
LLRPKillPasswordLock
LLRPAccessPasswordLock
*Example LLRPECWrite - Used to Write a EPC ID
http://localhost:8111/llrpencode/LLRP_1/1/000000000001111111111268/LLRPEPCWrite/accesspwd=12345678

*Example LLRPKillPasswordWrite - Used to Write a Kill Password
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPKillPasswordWrite/accesspwd=12345678;killpwd=87654321

*Example LLRPAccessPasswordWrite - Used to Write a Access Password
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPAccessPasswordWrite/oldaccesspwd=12345678;accesspwd=98765432

*Example LLRPEPCLock - Set EPC Lock Priveledge
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPEPCLock/accesspwd=98765432;epclockprivilege=Read_Write

*Example LLRPKillPasswordLock - Set Kill Password Lock Privilege
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPKillPasswordLock/accesspwd=98765432;killpwdlockprivilege=Read_Write

*Example LLRPAccessPasswordLock - Set Access Password Lock Privilege
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPKillPasswordLock/accesspwd=98765432;privilege=Read_Write
===Single Shot Encode Operations Response===
If MQTT Variables defined Globally (above) then operations result response will be sent to MQTT topic otherwise response is synchronous
*Topic naming convention: {readerID}/encode

===Encode Single Shot Response===

Response: Success
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Success</message>
</response>
</pre>

Response: Fail
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Fail</message>
<Description> LLRP Message Returned goes here such as Tag mask and Tag data not matching - such</Description>
</response>

Note: Some types of Fail responses could be
# More than one tag
# Not a LLLRP reader
# Not a valid session
# Invalid access spec request
# Encoding session already active

</pre>

Success Message
<pre>

<encodeMessage>
<status>Success</Status>
</encodeMessage>
</pre>
Fail Message
<pre>

<encodeMessage>
<status>Fail</status>
<operationList>
<operation>LLRPEPCLock:No_Response_From_Tag</operation>
</operationList>
</encodeMessage>
</pre>

Full List of Return Failure Codes:
<pre>

Insufficient_Power

No_Response_From_Tag

Nonspecific_Reader_Error

Nonspecific_Tag_Error

Tag_Memory_Locked_Error

Tag_Memory_Overrun_Error
</pre>

LLRP Tag Encoding

2014-10-26T17:23:39Z

Matt: /* LLRP Encode Single Shot Commands */

=LLRP Tag Encoding Options=
==LLRP Encode Command==
LLRP Encode Command is used to encode a new Tag with the following operations:
<pre>
Order: operationCode
1 - LLRPAccessPasswordWrite
2 - LLRPEPCWrite
3 - LLRPKillPasswordWrite
4 - LLRPEPCLock
5 - LLRPKillPasswordLock
6 - LLRPAccessPasswordLock
</pre>
What are EPC, Kill Password, Access Password:
*EPC is the GEN2 EPC ID for a Tag
*Kill Password is used to set the password necessary to kill/destroy a tag for future use (by default there is no password (value(0))
*Access Password is used to perform tag writes such as EPC, Kill Password, Access Password (by default there is no password (value(0))
*C1G2Write and C1G2Lock are the LLRP Access Spec operations used

*Command
llrpencode/{readerID}/{sessionID}/{tag}- Performs all LLRP Encoding operations for a New RFID Tag

*Example
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666
*Prerequisites
# Only one tag can be present(This is Not a Bulk encoding operation)
# Must be a LLRP reader
# Must be a valid readerID and sessionID
# tag must be evenly divide by 4 (word in hex) and tag must be able to support length
# access password and kill password must be evenly divide by 4 (4 or 8 characters/1 or 2 words) or 0
# Only one encoding session per reader can be active at one time

===Global Settings via Edge_Server_Configuration===
Global Properties below need to be set for LLRP encode based on ones requirements
*Note: All MQTT (if set), timeout tagmask and epctarget always come form Global Variables
*Note: These are set globally using the Rifidi Edge Configuration [[Edge_Server_Configuration]]
<pre>
-Dorg.rifidi.llrp.encode.targetepc=000000000000000000000000 - (Hex Value) Sets the EPC Tag Data to perform operation on (Must be even block of 4 charaters and size depends on Tag - typical is 24 characters) - default if not set is 000000000000000000000000
-Dorg.rifidi.llrp.encode.tagmask=000000000000000000000000 - (Hex Value) Sets the Tag Mask to perform operation on (0 is wildcard match, F is Exact Match) (Must be even block of 4 characters and size depends on Tag - typical is 24 characters) - default if not set is 000000000000000000000000
-Dorg.rifidi.llrp.encode.timeout=5000 - Sets the duration of time to attempt operation (O is infinite until operation occurs, set in milliseconds)
-Dorg.rifidi.llrp.encode.accesspwd=0 - Access Password (Hex Value) (8 Characters or value of 0) - default if not set is 0
-Dorg.rifidi.llrp.encode.oldaccesspwd=0 - Old Access Password (Hex Value) (8 Characters or value of 0) - default if not set is 0 Note: used when setting new access password
-Dorg.rifidi.llrp.encode.killpwd=0 - Kill Password (Hex Value) (8 Characters or value of 0) - default if not set is 0
-Dorg.rifidi.llrp.encode.killpwdlockprivilege=Read_Write - If Set Performs a Kill Password Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) - default if not set is Read_Write
-Dorg.rifidi.llrp.encode.accesspwdlockprivilege=Read_Write - If Set Performs a Access Password Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) default if not set is Read_Write
-Dorg.rifidi.llrp.encode.epclockprivilege=Read_Write - If Set Performs a EPC Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) - default if not set is Read_Write
-Dorg.rifidi.llrp.encode.mqttbroker -- mqtt broker url (if set, received response of encode operation is posted to this queue in asynchronous mode). Mqttqos and mqttclientid must be set too in order to post to queue
-Dorg.rifidi.llrp.encode.mqttqos -- Quality of service level for mqtt, example: 2
-Dorg.rifidi.llrp.encode.mqttclientid -- Client id to publish messages on queue

</pre>

Note: These are optional Global variables for MQTT. If these are set then llrpencode command operations response to sent asynchronously to a topic
*topic naming convention {readerId}/encode with result of encoding operations

<pre>
-Dorg.rifidi.llrp.encode.mqttqos=2
-Dorg.rifidi.llrp.encode.mqttbroker=tcp://localhost:1883
-Dorg.rifidi.llrp.encode.mqttclientid=llrpEncodeId
</pre>

===Encode Response===

Response: Success
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Success</message>
</response>
</pre>

Response: Fail
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Fail</message>
<Description> LLRP Message Returned goes here such as Tag mask and Tag data not matching - such</Description>
</response>

Note: Some types of Fail responses could be
# More than one tag
# Not a LLLRP reader
# Not a valid session
# Invalid access spec request
# Encoding session already active

</pre>

===Encode Operations Response===
If MQTT Variables defined Globally (above) then operations result response will be sent to MQTT topic
*Topic naming convention: {readerID}/encode

Success Message
<pre>

<encodeMessage>
<status>Success</Status>
</encodeMessage>
</pre>
Fail Message
<pre>

<encodeMessage>
<status>Fail</status>
<operationList>
<operation>LLRPEPCWrite:Sucess</operation>
<operation>LLRPKillPasswordWrite:Sucess</operation>
<operation>LLRPAccessPasswordWrite:Sucess</operation>
<operation>LLRPEPCLock:No_Response_From_Tag</operation>
<operation>LLRPKillPaswordLock: Success</operation>
<operation>LLRPAccessPaswordLock: Success</operation>
</operationList>
</encodeMessage>
</pre>

Full List of Return Failure Codes:
<pre>

Insufficient_Power

No_Response_From_Tag

Nonspecific_Reader_Error

Nonspecific_Tag_Error

Tag_Memory_Locked_Error

Tag_Memory_Overrun_Error
</pre>

==LLRP Encode Single Shot Commands==
These are used to perform single operations and override Global properties therefore all values must be supplied in request
Note: All MQTT (if set), timeout tagmask and epctarget always come form Global Variables
*Command
/llrpencode/{readerID}/{sessionID}/{tag}/{operationCode}/{properties}

List of operationCodes
LLRPEPCWrite
LLRPKillPasswordWrite
LLRPAccessPasswordWrite
LLRPEPCLock
LLRPKillPasswordLock
LLRPAccessPasswordLock
*Example LLRPECWrite - Used to Write a EPC ID
http://localhost:8111/llrpencode/LLRP_1/1/000000000001111111111268/LLRPEPCWrite/accesspwd=12345678

*Example LLRPKillPasswordWrite - Used to Write a Kill Password
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPKillPasswordWrite/accesspwd=12345678;killpwd=87654321

*Example LLRPAccessPasswordWrite - Used to Write a Access Password
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPAccessPasswordWrite/oldaccesspwd=12345678;accesspwd=98765432

*Example LLRPEPCLock - Set EPC Lock Priveledge
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPEPCLock/accesspwd=98765432;epclockprivilege=Read_Write

*Example LLRPKillPasswordLock - Set Kill Password Lock Privilege
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPKillPasswordLock/accesspwd=98765432;killpwdlockprivilege=Read_Write

*Example LLRPAccessPasswordLock - Set Access Password Lock Privilege
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666/LLRPKillPasswordLock/accesspwd=98765432;accesspwdlockprivilege=Read_Write
===Single Shot Encode Operations Response===
If MQTT Variables defined Globally (above) then operations result response will be sent to MQTT topic otherwise response is synchronous
*Topic naming convention: {readerID}/encode

===Encode Single Shot Response===

Response: Success
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Success</message>
</response>
</pre>

Response: Fail
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Fail</message>
<Description> LLRP Message Returned goes here such as Tag mask and Tag data not matching - such</Description>
</response>

Note: Some types of Fail responses could be
# More than one tag
# Not a LLLRP reader
# Not a valid session
# Invalid access spec request
# Encoding session already active

</pre>

Success Message
<pre>

<encodeMessage>
<status>Success</Status>
</encodeMessage>
</pre>
Fail Message
<pre>

<encodeMessage>
<status>Fail</status>
<operationList>
<operation>LLRPEPCLock:No_Response_From_Tag</operation>
</operationList>
</encodeMessage>
</pre>

Full List of Return Failure Codes:
<pre>

Insufficient_Power

No_Response_From_Tag

Nonspecific_Reader_Error

Nonspecific_Tag_Error

Tag_Memory_Locked_Error

Tag_Memory_Overrun_Error
</pre>

LLRP Tag Encoding

2014-10-26T17:22:53Z

Matt: /* LLRP Encode Single Shot Commands */

=LLRP Tag Encoding Options=
==LLRP Encode Command==
LLRP Encode Command is used to encode a new Tag with the following operations:
<pre>
Order: operationCode
1 - LLRPAccessPasswordWrite
2 - LLRPEPCWrite
3 - LLRPKillPasswordWrite
4 - LLRPEPCLock
5 - LLRPKillPasswordLock
6 - LLRPAccessPasswordLock
</pre>
What are EPC, Kill Password, Access Password:
*EPC is the GEN2 EPC ID for a Tag
*Kill Password is used to set the password necessary to kill/destroy a tag for future use (by default there is no password (value(0))
*Access Password is used to perform tag writes such as EPC, Kill Password, Access Password (by default there is no password (value(0))
*C1G2Write and C1G2Lock are the LLRP Access Spec operations used

*Command
llrpencode/{readerID}/{sessionID}/{tag}- Performs all LLRP Encoding operations for a New RFID Tag

*Example
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666
*Prerequisites
# Only one tag can be present(This is Not a Bulk encoding operation)
# Must be a LLRP reader
# Must be a valid readerID and sessionID
# tag must be evenly divide by 4 (word in hex) and tag must be able to support length
# access password and kill password must be evenly divide by 4 (4 or 8 characters/1 or 2 words) or 0
# Only one encoding session per reader can be active at one time

===Global Settings via Edge_Server_Configuration===
Global Properties below need to be set for LLRP encode based on ones requirements
*Note: All MQTT (if set), timeout tagmask and epctarget always come form Global Variables
*Note: These are set globally using the Rifidi Edge Configuration [[Edge_Server_Configuration]]
<pre>
-Dorg.rifidi.llrp.encode.targetepc=000000000000000000000000 - (Hex Value) Sets the EPC Tag Data to perform operation on (Must be even block of 4 charaters and size depends on Tag - typical is 24 characters) - default if not set is 000000000000000000000000
-Dorg.rifidi.llrp.encode.tagmask=000000000000000000000000 - (Hex Value) Sets the Tag Mask to perform operation on (0 is wildcard match, F is Exact Match) (Must be even block of 4 characters and size depends on Tag - typical is 24 characters) - default if not set is 000000000000000000000000
-Dorg.rifidi.llrp.encode.timeout=5000 - Sets the duration of time to attempt operation (O is infinite until operation occurs, set in milliseconds)
-Dorg.rifidi.llrp.encode.accesspwd=0 - Access Password (Hex Value) (8 Characters or value of 0) - default if not set is 0
-Dorg.rifidi.llrp.encode.oldaccesspwd=0 - Old Access Password (Hex Value) (8 Characters or value of 0) - default if not set is 0 Note: used when setting new access password
-Dorg.rifidi.llrp.encode.killpwd=0 - Kill Password (Hex Value) (8 Characters or value of 0) - default if not set is 0
-Dorg.rifidi.llrp.encode.killpwdlockprivilege=Read_Write - If Set Performs a Kill Password Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) - default if not set is Read_Write
-Dorg.rifidi.llrp.encode.accesspwdlockprivilege=Read_Write - If Set Performs a Access Password Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) default if not set is Read_Write
-Dorg.rifidi.llrp.encode.epclockprivilege=Read_Write - If Set Performs a EPC Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) - default if not set is Read_Write
-Dorg.rifidi.llrp.encode.mqttbroker -- mqtt broker url (if set, received response of encode operation is posted to this queue in asynchronous mode). Mqttqos and mqttclientid must be set too in order to post to queue
-Dorg.rifidi.llrp.encode.mqttqos -- Quality of service level for mqtt, example: 2
-Dorg.rifidi.llrp.encode.mqttclientid -- Client id to publish messages on queue

</pre>

Note: These are optional Global variables for MQTT. If these are set then llrpencode command operations response to sent asynchronously to a topic
*topic naming convention {readerId}/encode with result of encoding operations

<pre>
-Dorg.rifidi.llrp.encode.mqttqos=2
-Dorg.rifidi.llrp.encode.mqttbroker=tcp://localhost:1883
-Dorg.rifidi.llrp.encode.mqttclientid=llrpEncodeId
</pre>

===Encode Response===

Response: Success
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Success</message>
</response>
</pre>

Response: Fail
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Fail</message>
<Description> LLRP Message Returned goes here such as Tag mask and Tag data not matching - such</Description>
</response>

Note: Some types of Fail responses could be
# More than one tag
# Not a LLLRP reader
# Not a valid session
# Invalid access spec request
# Encoding session already active

</pre>

===Encode Operations Response===
If MQTT Variables defined Globally (above) then operations result response will be sent to MQTT topic
*Topic naming convention: {readerID}/encode

Success Message
<pre>

<encodeMessage>
<status>Success</Status>
</encodeMessage>
</pre>
Fail Message
<pre>

<encodeMessage>
<status>Fail</status>
<operationList>
<operation>LLRPEPCWrite:Sucess</operation>
<operation>LLRPKillPasswordWrite:Sucess</operation>
<operation>LLRPAccessPasswordWrite:Sucess</operation>
<operation>LLRPEPCLock:No_Response_From_Tag</operation>
<operation>LLRPKillPaswordLock: Success</operation>
<operation>LLRPAccessPaswordLock: Success</operation>
</operationList>
</encodeMessage>
</pre>

Full List of Return Failure Codes:
<pre>

Insufficient_Power

No_Response_From_Tag

Nonspecific_Reader_Error

Nonspecific_Tag_Error

Tag_Memory_Locked_Error

Tag_Memory_Overrun_Error
</pre>

==LLRP Encode Single Shot Commands==
These are used to perform single operations and override Global properties therefore all values must be supplied in request
Note: All MQTT (if set), timeout tagmask and epctarget always come form Global Variables
*Command
/llrpencode/{readerID}/{sessionID}/{tag}/{operationCode}/{properties}

List of operationCodes
LLRPEPCWrite
LLRPKillPasswordWrite
LLRPAccessPasswordWrite
LLRPEPCLock
LLRPKillPasswordLock
LLRPAccessPasswordLock
*Example LLRPECWrite - Used to Write a EPC ID
http://localhost:8111/llrpencode/LLRP_1/1/000000000001111111111268/LLRPEPCWrite/accesspwd=12345678

*Example LLRPKillPasswordWrite - Used to Write a Kill Password
http://localhost:8111/llrpencode/LLRP_1/1/00001111222233334444555566667777/LLRPKillPasswordWrite/accesspwd=12345678;killpwd=87654321

*Example LLRPAccessPasswordWrite - Used to Write a Access Password
http://localhost:8111/llrpencode/LLRP_1/1/00001111222233334444555566667777/LLRPAccessPasswordWrite/oldaccesspwd=12345678;accesspwd=98765432

*Example LLRPEPCLock - Set EPC Lock Priveledge
http://localhost:8111/llrpencode/LLRP_1/1/00001111222233334444555566667777/LLRPEPCLock/accesspwd=98765432;epclockprivilege=Read_Write

*Example LLRPKillPasswordLock - Set Kill Password Lock Privilege
http://localhost:8111/llrpencode/LLRP_1/1/00001111222233334444555566667777/LLRPKillPasswordLock/accesspwd=98765432;killpwdlockprivilege=Read_Write

*Example LLRPAccessPasswordLock - Set Access Password Lock Privilege
http://localhost:8111/llrpencode/LLRP_1/1/00001111222233334444555566667777/LLRPKillPasswordLock/accesspwd=98765432;accesspwdlockprivilege=Read_Write
===Single Shot Encode Operations Response===
If MQTT Variables defined Globally (above) then operations result response will be sent to MQTT topic otherwise response is synchronous
*Topic naming convention: {readerID}/encode

===Encode Single Shot Response===

Response: Success
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Success</message>
</response>
</pre>

Response: Fail
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Fail</message>
<Description> LLRP Message Returned goes here such as Tag mask and Tag data not matching - such</Description>
</response>

Note: Some types of Fail responses could be
# More than one tag
# Not a LLLRP reader
# Not a valid session
# Invalid access spec request
# Encoding session already active

</pre>

Success Message
<pre>

<encodeMessage>
<status>Success</Status>
</encodeMessage>
</pre>
Fail Message
<pre>

<encodeMessage>
<status>Fail</status>
<operationList>
<operation>LLRPEPCLock:No_Response_From_Tag</operation>
</operationList>
</encodeMessage>
</pre>

Full List of Return Failure Codes:
<pre>

Insufficient_Power

No_Response_From_Tag

Nonspecific_Reader_Error

Nonspecific_Tag_Error

Tag_Memory_Locked_Error

Tag_Memory_Overrun_Error
</pre>

LLRP Tag Encoding

2014-10-26T17:20:51Z

Matt: /* LLRP Encode Command */

=LLRP Tag Encoding Options=
==LLRP Encode Command==
LLRP Encode Command is used to encode a new Tag with the following operations:
<pre>
Order: operationCode
1 - LLRPAccessPasswordWrite
2 - LLRPEPCWrite
3 - LLRPKillPasswordWrite
4 - LLRPEPCLock
5 - LLRPKillPasswordLock
6 - LLRPAccessPasswordLock
</pre>
What are EPC, Kill Password, Access Password:
*EPC is the GEN2 EPC ID for a Tag
*Kill Password is used to set the password necessary to kill/destroy a tag for future use (by default there is no password (value(0))
*Access Password is used to perform tag writes such as EPC, Kill Password, Access Password (by default there is no password (value(0))
*C1G2Write and C1G2Lock are the LLRP Access Spec operations used

*Command
llrpencode/{readerID}/{sessionID}/{tag}- Performs all LLRP Encoding operations for a New RFID Tag

*Example
http://localhost:8111/llrpencode/LLRP_1/1/111122223333444455556666
*Prerequisites
# Only one tag can be present(This is Not a Bulk encoding operation)
# Must be a LLRP reader
# Must be a valid readerID and sessionID
# tag must be evenly divide by 4 (word in hex) and tag must be able to support length
# access password and kill password must be evenly divide by 4 (4 or 8 characters/1 or 2 words) or 0
# Only one encoding session per reader can be active at one time

===Global Settings via Edge_Server_Configuration===
Global Properties below need to be set for LLRP encode based on ones requirements
*Note: All MQTT (if set), timeout tagmask and epctarget always come form Global Variables
*Note: These are set globally using the Rifidi Edge Configuration [[Edge_Server_Configuration]]
<pre>
-Dorg.rifidi.llrp.encode.targetepc=000000000000000000000000 - (Hex Value) Sets the EPC Tag Data to perform operation on (Must be even block of 4 charaters and size depends on Tag - typical is 24 characters) - default if not set is 000000000000000000000000
-Dorg.rifidi.llrp.encode.tagmask=000000000000000000000000 - (Hex Value) Sets the Tag Mask to perform operation on (0 is wildcard match, F is Exact Match) (Must be even block of 4 characters and size depends on Tag - typical is 24 characters) - default if not set is 000000000000000000000000
-Dorg.rifidi.llrp.encode.timeout=5000 - Sets the duration of time to attempt operation (O is infinite until operation occurs, set in milliseconds)
-Dorg.rifidi.llrp.encode.accesspwd=0 - Access Password (Hex Value) (8 Characters or value of 0) - default if not set is 0
-Dorg.rifidi.llrp.encode.oldaccesspwd=0 - Old Access Password (Hex Value) (8 Characters or value of 0) - default if not set is 0 Note: used when setting new access password
-Dorg.rifidi.llrp.encode.killpwd=0 - Kill Password (Hex Value) (8 Characters or value of 0) - default if not set is 0
-Dorg.rifidi.llrp.encode.killpwdlockprivilege=Read_Write - If Set Performs a Kill Password Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) - default if not set is Read_Write
-Dorg.rifidi.llrp.encode.accesspwdlockprivilege=Read_Write - If Set Performs a Access Password Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) default if not set is Read_Write
-Dorg.rifidi.llrp.encode.epclockprivilege=Read_Write - If Set Performs a EPC Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) - default if not set is Read_Write
-Dorg.rifidi.llrp.encode.mqttbroker -- mqtt broker url (if set, received response of encode operation is posted to this queue in asynchronous mode). Mqttqos and mqttclientid must be set too in order to post to queue
-Dorg.rifidi.llrp.encode.mqttqos -- Quality of service level for mqtt, example: 2
-Dorg.rifidi.llrp.encode.mqttclientid -- Client id to publish messages on queue

</pre>

Note: These are optional Global variables for MQTT. If these are set then llrpencode command operations response to sent asynchronously to a topic
*topic naming convention {readerId}/encode with result of encoding operations

<pre>
-Dorg.rifidi.llrp.encode.mqttqos=2
-Dorg.rifidi.llrp.encode.mqttbroker=tcp://localhost:1883
-Dorg.rifidi.llrp.encode.mqttclientid=llrpEncodeId
</pre>

===Encode Response===

Response: Success
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Success</message>
</response>
</pre>

Response: Fail
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Fail</message>
<Description> LLRP Message Returned goes here such as Tag mask and Tag data not matching - such</Description>
</response>

Note: Some types of Fail responses could be
# More than one tag
# Not a LLLRP reader
# Not a valid session
# Invalid access spec request
# Encoding session already active

</pre>

===Encode Operations Response===
If MQTT Variables defined Globally (above) then operations result response will be sent to MQTT topic
*Topic naming convention: {readerID}/encode

Success Message
<pre>

<encodeMessage>
<status>Success</Status>
</encodeMessage>
</pre>
Fail Message
<pre>

<encodeMessage>
<status>Fail</status>
<operationList>
<operation>LLRPEPCWrite:Sucess</operation>
<operation>LLRPKillPasswordWrite:Sucess</operation>
<operation>LLRPAccessPasswordWrite:Sucess</operation>
<operation>LLRPEPCLock:No_Response_From_Tag</operation>
<operation>LLRPKillPaswordLock: Success</operation>
<operation>LLRPAccessPaswordLock: Success</operation>
</operationList>
</encodeMessage>
</pre>

Full List of Return Failure Codes:
<pre>

Insufficient_Power

No_Response_From_Tag

Nonspecific_Reader_Error

Nonspecific_Tag_Error

Tag_Memory_Locked_Error

Tag_Memory_Overrun_Error
</pre>

==LLRP Encode Single Shot Commands==
These are used to perform single operations and override Global properties therefore all values must be supplied in request
Note: All MQTT (if set), timeout tagmask and epctarget always come form Global Variables
*Command
/llrpencode/{readerID}/{sessionID}/{tag}/{operationCode}/{properties}

List of operationCodes
LLRPEPCWrite
LLRPKillPasswordWrite
LLRPAccessPasswordWrite
LLRPEPCLock
LLRPKillPasswordLock
LLRPAccessPasswordLock
*Example LLRPECWrite - Used to Write a EPC ID
http://localhost:8111/llrpencode/LLRP_1/1/000000000001111111111268/LLRPEPCWrite/accesspwd=12345678

*Example LLRPKillPasswordWrite - Used to Write a Kill Password
http://localhost:8111/LLRP_1/1/00001111222233334444555566667777/LLRPKillPasswordWrite/accesspwd=12345678;killpwd=87654321

*Example LLRPAccessPasswordWrite - Used to Write a Access Password
http://localhost:8111/LLRP_1/1/00001111222233334444555566667777/LLRPAccessPasswordWrite/oldaccesspwd=12345678;accesspwd=98765432

*Example LLRPEPCLock - Set EPC Lock Priveledge
http://localhost:8111/LLRP_1/1/00001111222233334444555566667777/LLRPEPCLock/accesspwd=98765432;epclockprivilege=Read_Write

*Example LLRPKillPasswordLock - Set Kill Password Lock Privilege
http://localhost:8111/LLRP_1/1/00001111222233334444555566667777/LLRPKillPasswordLock/accesspwd=98765432;killpwdlockprivilege=Read_Write

*Example LLRPAccessPasswordLock - Set Access Password Lock Privilege
http://localhost:8111/LLRP_1/1/00001111222233334444555566667777/LLRPKillPasswordLock/accesspwd=98765432;accesspwdlockprivilege=Read_Write
===Single Shot Encode Operations Response===
If MQTT Variables defined Globally (above) then operations result response will be sent to MQTT topic otherwise response is synchronous
*Topic naming convention: {readerID}/encode

===Encode Single Shot Response===

Response: Success
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Success</message>
</response>
</pre>

Response: Fail
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Fail</message>
<Description> LLRP Message Returned goes here such as Tag mask and Tag data not matching - such</Description>
</response>

Note: Some types of Fail responses could be
# More than one tag
# Not a LLLRP reader
# Not a valid session
# Invalid access spec request
# Encoding session already active

</pre>

Success Message
<pre>

<encodeMessage>
<status>Success</Status>
</encodeMessage>
</pre>
Fail Message
<pre>

<encodeMessage>
<status>Fail</status>
<operationList>
<operation>LLRPEPCLock:No_Response_From_Tag</operation>
</operationList>
</encodeMessage>
</pre>

Full List of Return Failure Codes:
<pre>

Insufficient_Power

No_Response_From_Tag

Nonspecific_Reader_Error

Nonspecific_Tag_Error

Tag_Memory_Locked_Error

Tag_Memory_Overrun_Error
</pre>

LLRP Tag Encoding

2014-10-26T17:20:26Z

Matt: /* LLRP Encode Command */

=LLRP Tag Encoding Options=
==LLRP Encode Command==
LLRP Encode Command is used to encode a new Tag with the following operations:
<pre>
Order: operationCode
1 - LLRPAccessPasswordWrite
2 - LLRPEPCWrite
3 - LLRPKillPasswordWrite
4 - LLRPEPCLock
5 - LLRPKillPasswordLock
6 - LLRPAccessPasswordLock
</pre>
What are EPC, Kill Password, Access Password:
*EPC is the GEN2 EPC ID for a Tag
*Kill Password is used to set the password necessary to kill/destroy a tag for future use (by default there is no password (value(0))
*Access Password is used to perform tag writes such as EPC, Kill Password, Access Password (by default there is no password (value(0))
*C1G2Write and C1G2Lock are the LLRP Access Spec operations used

*Command
llrpencode/{readerID}/{sessionID}/{tag}- Performs all LLRP Encoding operations for a New RFID Tag

*Example
http://localhost:8111/llrpencode/LLRP_1/1/00001111222233334444555566667777
*Prerequisites
# Only one tag can be present(This is Not a Bulk encoding operation)
# Must be a LLRP reader
# Must be a valid readerID and sessionID
# tag must be evenly divide by 4 (word in hex) and tag must be able to support length
# access password and kill password must be evenly divide by 4 (4 or 8 characters/1 or 2 words) or 0
# Only one encoding session per reader can be active at one time

===Global Settings via Edge_Server_Configuration===
Global Properties below need to be set for LLRP encode based on ones requirements
*Note: All MQTT (if set), timeout tagmask and epctarget always come form Global Variables
*Note: These are set globally using the Rifidi Edge Configuration [[Edge_Server_Configuration]]
<pre>
-Dorg.rifidi.llrp.encode.targetepc=000000000000000000000000 - (Hex Value) Sets the EPC Tag Data to perform operation on (Must be even block of 4 charaters and size depends on Tag - typical is 24 characters) - default if not set is 000000000000000000000000
-Dorg.rifidi.llrp.encode.tagmask=000000000000000000000000 - (Hex Value) Sets the Tag Mask to perform operation on (0 is wildcard match, F is Exact Match) (Must be even block of 4 characters and size depends on Tag - typical is 24 characters) - default if not set is 000000000000000000000000
-Dorg.rifidi.llrp.encode.timeout=5000 - Sets the duration of time to attempt operation (O is infinite until operation occurs, set in milliseconds)
-Dorg.rifidi.llrp.encode.accesspwd=0 - Access Password (Hex Value) (8 Characters or value of 0) - default if not set is 0
-Dorg.rifidi.llrp.encode.oldaccesspwd=0 - Old Access Password (Hex Value) (8 Characters or value of 0) - default if not set is 0 Note: used when setting new access password
-Dorg.rifidi.llrp.encode.killpwd=0 - Kill Password (Hex Value) (8 Characters or value of 0) - default if not set is 0
-Dorg.rifidi.llrp.encode.killpwdlockprivilege=Read_Write - If Set Performs a Kill Password Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) - default if not set is Read_Write
-Dorg.rifidi.llrp.encode.accesspwdlockprivilege=Read_Write - If Set Performs a Access Password Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) default if not set is Read_Write
-Dorg.rifidi.llrp.encode.epclockprivilege=Read_Write - If Set Performs a EPC Lock Operation (values can be Read_Write (which Locks), Perma_Lock, Unlock) - default if not set is Read_Write
-Dorg.rifidi.llrp.encode.mqttbroker -- mqtt broker url (if set, received response of encode operation is posted to this queue in asynchronous mode). Mqttqos and mqttclientid must be set too in order to post to queue
-Dorg.rifidi.llrp.encode.mqttqos -- Quality of service level for mqtt, example: 2
-Dorg.rifidi.llrp.encode.mqttclientid -- Client id to publish messages on queue

</pre>

Note: These are optional Global variables for MQTT. If these are set then llrpencode command operations response to sent asynchronously to a topic
*topic naming convention {readerId}/encode with result of encoding operations

<pre>
-Dorg.rifidi.llrp.encode.mqttqos=2
-Dorg.rifidi.llrp.encode.mqttbroker=tcp://localhost:1883
-Dorg.rifidi.llrp.encode.mqttclientid=llrpEncodeId
</pre>

===Encode Response===

Response: Success
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Success</message>
</response>
</pre>

Response: Fail
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Fail</message>
<Description> LLRP Message Returned goes here such as Tag mask and Tag data not matching - such</Description>
</response>

Note: Some types of Fail responses could be
# More than one tag
# Not a LLLRP reader
# Not a valid session
# Invalid access spec request
# Encoding session already active

</pre>

===Encode Operations Response===
If MQTT Variables defined Globally (above) then operations result response will be sent to MQTT topic
*Topic naming convention: {readerID}/encode

Success Message
<pre>

<encodeMessage>
<status>Success</Status>
</encodeMessage>
</pre>
Fail Message
<pre>

<encodeMessage>
<status>Fail</status>
<operationList>
<operation>LLRPEPCWrite:Sucess</operation>
<operation>LLRPKillPasswordWrite:Sucess</operation>
<operation>LLRPAccessPasswordWrite:Sucess</operation>
<operation>LLRPEPCLock:No_Response_From_Tag</operation>
<operation>LLRPKillPaswordLock: Success</operation>
<operation>LLRPAccessPaswordLock: Success</operation>
</operationList>
</encodeMessage>
</pre>

Full List of Return Failure Codes:
<pre>

Insufficient_Power

No_Response_From_Tag

Nonspecific_Reader_Error

Nonspecific_Tag_Error

Tag_Memory_Locked_Error

Tag_Memory_Overrun_Error
</pre>

==LLRP Encode Single Shot Commands==
These are used to perform single operations and override Global properties therefore all values must be supplied in request
Note: All MQTT (if set), timeout tagmask and epctarget always come form Global Variables
*Command
/llrpencode/{readerID}/{sessionID}/{tag}/{operationCode}/{properties}

List of operationCodes
LLRPEPCWrite
LLRPKillPasswordWrite
LLRPAccessPasswordWrite
LLRPEPCLock
LLRPKillPasswordLock
LLRPAccessPasswordLock
*Example LLRPECWrite - Used to Write a EPC ID
http://localhost:8111/llrpencode/LLRP_1/1/000000000001111111111268/LLRPEPCWrite/accesspwd=12345678

*Example LLRPKillPasswordWrite - Used to Write a Kill Password
http://localhost:8111/LLRP_1/1/00001111222233334444555566667777/LLRPKillPasswordWrite/accesspwd=12345678;killpwd=87654321

*Example LLRPAccessPasswordWrite - Used to Write a Access Password
http://localhost:8111/LLRP_1/1/00001111222233334444555566667777/LLRPAccessPasswordWrite/oldaccesspwd=12345678;accesspwd=98765432

*Example LLRPEPCLock - Set EPC Lock Priveledge
http://localhost:8111/LLRP_1/1/00001111222233334444555566667777/LLRPEPCLock/accesspwd=98765432;epclockprivilege=Read_Write

*Example LLRPKillPasswordLock - Set Kill Password Lock Privilege
http://localhost:8111/LLRP_1/1/00001111222233334444555566667777/LLRPKillPasswordLock/accesspwd=98765432;killpwdlockprivilege=Read_Write

*Example LLRPAccessPasswordLock - Set Access Password Lock Privilege
http://localhost:8111/LLRP_1/1/00001111222233334444555566667777/LLRPKillPasswordLock/accesspwd=98765432;accesspwdlockprivilege=Read_Write
===Single Shot Encode Operations Response===
If MQTT Variables defined Globally (above) then operations result response will be sent to MQTT topic otherwise response is synchronous
*Topic naming convention: {readerID}/encode

===Encode Single Shot Response===

Response: Success
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Success</message>
</response>
</pre>

Response: Fail
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<response>
<message>Fail</message>
<Description> LLRP Message Returned goes here such as Tag mask and Tag data not matching - such</Description>
</response>

Note: Some types of Fail responses could be
# More than one tag
# Not a LLLRP reader
# Not a valid session
# Invalid access spec request
# Encoding session already active

</pre>

Success Message
<pre>

<encodeMessage>
<status>Success</Status>
</encodeMessage>
</pre>
Fail Message
<pre>

<encodeMessage>
<status>Fail</status>
<operationList>
<operation>LLRPEPCLock:No_Response_From_Tag</operation>
</operationList>
</encodeMessage>
</pre>

Full List of Return Failure Codes:
<pre>

Insufficient_Power

No_Response_From_Tag

Nonspecific_Reader_Error

Nonspecific_Tag_Error

Tag_Memory_Locked_Error

Tag_Memory_Overrun_Error
</pre>

Rifidi:Source Code

2014-08-14T23:05:24Z

Matt: /* Add Repository */

[[category:developerDoc]]
This page explains how to download and run the source code for the Rifidi products. 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/.
=Quick Instructions=
The following are the basic steps needed to begin running Rifidi from source. If you have trouble or need more explanation, please see the more detailed instructions on this page.
# Download the Eclipse for plugin developers (3.5 is what we are using)
# Install the subclipse plugin
# Add this svn to the list of repositories: emulator, prototyper - https://transcends.svn.cloudforge.com/emulator, edge, workbench - https://transcends.svn.cloudforge.com/rifidi
# Check out the following projects from rifidi/trunk: org.rifidi.binary, org.rifidi.emulator.target, org.rifidi.ui.ide
# Open up the target file in org.rifidi.emulator.target and click the button that says "set as target platform"
# Open up the .product file in org.rifidi.ui.ide and click "launch an eclipse application"

=Rifidi Source Code=
For those who need to see the source code for the Rifidi products, you will have to check out the code from svn. This section explains how to check out and run the code from source.
==Organization==
In general the code for Rifidi is organized into Eclipse plugins or bundles. Eclipse handles the loading and execution of the plugins. For more detailed information about how our source code is organized, please see [[Development and Release Process#Concepts]].
* '''SVN Structure''' - There are three main folders in the Rifidi directory on <code>rep-external</code> (the main svn repository for Rifidi). The ''trunk'' folder contains the code that is being developed. It is ''not'' guaranteed to be stable. The ''tags'' folder contains tagged versions of the source for each of <span class="plainlinks">[http://www.timewing.com.sg/ <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">aircon service</span>] the plugins. The source in these plugins should be relatively stable. The ''branches'' folder contains plugins that have been branched so that larger changes can be made on plugins without holding up other developers. These changes can then later be merged back in. For more details about our SVN, see [[Development and Release Process#SVN Structure]]
* Target Platform - A target platform is the base set of <span class="plainlinks">[http://www.timewing.com.sg/ac_service.html <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">ac repair</span>] plugins that an Eclipse application needs to run. In order to provide a more stable environment and to ensure a clean separation between the base plugins that Rifidi needs and the base plugins that your Eclipse IDE needs, we provide a target platform for each of the Rifidi products. You can find these in the trunk. They will be named something like <code>org.rifidi.emulator.target</code>. For more information see [[Development and Release Process#Target Platforms]].
* org.rifidi.binary - As the source code for Rifidi gets larger it begins to get harder to maintain a stable set of plugins. In order to simplify things, there is a folder in the <span class="plainlinks">[http://www.timewing.com.sg/refrg_service.html<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"> refrigerator repair</span>] svn into which stable binaries of each of the plugins used in the rifidi project will be placed. This folder is used in conjunction with the target platform.
* Product File - In Eclipse, a product file is used to define the needed eclipse plugins. Running this file will create a new Eclipse 'Run Configuration' in your IDE. You can then tweak this run configuration as needed.
* Source Code Plugins - A stable binary version of each of the plugins is <span class="plainlinks">[http://jamumassagesingapore.com/services/dejamu/post-natal<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"> jamu postnatal massage</span>] contained in the org.rifidi.binary folder. However, if you wish to view the source of a particular plugin or run a plugin from source, you must download the code from either the version in the trunk or a tagged version in the tags directory.

==Downloading the Code==

Our code is hosted at https://transcends.svn.cloudforge.com/rifidi and https://transcends.svn.cloudforge.com/emulator. 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.

The following steps explain how to check out and run Rifidi Emulator. The other products in the Rifidi Suite follow similar steps. If you need help with them, you can ask questions on IRC or our forums.

===Prerequisites===

The Rifidi Emulator is written in java and consists of Eclipse plugins. At this point it is easiest to compile and build it inside of the eclipse environment.

====Install Eclipse====
Note that you need the "Eclipse for RCP/Plug-in Developers" version of eclipse. Rifidi will not run on other versions.
* If you do not already have eclipse, or if you have a different version, you will need to get this version
** Go to http://www.eclipse.org/downloads/ and download the "Eclipse for RCP/Plug-in Developers" version of Eclipse to a convenient location.
** Unzip the package.
** 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]]
* If you have not used eclipse before, you will be required to select a workspace when eclipse is opening.
** After eclipse opens go to the workbench[[Image:Rifidi_from_source-2-wokbench.png |none|thumb|800px|Open up the workbench]]
* If you have an existing workspace, you will need to create a new one.
** Go to file -> switch workspace -> other [[Image:Rifidi_from_source-3-switch_workspace.png |none|thumb|800px|Open up the workbench]]
** Select a new directory for your Rifidi workspace.

====Install Subclipse====

Subclipse is an eclipse plugin that manages svn commands.

* Follow the instructions at http://subclipse.tigris.org/install.html.
* In step 6 of the above instructions, don't install the Optional Integrations. Only the subclipse plugin is needed

===Add Repository===

* Open the 'SVN Repository Exploring' perspective
** Window -> Open Perspective -> Other [[Image:Rifidi_from_source-4-svn_rep_explore1.png |none|thumb|800px|Open up the perspective picker]]
** SVN Repository Exploring [[Image:Rifidi_from_source-5-svn_rep_explore2.png |none|thumb|400px|Open up the SVN Repository Explorer]]
* Add the rifidi repository
** Click 'Add SVN Repository' button
** Add ' https://transcends.svn.cloudforge.com/rifidi '[[Image:Rifidi_from_source-6-add_rep.png |none|400px|thumb|Add the repository]]

===Check Out Code===

* Check out all the projects in the rifidi/trunk folder of the repository
** Highlight the folders you would like to check out. For Emulator you will need
*** <code>org.rifidi.binary</code>
*** <code>org.rifidi.emulator.taget3.5.2</code>
*** <code>org.rifidi.ui.ide</code>
** Right click them and select checkout [[Image:Rifidi_from_source-7-checkout1.png |none|800px|thumb|Select the projects]]
** Select Finish. [[Image:Rifidi_from_source-8-checkout2.png |none|400px|thumb|Checkout projects]]

===Set The Target Platform===
* Open up the .target file in <code>org.rifidi.emulator.target</code>
* Click the button that says "set as target platform"

==Running Rifidi==

The last step to get Rifidi running is to create a run configuration.

A run configuration is the set of plugins that will be loaded when you run the application. Plugins can come from one of two places:
#Workspace - these are the plugins that you have in the source tree on the left
#Target Environment - These are the plugins defined by the target environment that you are using that the time.

Because there is a product file for emulator defined in the <code>org.rifidi.ui.ide</code> plugin, the easiest way to create a new run configuration is by running the product file. This will automatically create a new run configuration

To Create a new Run Configuration:
* 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]]
* Right click on Rifidi.product in the org.rifidi.ui.ide project
* Click on "Run as eclipse application" [[Image:Rifidi_from_source-10_run_eclipse.png |none|thumb|800px|Run Rifidi]]
* From now on, you can start Rifidi via the green triangle button at the top of eclipse

If there was an error when starting the application, follow the step below to edit the run configuration:

To Edit a Run Configuration:
* Run -> Open Run Dialog -> Eclipse Application -> Rifidi.product. This is the run configuration.
* Go to the Tab Plug-ins. The selected plugins are the ones that will be run. Notice that there are two sections: "workspace" and "target platform"
* click the Button "Add Required Plug-ins" [[Image:Rifidi_from_source-11_add_plugins.png |none|thumb|600px|Add required plugins]]
* check any plugins specifically required for the application to run (for example, the emulator requires the readers to be included). Make sure that the plugin is coming from the place <span class="plainlinks">[http://www.miiny.com<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"> deals singapore</span>] that you intended (i.e. workspace or target platform).
* click the Button "Validate Plug-ins" to make sure everything is set up correctly
* click the Button "Apply"
* click the Button "Run" and start the Project

==Updating the code==

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.

To update the code:

* Open up the Team Synchronizing Perspective in eclipse
* Click the button that says "Synchronize".
* Select all projects.
* Install any updates by selecting all the updates show, right clicking and choosing 'update'

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).

==Switching Branches==
If you need to run code from another branch or tag, please see [[Switching Branches]].

==Viewing Source and Running From Trunk==
By default all of the rifidi plugins you are running in eclipse are pre-compiled, binary plugins contained in the <code>org.rifidi.binary</code> folder. If you want to view or edit the source for a particular plugin, you will need to check out the plugin from the trunk. Once it is checked out make sure to edit your run configuration so that the application will use the plugin from the workspace and not from the target platform.

For example, suppose I want to view the source for the Alien reader plugin. I need to follow the steps above to check out and run rifidi emulator. In addition, I need to check out the <code>org.rifidi.emulator.readers.alien</code> plugin. This is the code for the alien reader. In addition, I need to edit the run configuration to make sure that my workspace alien reader plugin is being used instead of the target platform alien reader plugin.

=Reporting Bugs=

To report bugs, please use the forum at

http://forums.rifidi.net

or drop by our IRC channel:

<nowiki>#rifidi on irc.freenode.org.</nowiki>

You can also visit us online at http://www.rifidi.net

1.3 Maven Build

2014-05-13T22:32:25Z

Matt: Removing all content from page

Custom LLRP Extension Jumpstart

2014-04-04T04:06:44Z

Matt: New page: Coming soon!

Coming soon!

Edge Server Configuration

2013-09-06T04:55:57Z

Matt: /* RifidiEdgeServer.ini */

This page explains the various configuration options of the Rifidi Edge Server
=RifidiEdgeServer.ini=
The RifidiEdgeServer.ini is a property file that contains options for various options when the edge server starts up. For linux, these arguments are in the "rifidi-server" executable.
==rifidiserver.ini file==
As of release 1.3.0, the default rifidiserver.ini file looks like this:
<pre>
-console
-vmargs
-Declipse.ignoreApp=true
-Dosgi.noShutdown=true
-Dorg.rifidi.edge.configuration=config/rifidi.xml
-Dosgi.clean=true
-Dorg.osgi.framework.bootdelegation=javax.xml.ws
-Dcom.sun.management.jmxremote.port=2021
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Djava.rmi.server.hostname=127.0.0.1
-Dorg.rifidi.edge.core.rmi.port=1101
-Dorg.rifidi.edge.ale.port=8081
-Dorg.rifidi.edge.ale.host=127.0.0.1
-Dosgi.framework.extensions=org.eclipse.equinox.weaving.hook
-Dorg.aspectj.osgi.verbose=true
-Dorg.rifidi.edge.autostart=true
-Dorg.rifidi.edge.logging=config/logging.properties
-Dorg.rifidi.ui.notify=false
</pre>

==Console==
;-console
:This starts up the OSGi console so that you can interact with the edge server from the command line. For a list of commands that are available see [[Edge Server Commands]]. If you would like the console to be available over the network, supply a port after the -console (e.g. -console 2020). Now it is possible to telnet into the server at the given port. It is recommended that you use ssh tunneling for security reasons (i.e. first ssh to the machine that is running the edge server, then telnet to the console). One thing to note is that after you telnet to the OSGi console, you cannot use the <tt>exit</tt> command as you normally would to close the telnet session. This is because <tt>exit</tt> will be caught by the OSGi console and will perform a System.exit(). Instead, to exit the telnet session while keeping the server running, just close the telnet window.
==VMArgs==
VMArgs must follow the <tt>-vmargs</tt> flag in the .ini file. They must start with <tt>-D</tt>. Default values can be found in the <tt>bundle.properties</tt> file in the spring directory for the appropriate option. Important VM args:
;-Dorg.rifidi.edge.configuration
:This is the path to the persistence file. See [[#rifidi.xml]].
;-Dcom.sun.management.jmxremote.port
:The port to open up JMX on. This is important if you are using a program like VisualVM to profile the server
;-Djava.rmi.server.hostname
:The hostname to open up the RMI registry at. Default is <tt>127.0.0.1</tt>
;-Dorg.rifidi.edge.core.rmi.port
:The port of the RMI registry Default is <tt>1101</tt>
;-Dorg.rifidi.edge.ale.host
:The hostname to publish the ALE webservices at. Default is <tt>127.0.0.1</tt> '''(NOTE: ALE has been removed in version 1.3)'''
;-Dorg.rifidi.edge.ale.port
:The port to publish the ALE webservices at. Default is <tt>8081</tt> '''(NOTE: ALE has been removed in version 1.3)'''
;-Dorg.rifidi.edge.ale.read
:The service name of the ALE reading service. Default is <tt>ALEService</tt> '''(NOTE: ALE has been removed in version 1.3)'''
;-Dorg.rifidi.edge.ale.logicalreader
:The service name of the ALE logical reader service. Default is <tt>ALELRService</tt> '''(NOTE: ALE has been removed in version 1.3)'''
;-Dorg.rifidi.home
:The Rifidi directory. If not set, it defaults to ${user.dir}
;-Dorg.rifidi.ui.notify
:If set to true, reader adapters will send tag notifications to workbench. Default is true

=rifidi.xml=
The rifidi.xml file is the persistence file for the Rifidi Edge Server. The two important services that are saved are Reader Configurations and Command Configurations.

==Loading a configuration file==
Whenever the edge server starts up, it looks for the file that is specified in the <tt>org.rifidi.configuration</tt> vm flag. After the configuration file is read, the server will attempt to recreate all services specified in the file. If a needed factory is not available, the service will be skipped and recreated when the factory becomes available. For example, suppose the configuration file has an Alien Reader Configuration and an LLRP Reader Configuration. Suppose that when the server starts up, only the Alien plugin is available (so the Alien Reader Factory is available, but the LLRP Reader Factory is not). At this point the Alien Reader is recreated. If later the LLRP plugin is installed, then the LLRP reader will be recreated.

==File Structure==
The edge server uses JAXB to persist a configuration file. Each service will have a serviceID and a factoryID. The serviceID is the unique name of the service, and is used when using the service (such as starting a session on a reader). The factoryID is the ID of the factory that can create a service. The following is an example of file that has one Alien Reader saved.
<pre>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<configurationStore>
<services>
<attributes>
<entry>
<key>ReconnectionInterval</key>
<value>500</value>
</entry>
<entry>
<key>Port</key>
<value>20000</value>
</entry>
<entry>
<key>InvertExternalOutput</key>
<value>0</value>
</entry>
<entry>
<key>PersistTime</key>
<value>-1</value>
</entry>
<entry>
<key>Username</key>
<value>alien</value>
</entry>
<entry>
<key>Password</key>
<value>password</value>
</entry>
<entry>
<key>InvertExternalInput</key>
<value>0</value>
</entry>
<entry>
<key>ReaderNumber</key>
<value>0</value>
</entry>
<entry>
<key>ExternalOutput</key>
<value>0</value>
</entry>
<entry>
<key>IpAddress</key>
<value>127.0.0.1</value>
</entry>
<entry>
<key>MaxNumConnectionAttempts</key>
<value>10</value>
</entry>
<entry>
<key>RFAttenuation</key>
<value>0</value>
</entry>
</attributes>
<factoryID>Alien</factoryID>
<serviceID>Alien_1</serviceID>
</services>
</configurationStore>
</pre>

User's Guide

2013-04-21T06:07:54Z

Matt:

*[http://www.transcends.co/www/docs/Rifidi_Edge_Server_User_1.2.pdf User's Guide for 1.2.0]
*[http://www.transcends.co/www/docs/Rifidi_Edge_Server_User_1.3.pdf User's Guide for 1.3.0]
*[http://www.transcends.co/www/docs/Rifidi_Edge_Server_User_2.0.pdf User's Guide for 2.0.0]
*[http://wiki.rifidi.net/images/6/61/Rifidi_Edge_Server_User_2.1.pdf User's Guide for 2.1.0]

Developer's Guide

2013-04-21T06:05:13Z

Matt:

*[http://www.transcends.co/www/docs/Rifidi_Edge_Server_Developer_1.2.pdf Developer's Guide for 1.2.0]
*[http://www.transcends.co/www/docs/Rifidi_Edge_Server_Developer_1.3.pdf Developer's Guide for 1.3.0]
*[http://www.transcends.co/www/docs/Rifidi_Edge_Server_Developer_2.0.pdf Developer's Guide for 2.0.0]
*[http://wiki.rifidi.net/images/5/51/Rifidi_Edge_Server_Developer_2.1.pdf Developer's Guide for 2.1.0]

User's Guide

2013-04-21T06:03:44Z

Matt:

*[http://www.transcends.co/www/docs/Rifidi_Edge_Server_User_1.2.pdf User's Guide for 1.2.0]
*[http://www.transcends.co/www/docs/Rifidi_Edge_Server_User_1.3.pdf User's Guide for 1.3.0]
*[http://www.transcends.co/www/docs/Rifidi_Edge_Server_User_2.0.pdf User's Guide for 2.0.0]
*[http://wiki.rifidi.net/index.php?title=Image:Rifidi_Edge_Server_User_2.1.pdf User's Guide for 2.1.0]

File:Rifidi Edge Server User 2.1.pdf

2013-04-21T05:51:10Z

Matt:

File:Rifidi Edge Server Developer 2.1.pdf

2013-04-21T05:50:47Z

Matt:

File:Rifidi Edge Server User.pdf

2013-04-21T05:48:57Z

Matt:

Main Page

2013-04-21T03:58:31Z

Matt:

<table border="0" style="width: 100%">
<tr
style="text-align:center;margin-left:auto;margin-right:auto">
<td colspan="2" style="background-color:rgb(240, 247, 255)"><h1>Welcome
to the <strong>RIFIDI Community Wiki</strong></h1>

<p>RIFIDI is an open source RFID Middleware Platform</p>

<p>Please find out how to [[Documentation Guidelines|contribute to the Wiki]] before you begin
editing. </p>
</td>
</tr>
<tr>



<tr
style="text-align:center;margin-left:auto;margin-right:auto">
<td colspan="2" style="background-color:lightpink"><h4>Announcing Rifidi Edge Server 2.1!!!</h4>

<p>Version 2.1 fixes some of the issues that existed in 2.0. See [[Version 2.1]] for details</p>
</td>
</tr>
<tr>

<td>
<table border="0" style="width:80%">
<tr>
<td style="background-color:rgb(240, 247, 255)"><div style="text-align:center" ><strong>Edge Server</strong></div>
<hr>

<p><strong>User Documentation</strong></p>
<ul>
<li>[[Edge Server Getting Started|Getting Started]]</li>
<li>[[User's Guide | User's Guide]]</li>
<li>[[Edge Server Configuration|Configuration]]</li>
<li>[[Edge Server Console|Console]]</li>
<li>[[Edge Server Sensor Plugins | Sensor Plugin User's Guide]]</li>
<li>[[Installing an Application]] </li>
<li>[[Rifidi Edge Licensing - GPL v2]] </li>
</ul>
<p><strong>Developer
Documentation </strong></p>
<ul>
<li>[[Developer's Guide | Developer's Guide]]</li>
<li>[[Rifidi Edge Server Application Tutorials]]</li>
<li>[[Edge Server API]]</li>
<li>[[Sensor Plugin API]]</li>
<li>[[Edge Server Architecture|Architecture]]</li>
<li>[[Edge Server Development Environment|Setting up a Development Environment]]</li>
<li>[[Rifidi App Upgrade Guide|Upgrade a Rifidi App from 1.2 to 1.3]]</li>
<li>[[Edge Server HOWTOs | HOWTOs]]</li>
<li>[[Rifidi Services Jumpstart]]</li>
<li>[[Social Media Jumpstart]]</li>
<li>[[Cloud Jumpstart]]</li>
<li>[[Database Jumpstart]]</li>
<li>[[JMS Jumpstart]]</li>
</ul>
</td>
</tr>
<tr>
<td><p></p>
</td>
</tr>
<tr>
<td style="background-color:rgb(240, 247, 255)"><div style="text-align:center" ><strong>Workbench</strong></div>
<hr>
<p><strong>User Documentation</strong> </p>
<ul>
<li>[[Workbench User's Guide|Getting Started]]</li>
</ul>
</td>
</tr>
<tr>
<td><p></p>
</td>
</tr>
<tr>
<td style="background-color:rgb(240, 247, 255)"><div style="text-align:center" ><strong">Toolkit</strong></div>
<hr>
<p><strong>User Documentation</strong> </p>
<ul>
<li>[[Emulator User's Guide]]</li>
<li>[[Prototyper User's Guide]]</li>
<li>[[Tag Streamer User's Guide]]</li>
<li>[[Release Features]]</li>
<li>[[:Category:userDoc|browse more user documents...]]</li>
</ul>

<p><strong>Developer Documentation </strong></p>
<ul>
<li>[[Emulator documentation summary | Emulator Documentation]]</li>
<li>[[tag streamer documentation summary | Tag Streamer Documentation]]</li>
<li>Virtual [[Reader Guides]]</li>
<li>[[Development Process| How to Develop Rifidi]]</li>
<li> [[:Category:developerDoc|browse more developer documents...]]</li>
</ul>
</td>
</tr>
</table>
</td>
<td valign="top">
<table border="0" style="width:80%">
<tr>
<td style="background-color:rgb(240, 247, 255)"><div style="text-align:center" ><strong>Rifidi Suite</strong></div>
<hr>
<ul>
<li>[[Asset Tracking: An end-to end solution with the Rifidi Platform]]</li>
<li>[[Rifidi roadmap|Rifidi Roadmap]]</li>
<li>[http://rifidi.net/ About Rifidi]</li>
</ul>
</td>
</tr>
<tr>
<td><p></p>
</td>
</tr>
<tr>
<td style="background-color:rgb(240, 247, 255)"><div style="text-align:center" ><strong>General Information</strong></div>
<hr>
<ul>
<li>[[Developer FAQ]]</li>
<li>[[How to Contribute to the Rifidi project]]</li>
</ul>
</td>
</tr>
<tr>
<td><p></p>
</td>
</tr>
<tr>
<td style="background-color:rgb(240, 247, 255)"><div style="text-align:center" ><strong>Useful Links</strong></div>
<hr>
<p><strong>Rifidi Project</strong></p>
<ul>
<li>[http://forums.rifidi.net Rifidi Forums]</li>
<li>[https://trac.rifidi.org/rep-edge-trac/ Rifidi Bug Tracker]
<li>[http://sourceforge.net/projects/rifidi/ Rifidi's Sourceforge Page]</li>
<li>[https://svn.rifidi.org/svn/rep-external Rifidi Emulator/Prototyper/Tagstreamer Source SVN]</li>
<li>[https://svn.rifidi.org/svn/rep-edge Rifidi Edge/Workbench Source SVN]</li>
<li>[http://www.transcends.co Transcends' Website]</li>
</ul>

<p><strong>Other Projects</strong></p>
<ul>
<li>[http://static.springsource.org/spring/docs/3.1.x/spring-framework-reference/html/ Spring]</li>
<li>[http://esper.codehaus.org/about/esper/esper.html Esper is a trademark of EsperTech Inc]</li>
<li>[http://help.eclipse.org/juno/index.jsp Eclipse]</li>
<li>[http://springsource.com/repository/app/ Spring Enterprise Bundle Repository]</li>
</ul>
</td>
</tr>
</table>
</td>
</tr>
</table>

Version 2.1

2013-04-21T00:47:38Z

Matt:

==Changes in 2.1==

We are pleased to announce the release of Rifidi 2.1!

Here are some of the new features:

===Small bug fixes===

There were several smaller bugs present which have now been fixed.

===Thinkify now works on Windows===

The Thinkify TR-50/TR-200 was not working on windows for some people. This has now been fixed.

==Links==
Javadocs (method signatures same as 2.0.0):
http://www.transcends.co/www/javadoc/edge2.0.0/

[[Developer's_Guide]]

[[User's_Guide]]

Version 2.1

2013-04-21T00:44:21Z

Matt:

Version 2.1

2013-04-21T00:43:54Z

Matt: New page: We are pleased to announce the release of Rifidi 2.1! Here are some of the new features: ===Small bug fixes=== There were several smaller bugs present which have now been fixed. ===T...

We are pleased to announce the release of Rifidi 2.1!

Here are some of the new features:

===Small bug fixes===

There were several smaller bugs present which have now been fixed.

===Thinkify now works on Windows===

The Thinkify TR-50/TR-200 was not working on windows for some people. This has now been fixed.

Version 2.0

2013-01-16T05:24:17Z

Matt: /* Changes in 2.0 */

==Changes in 2.0==

===Equinox/OSGi upgraded from 3.5 to 3.8===

We're happy to announce that we've upgraded Equinox from version 3.5 to 3.8. With it comes a performance improvement and a new expanded console.

===Thinkify TR-50 Embedded reader support===

We have added support for the Thinkify TR-50 reader. To learn more about the Thinkify,

LLRP added GPIO support now, so you can test GPI ports and set GPO ports on an LLRP reader from within a RifidiApp.

===Spring upgraded to 3.1.2===

Spring has been upgraded and all new features available in 3.1.2 are now available for RifidiApps.

===Esper upgraded to 4.7===

Esper has been upgraded to version 4.7. Performance has increased, and there are new features.

===Amazon cloud support===
[[Cloud Jumpstart|AWS Cloud Jumpstart]].

===Changes to Esper for RifidiApps with Custom esper rules===

Example:

See Esper documentation for full list of changes
http://esper.codehaus.org/esper/documentation/documentation.html

===Bug Fixes===

You can now start Rifidi while offline without issue. The issue with the installer throwing an exception when offline is now fixed.

==Links==
Javadocs:
http://www.transcends.co/www/javadoc/edge2.0.0/

[[Developer's_Guide]]

[[User's_Guide]]

Version 2.0

2013-01-16T05:24:00Z

Matt:

==Changes in 2.0==

===Equinox/OSGi upgraded from 3.5 to 3.8===

We're happy to announce that we've upgraded Equinox from version 3.5 to 3.8. With it comes a performance improvement and a new expanded console.

===Thinkify TR-50 Embedded reader support===

We have added support for the Thinkify TR-50 reader. To learn more about the Thinkify,

LLRP added GPIO support now, so you can test GPI ports and set GPO ports on an LLRP reader from within a RifidiApp.

===Performance increase and optimization for embedded devices===

===Spring upgraded to 3.1.2===

Spring has been upgraded and all new features available in 3.1.2 are now available for RifidiApps.

===Esper upgraded to 4.7===

Esper has been upgraded to version 4.7. Performance has increased, and there are new features.

===Amazon cloud support===
[[Cloud Jumpstart|AWS Cloud Jumpstart]].

===Changes to Esper for RifidiApps with Custom esper rules===

Example:

See Esper documentation for full list of changes
http://esper.codehaus.org/esper/documentation/documentation.html

===Bug Fixes===

You can now start Rifidi while offline without issue. The issue with the installer throwing an exception when offline is now fixed.

==Links==
Javadocs:
http://www.transcends.co/www/javadoc/edge2.0.0/

[[Developer's_Guide]]

[[User's_Guide]]

Version 2.0

2013-01-16T03:09:45Z

Matt:

==Changes in 2.0==

===Equinox/OSGi upgraded from 3.5 to 3.8===

We're happy to announce that we've upgraded Equinox from version 3.5 to 3.8. With it comes a performance improvement and a new expanded console.

===Thinkify TR-50 Embedded reader support===

We have added support for the Thinkify TR-50 reader. To learn more about the Thinkify,

LLRP added GPIO support now, so you can test GPI ports and set GPO ports on an LLRP reader from within a RifidiApp.

===Performance increase and optimization for embedded devices===

===Spring upgraded to 3.1.2===

Spring has been upgraded.

===Esper upgraded to 4.7===

Esper has been upgraded to version 4.7. Performance has increased, and there are new features.

===Amazon cloud support===
[[Cloud Jumpstart|AWS Cloud Jumpstart]].

===Changes to Esper for RifidiApps with Custom esper rules===

Example:

See Esper documentaion for full list of changes
http://esper.codehaus.org/esper/documentation/documentation.html

===Bug Fixes===

You can now start rifidi when offline with no issues
The issue with the installer throwing an exception when offline is now fixed

==Links==
Javadocs:
http://www.transcends.co/www/javadoc/edge2.0.0/

[[Developer's_Guide]]

[[User's_Guide]]

Version 2.0

2013-01-16T01:47:55Z

Matt: /* Equinox/OSGi upgraded from 3.5 to 3.8 */

==Changes in 2.0==

===Equinox/OSGi upgraded from 3.5 to 3.8===

We're happy to announce that we've upgraded Equinox from version 3.5 to 3.8. With it comes a performance improvement and a new expanded console.

===Thinkify TR-50 Embedded reader support===

LLRP added GPIO support now, so you can test GPI ports and set GPO ports on an LLRP reader from within a RifidiApp.

===Performance increase and optimization for embedded devices===

===Spring upgraded to 3.1.2===

===Esper upgraded to 4.7===

Performance Increase and Extended Commands

===Amazon cloud support===
[[Cloud Jumpstart|AWS Cloud Jumpstart]].

===Changes to Esper for RifidiApps with Custom esper rules===

Example:

See Esper documentaion for full list of changes
http://esper.codehaus.org/esper/documentation/documentation.html

===Bug Fixes===

You can now start rifidi when offline with no issues
The issue with the installer throwing an exception when offline is now fixed

==Links==
Javadocs:
http://www.transcends.co/www/javadoc/edge2.0.0/

[[Developer's_Guide]]

[[User's_Guide]]

Version 2.0

2013-01-10T23:25:40Z

Matt:

==Changes in 2.0==

===Equinox/OSGi upgraded from 3.5 to 3.8===

Performance Increase and Extended Commands

===Thinkify TR-50 Embedded reader support===

LLRP added GPIO support now, so you can test GPI ports and set GPO ports on an LLRP reader from within a RifidiApp.

===Performance increase and optimization for embedded devices===

===Spring upgraded to 3.1.2===

===Esper upgraded to 4.7===

Performance Increase and Extended Commands

===Amazon cloud support===
[[Cloud Jumpstart|AWS Cloud Jumpstart]].

===Changes to Esper for RifidiApps with Custom esper rules===

Example:

See Esper documentaion for full list of changes
http://esper.codehaus.org/esper/documentation/documentation.html

===Bug Fixes===

You can now start rifidi when offline with no issues
The issue with the installer throwing an exception when offline is now fixed

==Links==
Javadocs:
http://www.transcends.co/www/javadoc/edge2.0.0/

[[Developer's_Guide]]

[[User's_Guide]]

Edge Server HOWTOs

2012-11-14T01:06:55Z

Matt:

*[[How to change logging levels]]
*[[How to export a service using RMI]]
*[[How to export a service using web services]]
*[[EdgeServerJMS#Setting up a Consumer|How to consume tag events from the Internal JMS Message Bus]]
*[[How to write esper queries]]
*[[How to configure Manifest.MF in my bundle]]
*[[How to configure spring.xml in my bundle]]
*[[How to use OSGi Services]]
*[[How to create a sensor plugin]]
*[[How to configure the run configuration in eclipse]]
*[[How to Add your own event types to Esper]]
*[[How to export your custom Rifidi application]]
*[[Rifidi App Upgrade Guide|How to upgrade a 1.2 RifidiApp to 1.3]]
*[[1.3 Maven Build]]
*[[Adding Third Party Libraries]]
*[[Custom Esper Rules Jumpstart]]
*[[GPIO Tutorial]]

Edge Server HOWTOs

2012-11-14T01:06:37Z

Matt:

File:DBApp.zip

2012-07-10T22:05:06Z

Matt: uploaded a new version of "Image:DBApp.zip"

A sample database application for Rifidi Edge. Eclipse project and compiled version included.

Alien Edge Server Guide

2012-05-15T00:49:43Z

Matt:

==Getting started==

This guide will help you quickly get an Alien reader up and reading tags on Rifidi Edge. The supported Alien readers are the 9800, the 9900, the 8800, and the 9600. Other versions haven't been tested, but may still work.

*Start the edge server and the edge client. Connect the client to the server.
*Right click on the 'Edge Server' icon in the 'Edge Server View' and select 'New Reader'.
*Select 'Alien' from the drop-down and click 'Next'.
*Type in the IP and port of the reader you wish to in their respective boxes. If you are using an emulated Alien, you can check this in the emulator itself. If you are connecting to a physical reader, you might need to use the discovery tool in the Alien software to find out what the IP and port are if you don't know them offhand.
*Set the username and password of the reader. The default is 'alien' and 'password', respectively.
*Select the reconnect interval (in milliseconds). If you want the Edge Server to keep trying to connect if the reader loses connection while running or if it can't connect to start with, you can set this value to what you want (in milliseconds). If you are unsure, you can just leave it at the default 500.
*Select the maximum number of times the server will try to connect to an unresponsive reader. -1 means it will keep going until it gets a connection. To turn this feature off, set it to 0.

==Reading Tags==

Now that the reader is set up, its time to actually connect to it and read some tags.

*First, click on the reader icon that has appeared under the 'Edge Server'. It probably looks something like 'Alien_1'. Now look at the 'properties' tab at the bottom. There are many properties here, some of which can be adjusted. If you wish to adjust a property, type in the new value you want, press 'enter', then right click on the reader and select 'Commit Property Changes'. If you wish to learn more about a specific property, consult the Alien documentation.
*Right click the reader and press 'create session'. If the IP is correct and the reader is turned on, the session should go to 'green'. If something is wrong, it will stay yellow or go back to red. Check and make sure the IP and port are correct and the reader is turned on if you have trouble connecting.
*Now go to the bottom left window, the 'Command View'. Right click on the 'Alien-Poll' folder and click 'create command template'.
*Click on the command you just created, and set the options you wish in the same way you set the reader properties (just with the command instead).
*Now right click on the session you created under the reader and press 'submit job'. Select the 'Alien-Poll' job you created, select 'Recurring Execution', and select the interval you want to read tags for (default is 1 second).
*Press 'Finish'. Congratulations! You are now reading tags from an Alien reader.

Database Jumpstart

2012-04-13T23:35:30Z

Matt:

File:DBApp.zip

2012-04-13T23:32:01Z

Matt: A sample database application for Rifidi Edge. Eclipse project and compiled version included.

A sample database application for Rifidi Edge. Eclipse project and compiled version included.

Cloud Jumpstart

2012-04-13T21:32:50Z

Matt:

==Create a RifidiApp==
* 1. Create a RifidiApp. First, be sure to set up a developer environment using [[Edge_Server_Development_Environment|these steps]].
Then check the developer guide for [[Developer%27s_Guide|creating your own Rifidi App]].
Check the section starting at "Importing a Project Template" on page 5 for how to do this.

After your application is set up, you'll have to choose how you want to receive your tags. Tags that are read by RFID readers will be inserted into an event processing engine called Esper. There are a few different ways to receive these tags, as outlined here:

==Import Services==
* 2. You can use one of the default services to send and receive tags. You can see a description of the default services [[Rifidi_Services_Jumpstart|here]].
You can also see an example of the two services in action in the "Northwind" example (specifically, the "ReadZoneMonitoringService" and the "StableSetService"). See the developer's guide for an overview of the Northwind example. The source code for the example (which can be imported as a project) is in the "apps" folder of the SDK.

Taking the ReadZoneMonitoringService as an example, a method will be called on designated classes whenever a tag arrives or departs. You can find out the ID of this tag (as well as other useful information) and then do whatever you wish with it, including writing the event to a cloud or to social media.

==Create Custom Esper Rules==
* 3. You can also write your own custom Esper rules, usually in concert with the ReadZoneMonitoringService. You can find out how to create custom Esper rules at the [[Custom Esper Rules Jumpstart]] page.

==Add Third Party Libraries==
* 4. You may need to add a third party library to your app. Check the [[Adding Third Party Libraries]] page to find out how to do that.

==Cloud Interface==
* 5. There are many ways you can communicate with the cloud, and many libraries that you can use to communicate with it. For this example we'll be using the [https://aws.amazon.com/sdkforjava/ Amazon AWS SDK for Java], specifically the [https://aws.amazon.com/simpledb/ SimpleDB]. There is a great example for how to use the SimpleDB [https://www.ibm.com/developerworks/java/library/j-javadev2-9/ here]. After you set up the credentials for the system, you can talk to the SimpleDB in a similar fashion that you would talk to any other database.

<pre>
@Override
public void tagArrived(TagReadEvent tag) {
System.out.println("Tag arrived at location " + location + ": " + tag.getTag().getFormattedID());
List<ReplaceableItem> data = new ArrayList<ReplaceableItem>();
data.add(new ReplaceableItem().withName(tag.getTag().getFormattedID()).withAttributes(
new ReplaceableAttribute().withName("Antenna").withValue(tag.getAntennaID()),
new ReplaceableAttribute().withName("Timestamp").withValue(tag.getTimestamp())));
//"sdb" is the SimpleDB client object, "domain" is the name of the domain you wish to insert the tag in
sdb.batchPutAttributes(new BatchPutAttributesRequest(domain, data));
}
</pre>

Cloud Jumpstart

2012-04-13T17:39:39Z

Matt:

Cloud Jumpstart

2012-04-13T17:35:57Z

Matt:

Social Media Jumpstart

2012-04-10T18:50:40Z

Matt:

==Create a RifidiApp==
* 1. Create a RifidiApp. First, be sure to set up a developer environment using [[Edge_Server_Development_Environment|these steps]].
Then check the developer guide for [[Developer%27s_Guide|creating your own Rifidi App]].
Check the section starting at "Importing a Project Template" on page 5 for how to do this.

After your application is set up, you'll have to choose how you want to receive your tags. Tags that are read by RFID readers will be inserted into an event processing engine called Esper. There are a few different ways to receive these tags, as outlined here:

==Import Services==
* 2. You can use one of the default services to send and receive tags. You can see a description of the default services [[Rifidi_Services_Jumpstart|here]].
You can also see an example of the two services in action in the "Northwind" example (specifically, the "ReadZoneMonitoringService" and the "StableSetService"). See the developer's guide for an overview of the Northwind example. The source code for the example (which can be imported as a project) is in the "apps" folder of the SDK.

Taking the ReadZoneMonitoringService as an example, a method will be called on designated classes whenever a tag arrives or departs. You can find out the ID of this tag (as well as other useful information) and then do whatever you wish with it, including writing the event to a cloud or to social media.

==Create Custom Esper Rules==
* 3. You can also write your own custom Esper rules, usually in concert with the ReadZoneMonitoringService. You can find out how to create custom Esper rules at the [[Custom Esper Rules Jumpstart]] page.

==Add Third Party Libraries==
* 4. You may need to add a third party library to your app. Check the [[Adding Third Party Libraries]] page to find out how to do that.

==Link to Social Media Interface==
* 5. You can link to a social media interface using the [http://www.springsource.org/spring-social Spring Social] [http://static.springsource.org/spring-social/docs/1.0.x/reference/html/serviceprovider.html API].

Here is an example of a link to social media within an "arrived" method of a subscriber:

<pre>
@Override
public void tagArrived(TagReadEvent tag) {
System.out.println("Tag arrived at location " + location + ": " + tag.getTag().getFormattedID());
TwitterTemplate twitter = new TwitterTemplate(apiKey, apiSecret, accessToken, accessTokenSecret);
twitter.updateStatus("Tag " + tag.getTag.getFormattedID() + " has arrived at location " + location + "!");

FacebookTemplate facebook = new FacebookTemplate(accessToken);
facebook.updateStatus("Tag " + tag.getTag.getFormattedID() + " has arrived at location " + location + "!");
}
</pre>

You'll need the credentials for a twitter and/or facebook account. You can find a good explanation of those credentials [http://gognamunish.blogspot.com/2011/01/accessing-social-network-using-spring.html here].

For this example we simply used the tag ID and the location that the Northwind project has as an example of publishing information to facebook or twitter. In reality the tagID probably wouldn't be particularly useful, and it would be advisable to go to the database and get some useful information the tag ID points to (such as the name of a person, or an item).

Database Jumpstart

2012-04-10T01:09:54Z

Matt:

Database Jumpstart

2012-04-10T01:08:39Z

Matt: New page: ==Create a RifidiApp== * 1. Create a RifidiApp. First, be sure to set up a developer environment using these steps. Then check the developer guid...

Main Page

2012-04-10T00:23:23Z

Matt:

<table border="0" style="width: 100%">
<tr
style="text-align:center;margin-left:auto;margin-right:auto">
<td colspan="2" style="background-color:rgb(240, 247, 255)"><h1>Welcome
to the <strong>RIFIDI Community Wiki</strong></h1>

<p>RIFIDI is an open source RFID Middleware Platform</p>

<p>Please find out how to [[Documentation Guidelines|contribute to the Wiki]] before you begin
editing. </p>
</td>
</tr>
<tr>



<tr
style="text-align:center;margin-left:auto;margin-right:auto">
<td colspan="2" style="background-color:lightpink"><h4>Announcing Rifidi Edge Server 1.3.1!!!</h4>

<p>Version 1.3.1 offers many new features, including an improved LLRP plugin. See [[Version 1.3.1]] for details</p>
</td>
</tr>
<tr>

<td>
<table border="0" style="width:80%">
<tr>
<td style="background-color:rgb(240, 247, 255)"><div style="text-align:center" ><strong>Edge Server</strong></div>
<hr>

<p><strong>User Documentation</strong></p>
<ul>
<li>[[Edge Server Getting Started|Getting Started]]</li>
<li>[[User's Guide | User's Guide]]</li>
<li>[[Edge Server Configuration|Configuration]]</li>
<li>[[Edge Server Console|Console]]</li>
<li>[[Edge Server Sensor Plugins | Sensor Plugin User's Guide]]
<li>[[Installing an Application]]
</ul>

<p><strong>Developer
Documentation </strong></p>
<ul>
<li>[[Developer's Guide | Developer's Guide]]</li>
<li>[[Rifidi Edge Server Application Tutorials]]</li>
<li>[[Edge Server API]]</li>
<li>[[Sensor Plugin API]]</li>
<li>[[Edge Server Architecture|Architecture]]</li>
<li>[[Edge Server Development Environment|Setting up a Development Environment]]</li>
<li>[[Rifidi App Upgrade Guide|Upgrade a Rifidi App from 1.2 to 1.3]]</li>
<li>[[Edge Server HOWTOs | HOWTOs]]</li>
<li>[[Rifidi Services Jumpstart]]</li>
<li>[[Social Media Jumpstart]]</li>
<li>[[Cloud Jumpstart]]</li>
<li>[[Database Jumpstart]]</li>
<li>[[JMS Jumpstart]]</li>
</ul>
</td>
</tr>
<tr>
<td><p></p>
</td>
</tr>
<tr>
<td style="background-color:rgb(240, 247, 255)"><div style="text-align:center" ><strong>Workbench</strong></div>
<hr>
<p><strong>User Documentation</strong> </p>
<ul>
<li>[[Workbench User's Guide|Getting Started]]</li>
</ul>
</td>
</tr>
<tr>
<td><p></p>
</td>
</tr>
<tr>
<td style="background-color:rgb(240, 247, 255)"><div style="text-align:center" ><strong">Toolkit</strong></div>
<hr>
<p><strong>User Documentation</strong> </p>
<ul>
<li>[[Emulator User's Guide]]</li>
<li>[[Prototyper User's Guide]]</li>
<li>[[Tag Streamer User's Guide]]</li>
<li>[[Release Features]]</li>
<li>[[:Category:userDoc|browse more user documents...]]</li>
</ul>

<p><strong>Developer Documentation </strong></p>
<ul>
<li>[[Emulator documentation summary | Emulator Documentation]]</li>
<li>[[tag streamer documentation summary | Tag Streamer Documentation]]</li>
<li>Virtual [[Reader Guides]]</li>
<li>[[Development Process| How to Develop Rifidi]]</li>
<li> [[:Category:developerDoc|browse more developer documents...]]</li>
</ul>
</td>
</tr>
</table>
</td>
<td valign="top">
<table border="0" style="width:80%">
<tr>
<td style="background-color:rgb(240, 247, 255)"><div style="text-align:center" ><strong>Rifidi Suite</strong></div>
<hr>
<ul>
<li>[[Asset Tracking: An end-to end solution with the Rifidi Platform]]</li>
<li>[[Rifidi roadmap|Rifidi Roadmap]]</li>
<li>[http://rifidi.org/ About Rifidi]</li>
</ul>
</td>
</tr>
<tr>
<td><p></p>
</td>
</tr>
<tr>
<td style="background-color:rgb(240, 247, 255)"><div style="text-align:center" ><strong>General Information</strong></div>
<hr>
<ul>
<li>[[Developer FAQ]]</li>
<li>[[How to Contribute to the Rifidi project]]</li>
</ul>
</td>
</tr>
<tr>
<td><p></p>
</td>
</tr>
<tr>
<td style="background-color:rgb(240, 247, 255)"><div style="text-align:center" ><strong>Useful Links</strong></div>
<hr>
<p><strong>Rifidi Project</strong></p>
<ul>
<li>[http://forums.rifidi.org Rifidi Forums]</li>
<li>[https://trac.rifidi.org/rep-edge-trac/ Rifidi Bug Tracker]
<li>[http://sourceforge.net/projects/rifidi/ Rifidi's Sourceforge Page]</li>
<li>[https://svn.rifidi.org/svn/rep-external Rifidi Emulator/Prototyper/Tagstreamer Source SVN]</li>
<li>[https://svn.rifidi.org/svn/rep-edge Rifidi Edge/Workbench Source SVN]</li>
<li>[http://www.transcends.co Transcends' Website]</li>
</ul>

<p><strong>Other Projects</strong></p>
<ul>
<li>[http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/ Spring]</li>
<li>[http://esper.codehaus.org/about/esper/esper.html Esper]</li>
<li>[http://help.eclipse.org/galileo/index.jsp Eclipse]</li>
<li>[http://springsource.com/repository/app/ Spring Enterprise Bundle Repository]</li>
</ul>
</td>
</tr>
</table>
</td>
</tr>
</table>

Cloud Jumpstart

2012-04-10T00:20:12Z

Matt: New page: ==Create a RifidiApp== * 1. Create a RifidiApp. First, be sure to set up a developer environment using these steps. Then check the developer guid...

Social Media Jumpstart

2012-04-09T22:45:48Z

Matt:

Social Media Jumpstart

2012-04-09T21:51:46Z

Matt:

Social Media Jumpstart

2012-04-09T21:51:28Z

Matt:

Social Media Jumpstart

2012-04-09T21:51:18Z

Matt:

Social Media jumpstart:

==Create a RifidiApp==
* 1. Create a RifidiApp. First, be sure to set up a developer environment using [[Edge_Server_Development_Environment|these steps]].
Then check the developer guide for [[Developer%27s_Guide|creating your own Rifidi App]].
Check the section starting at "Importing a Project Template" on page 5 for how to do this.

After your application is set up, you'll have to choose how you want to receive your tags. Tags that are read by RFID readers will be inserted into an event processing engine called Esper. There are a few different ways to receive these tags, as outlined here:

==Import Services==
* 2. You can use one of the default services to send and receive tags. You can see a description of the default services [[Rifidi_Services_Jumpstart|here]].
You can also see an example of the two services in action in the "Northwind" example (specifically, the "ReadZoneMonitoringService" and the "StableSetService"). See the developer's guide for an overview of the Northwind example. The source code for the example (which can be imported as a project) is in the "apps" folder of the SDK.

Taking the ReadZoneMonitoringService as an example, a method will be called on designated classes whenever a tag arrives or departs. You can find out the ID of this tag (as well as other useful information) and then do whatever you wish with it, including writing the event to a cloud or to social media.

==Create Custom Esper Rules==
* 3. You can also write your own custom Esper rules, usually in concert with the ReadZoneMonitoringService. You can find out how to create custom Esper rules at the [[Custom_Esper_Rules_Jumpstart]] page.

==Add Third Party Libraries==
* 4. You may need to add a third party library to your app. Check the [[Adding Third Party Libraries]] page to find out how to do that.

==Link to Social Media Interface==
* 5. You can link to a social media interface

Main Page

2012-04-09T21:43:52Z

Matt:

<table border="0" style="width: 100%">
<tr
style="text-align:center;margin-left:auto;margin-right:auto">
<td colspan="2" style="background-color:rgb(240, 247, 255)"><h1>Welcome
to the <strong>RIFIDI Community Wiki</strong></h1>

<p>RIFIDI is an open source RFID Middleware Platform</p>

<p>Please find out how to [[Documentation Guidelines|contribute to the Wiki]] before you begin
editing. </p>
</td>
</tr>
<tr>



<tr
style="text-align:center;margin-left:auto;margin-right:auto">
<td colspan="2" style="background-color:lightpink"><h4>Announcing Rifidi Edge Server 1.3.1!!!</h4>

<p>Version 1.3.1 offers many new features, including an improved LLRP plugin. See [[Version 1.3.1]] for details</p>
</td>
</tr>
<tr>

<td>
<table border="0" style="width:80%">
<tr>
<td style="background-color:rgb(240, 247, 255)"><div style="text-align:center" ><strong>Edge Server</strong></div>
<hr>

<p><strong>User Documentation</strong></p>
<ul>
<li>[[Edge Server Getting Started|Getting Started]]</li>
<li>[[User's Guide | User's Guide]]</li>
<li>[[Edge Server Configuration|Configuration]]</li>
<li>[[Edge Server Console|Console]]</li>
<li>[[Edge Server Sensor Plugins | Sensor Plugin User's Guide]]
<li>[[Installing an Application]]
</ul>

<p><strong>Developer
Documentation </strong></p>
<ul>
<li>[[Developer's Guide | Developer's Guide]]</li>
<li>[[Rifidi Edge Server Application Tutorials]]</li>
<li>[[Edge Server API]]</li>
<li>[[Sensor Plugin API]]</li>
<li>[[Edge Server Architecture|Architecture]]</li>
<li>[[Edge Server Development Environment|Setting up a Development Environment]]</li>
<li>[[Rifidi App Upgrade Guide|Upgrade a Rifidi App from 1.2 to 1.3]]</li>
<li>[[Edge Server HOWTOs | HOWTOs]]</li>
<li>[[Rifidi Services Jumpstart]]</li>
</ul>
</td>
</tr>
<tr>
<td><p></p>
</td>
</tr>
<tr>
<td style="background-color:rgb(240, 247, 255)"><div style="text-align:center" ><strong>Workbench</strong></div>
<hr>
<p><strong>User Documentation</strong> </p>
<ul>
<li>[[Workbench User's Guide|Getting Started]]</li>
</ul>
</td>
</tr>
<tr>
<td><p></p>
</td>
</tr>
<tr>
<td style="background-color:rgb(240, 247, 255)"><div style="text-align:center" ><strong">Toolkit</strong></div>
<hr>
<p><strong>User Documentation</strong> </p>
<ul>
<li>[[Emulator User's Guide]]</li>
<li>[[Prototyper User's Guide]]</li>
<li>[[Tag Streamer User's Guide]]</li>
<li>[[Release Features]]</li>
<li>[[:Category:userDoc|browse more user documents...]]</li>
</ul>

<p><strong>Developer Documentation </strong></p>
<ul>
<li>[[Emulator documentation summary | Emulator Documentation]]</li>
<li>[[tag streamer documentation summary | Tag Streamer Documentation]]</li>
<li>Virtual [[Reader Guides]]</li>
<li>[[Development Process| How to Develop Rifidi]]</li>
<li> [[:Category:developerDoc|browse more developer documents...]]</li>
</ul>
</td>
</tr>
</table>
</td>
<td valign="top">
<table border="0" style="width:80%">
<tr>
<td style="background-color:rgb(240, 247, 255)"><div style="text-align:center" ><strong>Rifidi Suite</strong></div>
<hr>
<ul>
<li>[[Asset Tracking: An end-to end solution with the Rifidi Platform]]</li>
<li>[[Rifidi roadmap|Rifidi Roadmap]]</li>
<li>[http://rifidi.org/ About Rifidi]</li>
</ul>
</td>
</tr>
<tr>
<td><p></p>
</td>
</tr>
<tr>
<td style="background-color:rgb(240, 247, 255)"><div style="text-align:center" ><strong>General Information</strong></div>
<hr>
<ul>
<li>[[Developer FAQ]]</li>
<li>[[How to Contribute to the Rifidi project]]</li>
</ul>
</td>
</tr>
<tr>
<td><p></p>
</td>
</tr>
<tr>
<td style="background-color:rgb(240, 247, 255)"><div style="text-align:center" ><strong>Useful Links</strong></div>
<hr>
<p><strong>Rifidi Project</strong></p>
<ul>
<li>[http://forums.rifidi.org Rifidi Forums]</li>
<li>[https://trac.rifidi.org/rep-edge-trac/ Rifidi Bug Tracker]
<li>[http://sourceforge.net/projects/rifidi/ Rifidi's Sourceforge Page]</li>
<li>[https://svn.rifidi.org/svn/rep-external Rifidi Emulator/Prototyper/Tagstreamer Source SVN]</li>
<li>[https://svn.rifidi.org/svn/rep-edge Rifidi Edge/Workbench Source SVN]</li>
<li>[http://www.transcends.co Transcends' Website]</li>
</ul>

<p><strong>Other Projects</strong></p>
<ul>
<li>[http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/ Spring]</li>
<li>[http://esper.codehaus.org/about/esper/esper.html Esper]</li>
<li>[http://help.eclipse.org/galileo/index.jsp Eclipse]</li>
<li>[http://springsource.com/repository/app/ Spring Enterprise Bundle Repository]</li>
</ul>
</td>
</tr>
</table>
</td>
</tr>
</table>