Difference between revisions of "Version 3.1"
From RifidiWiki
(→Failover (Primary/Secondary) Nodes) |
(→Failover (Primary/Secondary) Nodes) |
||
Line 29: | Line 29: | ||
===Failover (Primary/Secondary) Nodes=== | ===Failover (Primary/Secondary) Nodes=== | ||
[[Fail-over_Configuration_(Primary/Secondary)]] Nodes | [[Fail-over_Configuration_(Primary/Secondary)]] Nodes | ||
− | Starting in 3.1 Failover Configuration (Primary/Secondary) feature is available. | + | *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. | 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. | ||
Revision as of 13:26, 4 October 2014
Contents
- 1 Changes in 3.1
- 1.1 Sensor and Application Management
- 1.2 Edge Monitoring
- 1.3 Edge Messaging
- 1.4 LLRP Updates
- 1.5 New Sensor/Reader Adapter
- 1.6 New Example Applications
- 1.7 Sensor Rules Engine
- 1.8 Failover (Primary/Secondary) Nodes
- 1.9 OSGI - P2 Infrastructure and how to use
- 1.10 Platform Upgrades
- 1.11 Bug Fixes
- 1.12 Documentation Updates
- 1.13 Links
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
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- 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 impacting some windows 7 and windows 8 setups [ http://forums.rifidi.net/viewtopic.php?f=35&t=4248]
- handle connecting and processing to avoid auto save rifidi.xml config into a dead state (connecting)
- 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
- add display name for Thinkify and Generic adapter in workbench
- getCommandInstance make public (from protected) for Dynamic reader using submitandblock method [ http://forums.rifidi.net/viewtopic.php?f=35&t=4239]
Documentation Updates
- developer's guide - Rifidi Management API Jumstart, MQTT Jumpstart, Rifidi Services Jumstart Development_Jumpstarts
- developer's guide - Edge Management, Edge Monitoring and Edge Messaging (MQTT)
- user's guide - Edge_Management, Edge_Monitoring and Edge_Messaging(MQTT)
- user's guide - CSL Adapter -
- user's guide - Dynamic LLRP Configuartion via Restful Services-
- user's guide - LLRP Tag Encoding/Writing Rest