Consortium
Activities
Projects
Forge
Events
Log-in
Register
Provided By AIT Branch
Space Menu
Consortium
|
Solutions
|
Middleware
|
Forge
|
MyObjectWeb
|
PDF
|
History
|
More Actions
View
Code
|
XML
|
Help
Documentation
|
XWiki Syntax
|
1 Provided By AIT Branch ---- #toc("" "" "true") ---- * *Reader Core Proxy* ** Exists within OSGi ** Provides JMX management interface ** Provides EPC Reader Management (not currently enabled and used) ** ALE communicates with it via EPC Reader Protocol ** Provides Interfaces with readers: *** For Intermec(BRI) *** For Impinj (Mach1) *** For FossTrack’s Simulator reader *** HAL Wrapper for new readers * *ALE Server* ** EPC F&C1.1 standard compliant. *** Check if AspireRFID fully supports Tag Memory Specification API (Section 7 of ALE 1.1 specifications) **** ALETM – Main API class (Section 7.1 of ALE1.1 specifications) and implement it if it doesn’t. ** Runs on Apache tomcat 6.0 ** Uses CXF and spring to implement JaxWS for the control interface. ** It Supports Maven. ** Supports RP and LLRP for the communication with the readers. ** Supports TCP/HTTP protocol to deliver EC reports ** Provides Standard EPC Control Interface Based on SOAP messages * *EPCIS* ** EPC 1.0.1 standard compliant *** Provides Extension Mechanisms **** ~~New Event Field~~ A new field may be added to an existing Event Type in the Data Definition Layer. Additionally to every event the following data are supported from the repository (check Section 6.3 and 9.1 of the EPCIS specifications): {table} Column Name | Type Name event_id | BIGINT fieldname | VARCHAR prefix | VARCHAR intValue | INT floatValue | FLOAT dateValue | TIMESTAMP strValue | VARCHAR {table} ** Runs on Apache tomcat 6.0 ** Uses CXF and spring to implement JaxWS for the query and capture interface. ** Uses SQL for the query interface and Hibernate for the capture interface. ** Supports MySQL 5.0 ** Provides standard EPC Query and capture Interface Based on SOAP messages. ** Provides proprietary master data capture interface. * *BEG* (under development) * *Tooling (Eclipse)* ASPIRE IDE has been designed as an Eclipse RCP (Rich Client Platform) application that will run over Equinox OSGI server. It uses the command API to define menus, pop-up menu items and toolbars so as to support easily plug-ins and provide more control. Every tool will be an eclipse plug-in/bundle that will be able to be installed or removed as needed. ** AspireRfidIDE Core ** ALE Server Configurator Plug-in ** Business Event Generator Plug-in ** Physical Reader Configuration & Management Plug-in ** EC-Spec Editor Plug-in ** LR-Spec Editor Plug-in ** Master Data Editor Plug-in Business Process Management and Workflow Management Editor Plug-in (under design) Connector Configurator Plug-in (Under design) ASPIRE Programmability Engine Plug-in (Under design) * *Connector* ** Connector engine component ** Connector client component