Rifidi Services Jumpstart - Revision history

Bppause at 01:44, 15 October 2014

2014-10-15T01:44:10Z

Show changes

Bppause: /* Example Rifidi Services Application */

2014-09-23T21:12:20Z

‎Example Rifidi Services Application

Bppause: /* Example Rifidi Services Application */

2014-09-23T21:02:29Z

‎Example Rifidi Services Application

Bppause: /* Example Rifidi Services Application */

2014-09-23T16:10:53Z

‎Example Rifidi Services Application

Bppause: /* Example Rifidi Services Application */

2014-09-23T16:09:48Z

‎Example Rifidi Services Application

Bppause: /* Example Rifidi Services Application */

2014-09-23T16:09:30Z

‎Example Rifidi Services Application

Show changes

Bppause at 11:22, 19 September 2014

2014-09-19T11:22:11Z

Bppause at 10:19, 6 April 2014

2014-04-06T10:19:38Z

Bppause at 10:19, 6 April 2014

2014-04-06T10:19:09Z

Matt: /* How to use a Service */

2012-04-04T20:47:51Z

‎How to use a Service

@@ Line 121: / Line 121: @@
 =Example Rifidi Services Application=
 Here is where one can find the sources for the sample Rifidi Services Application
-[https://transcends.svn.cloudforge.com/rifidi/rifidi/trunk/apps/org.rifidi.app.rifidiservices/ Rifidi Database App using Rifidi SDK]
+[https://transcends.svn.cloudforge.com/rifidi/rifidi/trunk/apps/org.rifidi.app.rifidiservices/ Rifidi Services App using Rifidi SDK]
 Note: The example application show the use of all the out of the box Rifidi Services mentioned above in a scenario for monitoring events for a front door with one reader ( 1 to 1 relationship between readzone and reader) and back door with 2 readers (1 to many relationship between readzone and reader using regular expressions)
 *Note: Link to rifidi.xml  - listed below as well - [https://transcends.svn.cloudforge.com/rifidi/rifidi/trunk/apps/org.rifidi.app.rifidiservices/RifidiServices/rifidi.xml rifidi.xml for Rifidi Services App]

@@ Line 124: / Line 124: @@
 Note: The example application show the use of all the out of the box Rifidi Services mentioned above in a scenario for monitoring events for a front door with one reader ( 1 to 1 relationship between readzone and reader) and back door with 2 readers (1 to many relationship between readzone and reader using regular expressions)
 *Note: Link to rifidi.xml  - listed below as well - [https://transcends.svn.cloudforge.com/rifidi/rifidi/trunk/apps/org.rifidi.app.rifidiservices/RifidiServices/rifidi.xml rifidi.xml for Rifidi Services App]
 <pre>

@@ Line 123: / Line 123: @@
 [https://transcends.svn.cloudforge.com/rifidi/rifidi/trunk/apps/org.rifidi.app.rifidiservices/ Rifidi Database App using Rifidi SDK]
 Note: The example application show the use of all the out of the box Rifidi Services mentioned above in a scenario for monitoring events for a front door with one reader ( 1 to 1 relationship between readzone and reader) and back door with 2 readers (1 to many relationship between readzone and reader using regular expressions)
-*Note: Link to rifidi.xml  - listed below as well - [https://transcends.svn.cloudforge.com/rifidi/rifidi/trunk/apps/org.rifidi.app.rifidiservices/RifidiServices/rifidi.xml]
+*Note: Link to rifidi.xml  - listed below as well - [https://transcends.svn.cloudforge.com/rifidi/rifidi/trunk/apps/org.rifidi.app.rifidiservices/RifidiServices/rifidi.xml rifidi.xml for Rifidi Services App]
 <pre>

@@ Line 123: / Line 123: @@
 [https://transcends.svn.cloudforge.com/rifidi/rifidi/trunk/apps/org.rifidi.app.rifidiservices/ Rifidi Database App using Rifidi SDK]
 Note: The example application show the use of all the out of the box Rifidi Services mentioned above in a scenario for monitoring events for a front door with one reader ( 1 to 1 relationship between readzone and reader) and back door with 2 readers (1 to many relationship between readzone and reader using regular expressions)
-Note: Link to rifidi.xml  - listed below as well - [https://transcends.svn.cloudforge.com/rifidi/rifidi/trunk/apps/org.rifidi.app.rifidiservices/RifidiServices/rifidi.xml]
+*Note: Link to rifidi.xml  - listed below as well - [https://transcends.svn.cloudforge.com/rifidi/rifidi/trunk/apps/org.rifidi.app.rifidiservices/RifidiServices/rifidi.xml]
 <pre>

← Older revision		Revision as of 11:22, 19 September 2014
Line 118:		Line 118:

	We give a subscriber, the readzone, and a timeout with given units. Now, whenever a tag arrives at the readzone, the "arrived" method will get called in the subscriber class.		We give a subscriber, the readzone, and a timeout with given units. Now, whenever a tag arrives at the readzone, the "arrived" method will get called in the subscriber class.
		+
		+	=Example Rifidi Services Application=
		+	Here is where one can find the sources for the sample Rifidi Services Application
		+	[https://transcends.svn.cloudforge.com/rifidi/rifidi/trunk/apps/org.rifidi.app.rifidiservices/ Rifidi Database App using Rifidi SDK]
		+	Note: The example application show the use of all the out of the box Rifidi Services mentioned above in a scenario for monitoring events for a front door with one reader ( 1 to 1 relationship between readzone and reader) and back door with 2 readers (1 to many relationship between readzone and reader using regular expressions)

@@ Line 16: / Line 16: @@
 This service will notify you at given intervals of all tags currently seen at the given readzones.
-==RSSI Monitoring Service
+==RSSI Monitoring Service==
 This service monitors which readzone returns the highest average RSSI value for a tag in a given
 duration. It returns a reader and epc code when the reader with the highest RSSI value changes for the

@@ Line 15: / Line 15: @@
 ==UniqueTagBatchIntervalService==
 This service will notify you at given intervals of all tags currently seen at the given readzones.
 =How to use a Service=

@@ Line 73: / Line 73: @@
 For simplicity's sake I've removed most of the functionality and all of the comments from this class.  The actual class itself is much more descriptive, and much more useful.  For this class, an alert will be printed whenever a tag arrives in the monitored readzone.  You can do whatever you wish when the tag arrives, however, such as inserting it into a database, posting the result to facebook, or adding an event to Amazon cloud.
-Now that we have a subscriber class, we can create one of them in our application class:
+Now that we have a subscriber class, we can create one of them in our application class (in the start method):
 <pre>
@@ Line 81: / Line 81: @@
 The final variable DOCK_DOOR is a string describing the location that we pass in to use in the System.out statement.
-We also have to define a readzone.  In the case of the Northwind I simply defined a readzone in the "readzone-dockdoor.properties" file in the "readzone" folder inside the "Northwind" folder in the app.  The "readzone" folder goes in the same folder as your regular properties files:
+We also have to define a readzone.  In the case of the Northwind I simply defined a readzone in the "readzone-dockdoor.properties" file in the "readzone" folder inside the "Northwind" folder in the app.  The "readzone" folder goes in the same folder as your regular properties files (so remember to put the entire "Northwind" folder in "RifidiHome/applications" if you are running from eclipse):
 <pre>
@@ Line 98: / Line 98: @@
 </pre>
-Lines with "#" are ignored.  We don't need to define specific antennas to listen to, nor do we need to filter tags based on their ID, so I've set the readerID to "Alien_1" (the reader we want to listen to for tags), and left the "antennas" property blank (which means "listen to all antennas").  The rest is unneeded for this example and commented out.
+Lines starting with "#" are ignored.  We don't need to define specific antennas to listen to, nor do we need to filter tags based on their ID, so I've set the readerID to "Alien_1" (the reader we want to listen to for tags), and left the "antennas" property blank (which means "listen to all antennas").  The rest is unneeded for this example and commented out.