Custom Esper Rules Jumpstart - Revision history

Matt at 04:43, 6 April 2012

2012-04-06T04:43:31Z

Matt at 21:51, 4 April 2012

2012-04-04T21:51:43Z

Matt at 21:49, 4 April 2012

2012-04-04T21:49:52Z

Matt at 21:20, 4 April 2012

2012-04-04T21:20:28Z

Matt: New page: =Custom Esper Rules= In addition to the

2012-04-04T21:03:51Z

New page: =Custom Esper Rules= In addition to the

New page

=Custom Esper Rules=

In addition to the

← Older revision		Revision as of 04:43, 6 April 2012
Line 3:		Line 3:
	In addition to the normal [[Rifidi Services Jumpstart\|Rifidi Services]] you can also create your own custom Esper rules. There is an example of this in the Northwind application as documented in the [[Developer's Guide]].		In addition to the normal [[Rifidi Services Jumpstart\|Rifidi Services]] you can also create your own custom Esper rules. There is an example of this in the Northwind application as documented in the [[Developer's Guide]].

−	Be sure that you understand the ReadZoneMonitorService as detailed in the [[Rifidi Services Jumpstart]], as this guide will use the ReadZoneMonitoringService to help create the custom commands that we will use.	+	Be sure that you understand the ReadZoneMonitorService as detailed in the [[Rifidi Services Jumpstart]], as this guide will use the ReadZoneMonitoringService to help create the custom commands that we will use. We will add to the code already given in the previous example.
		+
		+	1. First, we will create some event classes that we will send through esper. These classes will have the information we want the event to contain:
		+
		+	<pre>
		+	public class DockDoorArrivedEvent {
		+	private final TagReadEvent tag;
		+	public DockDoorArrivedEvent(TagReadEvent tag) {
		+	super();
		+	this.tag = tag;
		+	}
		+	public TagReadEvent getTag() {
		+	return tag;
		+	}
		+	}
		+	public class DockDoorDepartedEvent {
		+	private final TagReadEvent tag;
		+	public DockDoorDepartedEvent(TagReadEvent tag) {
		+	super();
		+	this.tag = tag;
		+	}
		+	public TagReadEvent getTag() {
		+	return tag;
		+	}
		+	}
		+	</pre>
		+
		+	2. Now, we need to add the event types in the _start() method
		+
		+	<pre>
		+	addEventType(DockDoorArrivedEvent.class);
		+	addEventType(DockDoorDepartedEvent.class);
		+	</pre>
		+
		+	3. Now we will do something useful with the esper. Tags should not stay on the dock door too long, so we will create an esper rule
		+
		+	<pre>
		+	StatementAwareUpdateListener dockDoorTagOnTooLongListener = new StatementAwareUpdateListener() {
		+	@Override
		+	public void update(EventBean[] arg0, EventBean[] arg1,
		+	EPStatement arg2, EPServiceProvider arg3) {
		+	if (arg0 != null) {
		+	TagReadEvent tag = (TagReadEvent) arg0[0]
		+	.get("dockarrived.tag");
		+	System.out.println("Tag seen for too long on the dock"
		+	+ " door: " + tag.getTag().getID());
		+	}
		+	}
		+	};
		+	addStatement("select dockarrived.tag from pattern "
		+	+ "[every dockarrived=DockDoorArrivedEvent-> "
		+	+ "timer:interval(" + this.dockdoor_dwelltime
		+	+ ") and not DockDoorDepartedEvent"
		+	+ "(tag.tag.ID=dockarrived.tag.tag.ID)]",
		+	dockDoorTagOnTooLongListener);
		+	</pre>
		+
		+	The "addStatement" method contains the esper itself. The "update" method of the listener will be called if an arrived event for a tag happens without a depart event for the same tag within the timelimit given by the "dwelltime" variable.
		+
		+	4. Now, we need to add the event into esper. We can change the methods in our subscriber class:
		+
		+	<pre>
		+	@Override
		+	public void tagArrived(TagReadEvent tag) {
		+	System.out.println("Tag arrived at location " + location + ": "
		+	+ tag.getTag().getFormattedID());
		+	if (this.isDockDoor) {
		+	this.app.sendNorthwindEvent(new DockDoorArrivedEvent(tag));
		+	}
		+	}
		+
		+	@Override
		+	public void tagDeparted(TagReadEvent tag) {
		+	System.out.println("Tag departed at location " + location + ": "
		+	+ tag.getTag().getFormattedID());
		+	if (this.isDockDoor) {
		+	this.app.sendNorthwindEvent(new DockDoorDepartedEvent(tag));
		+	}
		+	}
		+	</pre>

← Older revision		Revision as of 21:51, 4 April 2012
Line 3:		Line 3:
	In addition to the normal [[Rifidi Services Jumpstart\|Rifidi Services]] you can also create your own custom Esper rules. There is an example of this in the Northwind application as documented in the [[Developer's Guide]].		In addition to the normal [[Rifidi Services Jumpstart\|Rifidi Services]] you can also create your own custom Esper rules. There is an example of this in the Northwind application as documented in the [[Developer's Guide]].

−	Be sure that you understand the ReadZoneMonitorService as detailed in the [[Rifidi Services Jumpstart]], as this guide will use the ReadZoneMonitoringService to help create	+	Be sure that you understand the ReadZoneMonitorService as detailed in the [[Rifidi Services Jumpstart]], as this guide will use the ReadZoneMonitoringService to help create the custom commands that we will use.

← Older revision		Revision as of 21:49, 4 April 2012
Line 2:		Line 2:

	In addition to the normal [[Rifidi Services Jumpstart\|Rifidi Services]] you can also create your own custom Esper rules. There is an example of this in the Northwind application as documented in the [[Developer's Guide]].		In addition to the normal [[Rifidi Services Jumpstart\|Rifidi Services]] you can also create your own custom Esper rules. There is an example of this in the Northwind application as documented in the [[Developer's Guide]].
		+
		+	Be sure that you understand the ReadZoneMonitorService as detailed in the [[Rifidi Services Jumpstart]], as this guide will use the ReadZoneMonitoringService to help create

← Older revision		Revision as of 21:20, 4 April 2012
Line 1:		Line 1:
	=Custom Esper Rules=		=Custom Esper Rules=

−	In addition to the	+	In addition to the normal [[Rifidi Services Jumpstart\|Rifidi Services]] you can also create your own custom Esper rules. There is an example of this in the Northwind application as documented in the [[Developer's Guide]].