Revision as of 19:07, 8 November 2017

Changes in 3.7

LLRP

1. Check rospec response is not error before entering processing state
2. Handle add ro spec errors either through logging error and or resending rospec via checking error being returned learned in honeywell cwr project

Monitoring

1. Push notifications of server keep alive via MQTT. with ability to enable/disable and config standard mqtt parameters/topic..similar payload to ping I think and server IP/port as messages may go to centralized MQTT topic in cloud and needs to be a way to identify which Rifidi instance it came from - Payload "127.0.0.1</> LLRP_1</>Processing</>epochdate/time</></> - and each event type would have its own end point config/ip/port/qos/topic" - not sure if json format of xml makes more sense here

Rest

1. Reset session - delete session, create session, reexcute previous running commands, restart session(if already in processing state)
2. LLRP Encoding - validate session state in processing and provide necessary response
3. Start/Stop/Install/Uninstall Bundle - allow for install via url http://stackoverflow.com/questions/36017774/how-can-i-execute-osgi-command-in-code http://stackoverflow.com/questions/18825030/can-osgi-install-deploy-bundles-hosted-on-a-url
4. Restart Rifidi Edge server
5. OSGI SS operations or more generically expose OSGI command line operations - http://stackoverflow.com/questions/36017774/how-can-i-execute-osgi-command-in-code
6. Stop Rifidi server command

Adapters

1. Added REST interface to the Generic adapter Generic_User_Guide#Rest_Interface

Framework

1. Java 64 bit support
2. Migrate JVM Arguments where applicable such as things not required during server startup like llrp encoding (Dorg.rifidi.llrp.encode) leveraging Rifidi apps properties framework
3. Modify dbapp to use postgresql by defau

Links

Javadocs: http://www.transcends.co/www/javadoc/edge3.7.0/

Developer's_Guide

User's_Guide