ALE Server Configurator

Introduction

The objective of this tool is to provide a control client to execute Application Level Event specification (ALE) commands on a reader or component that implements the ALE specification.

AleServerConfigurator.jpg

This guide gives a short overview to the ALE Server Configurator that allows to interactively use the Filtering and Collection Server instance which is an AspireRFID plug-in and comprises:

  • A View, where you can interact with the F&C Server
  • A Preference window where you can choose the various preferences for the Configurator
  • And a Console, used to display the server's response.

Requirements

Hardware (minimum)

  • P IV 1.2GHz or equivalent
  • 512 MB Ram
  • 50 MB free HD space
Software

Users Guide

Download & Run

You can download the ALE Server Configurator tool from the AspireRFID forge named “AspireRfidIdeToolCollection” under "AspireRFID AITdev" package. Just decompress it and hit the “aspireRfidIDE” executable Also you can download from the same link the “ASPIRE_APPLICATION_FILES”. Decompress and place its content at your home directory "user.home\AspireRFID\IDE\..." (e.g. “C:\Documents and Settings\nkef\AspireRFID\IDE\”).

Configuration

The ALE Server Configurator is configured through the IDE’s preferences window (Window>Preferences) by choosing the ALE Server Configurator from the list appearing at the left see the picture below.

AleServerConfiguratorPreferences.jpg

From there you can configure the:

  • EC Specs Directory: The directory where ECSpecs will be stored which will be used to configure the server’s filtering function.
  • ALE Client EndPoint: The F&C Server’s EndPoint that accepts connections for the ALEService.
  • LR Specs Directory: The directory where the LRSpecs will be stored that will be used to dynamically define logical readers.
  • ALE LR Client EndPoint: The F&C Server’s LR EndPoint that accepts connections for the ALELRService to dynamically define logical readers.

ECSpec

The ECSpecs define how the Filtering and Collection Server generates reports. You can retrieve current tags, tags that have been added or deleted with respect to the last EventCycle or combinations of all. For that, you need to provide to the Filtering and Collection Server with a valid ECSpec in xml format by using the ALE Server Configurator. The ECSpec becomes active as soon as you subscribe with a notificationURI.

LRSpec

An LRSpec contains information about a reader. Whenever a new reader is to be created, a corresponding LRSpec has to be created and shipped to the Filtering and Collection Server.

Developers Guide

ALE Server configurator is an “AspireRfidIDE” product plug-in that is running within its environment. So for using this plug-in you should first download the “AspireRfidIDECore”.

Acquiring the code

The “Master Data Editor Plug-in” source code is available for checkout at the AspireRFID forge SVN. Check it out by:
  • hitting the create new repository location button at the SVN Repositories view of the Eclipse’s subversion plug-in and by using the following URL at the window that appears:
svn://svn.forge.objectweb.org/svnroot/aspire/trunk/AspireRfidIDE/AspireRfidIdePlug-ins/aspireRfidIde-AleSerConfig
  • right click the repository that has been just created and hit the check out button
  • check the aspireRfidIde-AleSerConfig project on the list and hit ok

Running the Project

For running AspireRfidIDE with the ALE ServerConfigurator Plug-in:

  • Create an aspireRfidIDE project (unless you have already created one)
  • Go to the aspireRfidIde project Run Configurations (Run>Run Configurations…) and at the list choose Eclipse Application>aspireRfidIde.product
  • At the Main tab of the “aspireRfidIde.product” set Run a product: aspireRfidIde.product
  • At the Plug-ins tab of the “aspireRfidIde.product” hit deselect all button and then choose the aspireRfidIde, org.ow2.aspirerfid.ide.aleconfig and then hit the Add required Plug-ins button.
  • Hit apply
  • Now you are ready to run the application.