Version 1.2 - Revision history

Matt: Reverted edits by Amesycyxa (Talk); changed back to last version by Kyle

2010-11-26T19:44:02Z

Reverted edits by Amesycyxa (Talk); changed back to last version by Kyle

Amesycyxa at 22:20, 17 November 2010

2010-11-17T22:20:33Z

Amesycyxa at 22:20, 17 November 2010

2010-11-17T22:20:19Z

Kyle: /* Documentation */

2010-09-07T20:48:47Z

‎Documentation

Kyle: /* Commands */

2010-09-07T20:47:12Z

‎Commands

Kyle: New page: =What's new in version 1.2= ==Functionality== * First class support for Rifidi Applications. In 1.1 applications were no more than OSGi bundles which hooked into Esper. In 1.2, can make u...

2010-09-07T20:44:27Z

New page: =What's new in version 1.2= ==Functionality== * First class support for Rifidi Applications. In 1.1 applications were no more than OSGi bundles which hooked into Esper. In 1.2, can make u...

New page

=What's new in version 1.2=

==Functionality==
* First class support for Rifidi Applications. In 1.1 applications were no more than OSGi bundles which hooked into Esper. In 1.2, can make use of the new Application API which provides many services which make it easier to make powerful RFID applications. For more information see the Developer’s guide included in the SDK release.
* ActiveMQ configuration is now more flexible. The configuration is provided via an xml file and the previously used system properties have been removed.
* Improved LLRP flexibility. LLRP configuration can now be done via XML files rather than commands.
* Serial barcode reader support
* Generic reader adapter for allowing connection to readers which specific reader adapters are not provided for.
* Diagnostic commands for determining if the Edge Server is connected to readers and processing tags.

===Example of Rifidi Applications===
One of the great improvements with 1.2 is the 'Rifidi Application'. Rifidi Applications make it much easier to create RFID applications that run on top of the Rifidi Edge Server. The following is a simple example that prints a line when a tag arrives and when it departs. There are more examples inside the SDK release, including a completely re-worked Northwind example!
<pre>
package test;

import java.util.concurrent.TimeUnit;

import org.rifidi.edge.core.app.api.AbstractRifidiApp;
import org.rifidi.edge.core.app.api.service.tagmonitor.ReadZone;
import org.rifidi.edge.core.app.api.service.tagmonitor.ReadZoneMonitoringService;
import org.rifidi.edge.core.app.api.service.tagmonitor.ReadZoneSubscriber;
import org.rifidi.edge.core.services.notification.data.TagReadEvent;

/**
* A simple app to monitor a read zone
* @author Kyle Neumeier
*
*/
public class MyApp extends AbstractRifidiApp implements ReadZoneSubscriber{

/**A service to monitor a read zone*/
private ReadZoneMonitoringService readzoneService;

public MyApp(String group, String name) {
super(group, name);
}

@Override
protected void _start() {
ReadZone zone = getReadZones().get("dockdoor");
readzoneService.subscribe(this, zone, 10f, TimeUnit.SECONDS);
}

@Override
protected void _stop() {
readzoneService.unsubscribe(this);
}

@Override
public void initialize() {
}

@Override
public void tagArrived(TagReadEvent tag) {
System.out.println("TAG ARRIVED!: " + tag);
}

@Override
public void tagDeparted(TagReadEvent tag) {
System.out.println("TAG DEPARTED!: " + tag);
}

/**
* @param readzoneService the readzoneService to set
*/
public void setReadzoneService(ReadZoneMonitoringService readzoneService) {
this.readzoneService = readzoneService;
}

}
</pre>

==Properties==
We've added a couple new properties that can be added to the system properties when you run the edge server
* org.rifidi.ui.notify. If set to true, tags will be delivered to Workbench over a JMS topic. If set to false, the tags will not be put onto JMS. Not sending tags improves performance. It is set to true by default.
* org.rifidi.home This set set to the home directory (where the 'applications' folder and the 'config' directory reside). It is useful to change this when you are developing applications in eclipse to the SDK directory so that your configuration files can be stored within eclipse. It is set to 'user.dir' by default.

==Commands==

==Documentation==

@@ Line 1: / Line 1: @@
->=What's new in version 1.2=
+=What's new in version 1.2=
->==Functionality==
+==Functionality==
 * First class support for Rifidi Applications. In 1.1 applications were no more than OSGi bundles which hooked into Esper. In 1.2, can make use of the new Application API which provides many services which make it easier to make powerful RFID applications. For more information see the Developer’s guide included in the SDK release.
 * ActiveMQ configuration is now more flexible. The configuration is provided via an xml file and the previously used system properties have been removed.
@@ Line 11: / Line 11: @@
 ===Example of Rifidi Applications===
 One of the great improvements with 1.2 is the 'Rifidi Application'. Rifidi Applications make it much easier to create RFID applications that run on top of the Rifidi Edge Server. The following is a simple example that prints a line when a tag arrives and when it departs. There are more examples inside the SDK release, including a completely re-worked Northwind example!
-&amp;lt;pre&amp;gt;
+<pre>
 package test;
@@ Line 38: / Line 38: @@
 	@Override
 	protected void _start() {
-		ReadZone zone = getReadZones().get(&amp;quot;dockdoor&amp;quot;);
+		ReadZone zone = getReadZones().get("dockdoor");
 		readzoneService.subscribe(this, zone, 10f, TimeUnit.SECONDS);
+	}
@@ Line 54: / Line 54: @@
 	@Override
 	public void tagArrived(TagReadEvent tag) {
-		System.out.println(&amp;quot;TAG ARRIVED!: &amp;quot; + tag);
+		System.out.println("TAG ARRIVED!: " + tag);
+	}
 	@Override
 	public void tagDeparted(TagReadEvent tag) {
-		System.out.println(&amp;quot;TAG DEPARTED!: &amp;quot; + tag);
+		System.out.println("TAG DEPARTED!: " + tag);
+	}
@@ Line 70: / Line 70: @@
+}
-&amp;lt;/pre&amp;gt;
+</pre>
-−
-----
-<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
-----
-=[http://ytamoru.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=
-----
-=[http://ytamoru.co.cc CLICK HERE]=
-----
-</div>
 ==Properties==
@@ Line 88: / Line 79: @@
 ==Commands==
 We have added several new OSGi commands to help diagnose common problems with your applications. For example:
-* &lt;tt&gt;tagrate&lt;/tt&gt; prints out how many tags per second the edge server is currently reading
+* <tt>tagrate</tt> prints out how many tags per second the edge server is currently reading
-* &lt;tt&gt;currenttags [readerID]&lt;/tt&gt; prints out a list of tags that can be currently seen by the given reader
+* <tt>currenttags [readerID]</tt> prints out a list of tags that can be currently seen by the given reader
 For a full list of commands, see the [[User's Guide]]
@@ Line 97: / Line 88: @@
 In addition, we provide a [[Developer's Guide]] that explains how to write Rifidi Applications using our new API.

@@ Line 1: / Line 1: @@
 >=What's new in version 1.2=
-==Functionality==
+>==Functionality==
 * First class support for Rifidi Applications. In 1.1 applications were no more than OSGi bundles which hooked into Esper. In 1.2, can make use of the new Application API which provides many services which make it easier to make powerful RFID applications. For more information see the Developer’s guide included in the SDK release.
 * ActiveMQ configuration is now more flexible. The configuration is provided via an xml file and the previously used system properties have been removed.
@@ Line 11: / Line 11: @@
 ===Example of Rifidi Applications===
 One of the great improvements with 1.2 is the 'Rifidi Application'. Rifidi Applications make it much easier to create RFID applications that run on top of the Rifidi Edge Server. The following is a simple example that prints a line when a tag arrives and when it departs. There are more examples inside the SDK release, including a completely re-worked Northwind example!
-&lt;pre&gt;
+&amp;lt;pre&amp;gt;
 package test;
@@ Line 38: / Line 38: @@
 	@Override
 	protected void _start() {
-		ReadZone zone = getReadZones().get(&quot;dockdoor&quot;);
+		ReadZone zone = getReadZones().get(&amp;quot;dockdoor&amp;quot;);
 		readzoneService.subscribe(this, zone, 10f, TimeUnit.SECONDS);
+	}
@@ Line 54: / Line 54: @@
 	@Override
 	public void tagArrived(TagReadEvent tag) {
-		System.out.println(&quot;TAG ARRIVED!: &quot; + tag);
+		System.out.println(&amp;quot;TAG ARRIVED!: &amp;quot; + tag);
+	}
 	@Override
 	public void tagDeparted(TagReadEvent tag) {
-		System.out.println(&quot;TAG DEPARTED!: &quot; + tag);
+		System.out.println(&amp;quot;TAG DEPARTED!: &amp;quot; + tag);
+	}
@@ Line 70: / Line 70: @@
+}
-&lt;/pre&gt;
+&amp;lt;/pre&amp;gt;
 ==Properties==

@@ Line 1: / Line 1: @@
-=What's new in version 1.2=
+>=What's new in version 1.2=
 ==Functionality==
@@ Line 11: / Line 11: @@
 ===Example of Rifidi Applications===
 One of the great improvements with 1.2 is the 'Rifidi Application'. Rifidi Applications make it much easier to create RFID applications that run on top of the Rifidi Edge Server. The following is a simple example that prints a line when a tag arrives and when it departs. There are more examples inside the SDK release, including a completely re-worked Northwind example!
-<pre>
+&lt;pre&gt;
 package test;
@@ Line 38: / Line 38: @@
 	@Override
 	protected void _start() {
-		ReadZone zone = getReadZones().get("dockdoor");
+		ReadZone zone = getReadZones().get(&quot;dockdoor&quot;);
 		readzoneService.subscribe(this, zone, 10f, TimeUnit.SECONDS);
+	}
@@ Line 54: / Line 54: @@
 	@Override
 	public void tagArrived(TagReadEvent tag) {
-		System.out.println("TAG ARRIVED!: " + tag);
+		System.out.println(&quot;TAG ARRIVED!: &quot; + tag);
+	}
 	@Override
 	public void tagDeparted(TagReadEvent tag) {
-		System.out.println("TAG DEPARTED!: " + tag);
+		System.out.println(&quot;TAG DEPARTED!: &quot; + tag);
+	}
@@ Line 70: / Line 70: @@
+}
-</pre>
+&lt;/pre&gt;
 ==Properties==
@@ Line 79: / Line 79: @@
 ==Commands==
 We have added several new OSGi commands to help diagnose common problems with your applications. For example:
-* <tt>tagrate</tt> prints out how many tags per second the edge server is currently reading
+* &lt;tt&gt;tagrate&lt;/tt&gt; prints out how many tags per second the edge server is currently reading
-* <tt>currenttags [readerID]</tt> prints out a list of tags that can be currently seen by the given reader
+* &lt;tt&gt;currenttags [readerID]&lt;/tt&gt; prints out a list of tags that can be currently seen by the given reader
 For a full list of commands, see the [[User's Guide]]
@@ Line 88: / Line 88: @@
 In addition, we provide a [[Developer's Guide]] that explains how to write Rifidi Applications using our new API.

← Older revision		Revision as of 20:48, 7 September 2010
Line 85:		Line 85:

	==Documentation==		==Documentation==
		+	We now provide a [[User's Guide]] that describes many aspects of running, configuring, and administrating the Rifidi Edge Server.
		+
		+	In addition, we provide a [[Developer's Guide]] that explains how to write Rifidi Applications using our new API.

← Older revision		Revision as of 20:47, 7 September 2010
Line 78:		Line 78:

	==Commands==		==Commands==
		+	We have added several new OSGi commands to help diagnose common problems with your applications. For example:
		+	* <tt>tagrate</tt> prints out how many tags per second the edge server is currently reading
		+	* <tt>currenttags [readerID]</tt> prints out a list of tags that can be currently seen by the given reader
		+
		+	For a full list of commands, see the [[User's Guide]]

	==Documentation==		==Documentation==