Difference between revisions of "Version 3.1"
From RifidiWiki
(→OSGI - Basic P2 Infrastructure and how to use) |
(→Bug Fixes) |
||
Line 37: | Line 37: | ||
# handle connecting and processing to avoid auto save rifidi.xml config into a dead state (connecting) | # handle connecting and processing to avoid auto save rifidi.xml config into a dead state (connecting) | ||
# Ability to disable specific startup apps such as monitoring and diagnostic | # Ability to disable specific startup apps such as monitoring and diagnostic | ||
− | # add display name for | + | # add display name for Thinkify and Generic adapter in workbench |
# submitAndBlock make public for Dynamic reader [ http://forums.rifidi.net/viewtopic.php?f=35&t=4239] | # submitAndBlock make public for Dynamic reader [ http://forums.rifidi.net/viewtopic.php?f=35&t=4239] | ||
Revision as of 11:38, 21 September 2014
Contents
Changes in 3.1
Sensor and Application Management
Exposed the Rifidi API via Restful Services enabling users/applications/devices to trigger dynamic events to applications and sensors managed by the Rifidi Edge Server Edge_Management
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 Edge_Messaging
LLRP Updates
- Restful LLRP Config Command - ability to inject dynamic llrp.xml/configuration via restful service
- 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
OSGI - P2 Infrastructure and how to use
Platform Upgrades
Esper 5.x- Event Engine, Moquette 0.4 - MQTT Messaging Broker, Restlet 2.2.1 - Restful Services, Jolokia 1.2.2 - Restful/JMX Bridge used for Monitoring, - AWS 1.8.4. upgrades to latest
Bug Fixes
- Fix Problem with Manifest file in rxtx-osgi-2.2-pre2.jar [1]
- handle connecting and processing to avoid auto save rifidi.xml config into a dead state (connecting)
- Ability to disable specific startup apps such as monitoring and diagnostic
- add display name for Thinkify and Generic adapter in workbench
- submitAndBlock make public for Dynamic reader [ http://forums.rifidi.net/viewtopic.php?f=35&t=4239]