Edge Server Architecture

From RifidiWiki

Revision as of 19:42, 23 September 2009 by Kyle (Talk | contribs)

Jump to: navigation, search

This page describes several aspects of the Rifidi Edge Server Core. It is intended for developers to understand how the core is structured.

Overview

There are two main aspects to understanding the edge server. The first is the three architectural layers that facilitate the flow of data from sensor to a designated endpoint. The second is the runtime and how it uses service oriented architecture and OSGi to be dynamic and light weight.

Layers

The purpose of the edge server is to connect to any kind of sensors (e.g. RFID readers, Barcode readers, Mobile Devices) and collect ID information from them. In many scenarios, this consists of connecting to a Gen2 fixed reader (such as Alien 9800, Motorolla LLRP, etc), and collecting EPC information. However, the edge server is designed in a way so that the edge server to collect many kinds of data (active, passive, etc) from many kinds of devices. After the data is collected, it

Sensor Abstraction Layer

Complex Event Processing Layer

Notification Layer

OSGi

OSGi is a dynamic modules system for Java. It provides several pieces of functionality including the following:

  1. A deployment unit (called a bundle), which is a normal JAR with some extra information in the Manifest.
  2. A lightweight runtime that allows bundle lifecycle to be controlled. In other words, you can start, stop, and update bundles at runtime.
  3. Dependencies are explicitly stated in the Manifest either as "bundle dependencies" or "package dependencies".
  4. Classes are only visible to other bundles if their containing packages have been exposed. This allows developers to hide classes that should be strictly internal.
  5. The runtime provides a service registry -- a system-wide repository for bundles to provide functionality.

The edge server is simply a collection of bundles that run in an OSGi environment (Equinox). Functionality between bundles is shared by means of services that are available in the service registry. Because bundles can be started and stopped while the rest of the server is still running, we can update non-essential parts of the edge server without restarting it.

Services

Core Services

Reader DAO

Command DAO

Configuration Service

Sensor Management Service

JMX Service

JMS Services

Internal Destination

External Tags Destination

External Notification Destination

Internal Broker Connection Factory

External Broker Connection Factory

External JMS Template

Other Services

Esper Management Service

Notification Service

Logging Service

Bundles

org.rifidi.edge.api

org.rifidi.edge.console

org.rifidi.edge.core

org.rifidi.edge.core.rmi.server

org.rifidi.edge.core.services

org.rifidi.edge.core.jms

org.rifidi.edge.core.services.logging

org.rifidi.edge.core.services.notifications

Important Dependencies

Spring

Spring DM

SLF4J

Esper

ActiveMQ

Personal tools