Document Sample
Edge_Server_Use_Cases Powered By Docstoc
					Edge Server Use Cases


The following is a general rundown of how we would like to demo Rifidi Edge Server and the Dashboard
for the show. The use cases are geared towards what we will be showing of both the edge server and
more visually the Dashboard for our setup at the show.

Our setup will be quite similar to last year’s with a large screen TV and a large computer monitor. The
large screen tv will be showing off the dashboard and the computer monitor will have the edge server
and Rifidi Designer or Emulator running to show off more readers. We may also set up a switch to the tv
in order to switch between designer and emulator. We will also have a table with the Alien Reader set
up the power turned down to basically read for only a few inches and we will have lots of tags that we
will affix to boxes to swipe over the reader. The reader will be networked and connected to our edge

Our basic proposition in the demo is to go over some facts regarding the edge server and then to
demonstrate it. The two main aspects we will go over is our Reader Plugin layer (called SAL – Sensor
Abstraction Layer) and our ALE engine. We will also of course cover tech topics such as OSGI and Esper
but primarily these will be communicated through a marketing brochure we will hand out.

The demo will basically be a quick 5 minute speech followed by first showcasing the hardware layer of
Rifidi Edge and then moving on to an ALE demo.

Demo 1:

Demonstrate the Sensor Abstraction Layer (SAL) of Rifidi and be able to showcase the fact that Rifidi can
be fine grained and provide close reader control that can be used as an API and platform for further

    1) Start Dashboard – Connect to Rifidi (some talk about dashboard and as a console for Rifidi)

    2) Create a connection to the Alien Reader – name the reader something unique such as
       RFIDJournalLive2009Reader etc.

    3) Showcase the properties of the reader and the changing of properties etc.

    4) Showcase the blueprint and the placing of readers to provide symbolic representation of the

    5) Show the alerts infrastructure for System management by unplugging the reader and seeing it
       go red.
            a. Optional – turn off power of reader

            b. Optional – demonstrate our reconnect feature

    6) Place tag on reader’s field and showcase the tag reads with Tag View

            a. Optional - show velocity and directionality information

End of Dashboard and SAL demo

Demo 2:

Now we will showcase the ALE functionality of Rifidi. There will be some talk about how this is only a
limited demo and we can show more extensive features later in the evening.

    1) Open up ALE Perspective – describe that it is a perspective for developing and for quick
       monitoring of ALE processes

            a. Show the ALE process view

            b. Show the ALE Spec Builder View

            c. Show the ALE Spec Result View

    2) Create a new ALE process that basically triggers a report when certain tag prefixes are read.

            a. We will have several different boxes with different tags and we will ask the audience to
               pick the box that should be alerted and reported for.

            b. Show the time, tag id, and antennas etc when the correct tag is read

            c. Optional – create a report for all other tags that were not of the correct prefix.

    3) Show ALE Builder View which is basically a form that can either take in an ALE XML or has some
       fields to fill in that will construct the ALE XML.

    4) The left hand side view should have information about the ALE XML and its current state –
       deployed, undeployed, running etc.

    5) Optional – Have a groups tab in the view that lets you define named groups for sets of readers.

    6) The main view will be comprised of the ALE Builder View and another tab that opens up to show
       the results of the ALE spec that is being run.

            a. When a new spec is opened up it will close the other views related to the old spec and
               open up the new spec.
   7) In the bottom of the application where we usually have the properties view will be a subscriber
      view where we can show different subscribers or delivery methods for the ALE response.

           a. Right now we will only subscribe JMS as a subscriber

           b. Have another tab that can just read the message from the JMS queue

At the end of these two demo’s we will give some performance numbers and then pull back a small shelf
and show the MSI Wind or EEE pc box running the edge server. End with ridiculously small requirements

Optional Demo 3:

This is a demo we can show after the main demo during free time. It involves us showing the grouping
functionality and will use Rifidi emulator.

Optional Demo 4

Showcase the configuration and management aspects of the edge server by bringing it up and tweaking
the configuration both by hand and then by displaying it on the JMX console. Change of properties etc
could be worked in here as well as events on changes to certain states.

Shared By: