Version 3.1

From RifidiWiki

Jump to: navigation, search

Changes in 3.1

Edge Management of Reader/Sensor and Application API via REST

Exposed the Rifidi API via REST enabling users/applications/devices to more dynamically manage sensors/RFID readers and trigger sensor events Edge_Management and manage Rifidi app and readzone properties Rifidi_App_API

Edge Monitoring

Sensor/Reader Statistics, Memory, CPU, JVM, OSGI Monitoring via Restful Services Edge_Monitoring

Edge Messaging

The Edge Server is now bundled with the lightweight messaging broker MQTT widely used within IoT. Applications can now publish and subscribe to Rifidi Messaging Events leveraging this lightweight standards based messaging protocol Edge_Messaging

LLRP Updates

  • REST LLRP Configuration (one shot) Command - ability to inject dynamic llrp.xml/configuration via restful service
  • REST LLRP Tag Encoding/Writing Command Edge_Management#LLRP_Encode_command_example
  • Performance Enhancements/Fixes,
  • LLRP - include custom LLRP Tag report information in generic way
  • Use reader time (instead of Rifidi Edge system time)

New Sensor/Reader Adapter

Convergence Systems Limited CS203 Edge_Server_Sensor_Plugins

New Example Applications

The Rifidi Services Jumpstart App, MQTT App and Restful Services App has been added to the developers guide to provide a simpler example and recommended production implementation design pattern Developer's_Guide Development_Jumpstarts

Sensor Rules Engine

Ability to Override Esper default configuration

Failover (Primary/Secondary) Nodes

Fail-over_Configuration_(Primary/Secondary) Nodes

  • Starting in 3.1 Failover Configuration (Primary/Secondary) feature is available.

This enables a Rifidi Edge server to be defined as a secondary node based on configuration described below. The secondary server will start and load the basic libraries. In the even a failure is detected based on thresholds configured the server will continue loading starting the necessary Rifidi Apps and connecting to the required sensors/readers to continue processing events.

OSGI - P2 Infrastructure and how to use

Platform Upgrades

  • Esper 5.x- Complex Event Processing Engine
  • Moquette 0.4 - MQTT Messaging Broker
  • Restlet 2.2.1 - REST Services Implementation
  • Jolokia 1.2.2 - REST/JMX Bridge used for Monitoring, -
  • AWS 1.9 - Amazon Web Services client
  • Eclipse Paho .4 - MQTT Client

Bug Fixes

  1. Fix Problem with Manifest file in rxtx-osgi-2.2-pre2.jar impacting some windows 7 and windows 8 setups []
  2. handle connecting and processing to avoid auto save rifidi.xml config into a dead state (connecting)
  3. Performance Tuning - Ability to disable Rifidi startup apps tag monitoring and tag diagnostic (under heavy loads these could have impact on performance - see Performance_Tuning_Tips
  4. add display name for Thinkify and Generic adapter in workbench
  5. getCommandInstance make public (from protected) for Dynamic reader using submitandblock method []

Documentation Updates

  1. developer's guide - Rifidi Management API Jumstart, MQTT Jumpstart, Rifidi Services Jumpstart Development_Jumpstarts
  2. developer's guide - Edge_Management, Edge_Monitoring and Edge_Messaging(MQTT)
  3. developer's guide - Best_Practice_for_Designing_a_Rifidi_APP
  4. user's guide - Edge_Management, Edge_Monitoring and Edge_Messaging(MQTT)
  5. user's guide - CSL Adapter Edge_Server_Sensor_Plugins
  6. user's guide - Dynamic (one shot) LLRP Configuration via Restful Services Edge_Management#LLRP_Dynamically_Configuration_command_example
  7. developer's guide - LLRP Tag Encoding/Writing via Rest Edge_Management#LLRP_Encode_command_example
  8. user's guide - Fail-over_Configuration_(Primary/Secondary)





Personal tools