EdgeServerCore

From RifidiWiki

Jump to: navigation, search

Overview

The Rifid Edge Server Core is comprised of several modules that provide base functionality for developers to extend to meet the needs of their own applications and to access the data in an extensible way. The following links will provide more detail about a few important components in the edge server core.

Configuration Framework
The Configuration Framework handles persisting certain services, exposing them via JMX, and making them available in the OSGi registry
Reader Framework
The Reader Framework uses the Configuration Framework to expose readers as services to the rest of the edge server
Command Framework
The Command Framework uses the Configuration Framework to expose commands as services to the rest of the edge server
RMI Interface
The interface for programmatically interacting with the Edge Server

Architecture Overview

ReaderFactory
OSGi Service that produces Readers. Produces only one type of reader (i.e. Alien9800 reader).
Reader
A configured Reader Client. One-to-one relationship with a physical reader. Produces sessions. OSGi Service
Session
An active connection to a physical reader. Executor for Commands.
CommandConfigurationFactory
OSGi Service that produces CommandConfigurations. Can produce more than one type of CommandConfiguration (i.e. GetTagListCommand, GPIOEnabledCommand).
CommandConfiguration
A configured Command Factory. Produces configured commands of a certain type. OSGi Service.
Command
A runnable that is executed on a session. Must finish quickly.

OSGi

Services

<Services that are available for use, for example, DAOs>

Bundle Dependencies

< Graph displaying which bundles depend on each other > <TODO: Jochen>

ALE & ESPER

<TODO: Jochen>

Example Code

Personal tools