Dynamic Reader Configuration Jumpstart

Create a RifidiApp

• 1. Create a RifidiApp. First, be sure to set up a developer environment using these steps.

Then check the developer guide for 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 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.

Sample Rifidi Dynamic Reader Configuration - Run-time Updates to Reader Configurations based on Business and Infrastructure Events with SDK

• 5. Here is where one can find the sources for the sample Rifidi Dynamic Reader Configuration

Rifidi Dynamic Reader Configuration using Rifidi SDK Note: The example app updates and existing readers LLRP RoSpec configuration in runtime. This could be extended to update other reader property/configurations dynamically.