Difference between revisions of "Edge Gateway Builds"

From Datonis
Jump to: navigation, search
(Updated build minor version from 633 to 636)
Line 15: Line 15:
|[https://s3.amazonaws.com/kura-builds/rel_5.3/636/linux-edge-5.3.636.zip https://s3.amazonaws.com/kura-builds/rel_5.3/639/linux-edge-5.3.639.zip]
|docker run --name datonis-edge-5.3.636 --mount type=volume,source=edge-vol,target=/opt/datonis-edge-data --publish 8080:8080 --publish 8443:8443 --detach altizon/linux-edge:5.3.636
|docker run --name datonis-edge-5.3.639 --mount type=volume,source=edge-vol,target=/opt/datonis-edge-data --publish 8080:8080 --publish 8443:8443 --detach altizon/linux-edge:5.3.639
|[[Datonis Edge 5.3 Release Notes]]
|[[Datonis Edge 5.3 Release Notes]]

Revision as of 11:16, 14 May 2018

Edge Gateway Home > Builds
Release Build No Windows Artifact Linux Artifact Dev Env Artifact Docker Command Customer 


Release Notes
5.3 636 https://s3.amazonaws.com/kura-builds/rel_5.3/639/win-edge-5.3.639.zip https://s3.amazonaws.com/kura-builds/rel_5.3/639/linux-edge-5.3.639.zip https://s3.amazonaws.com/kura-builds/rel_5.3/639/dev-env-5.3.639.zip docker run --name datonis-edge-5.3.639 --mount type=volume,source=edge-vol,target=/opt/datonis-edge-data --publish 8080:8080 --publish 8443:8443 --detach altizon/linux-edge:5.3.639 Yes Datonis Edge 5.3 Release Notes
5.2 593 https://s3.amazonaws.com/kura-builds/rel_5.2/593/win-edge-5.2.593.zip https://s3.amazonaws.com/kura-builds/rel_5.2/593/linux-edge-5.2.593.zip https://s3.amazonaws.com/kura-builds/rel_5.2/593/dev-env-5.2.593.zip docker run --name datonis-edge-5.2.593 --mount type=volume,source=edge-vol,target=/opt/datonis-edge-data --publish 8080:8080 --publish 8443:8443 --detach altizon/linux-edge:5.2.593 Limited Datonis Edge 5.2 Release Notes
5.1 562 https://s3.amazonaws.com/kura-builds/rel_5.1/562/win-edge-5.1.562.zip https://s3.amazonaws.com/kura-builds/rel_5.1/562/linux-edge-5.1.562.zip https://s3.amazonaws.com/kura-builds/rel_5.1/562/dev-env-5.1.562.zip No Datonis Edge 5.1 Release Notes
5.0 518 https://s3.amazonaws.com/kura-builds/rel_5.0/518/win-edge-5.0.518.zip https://s3.amazonaws.com/kura-builds/rel_5.0/518/linux-edge-5.0.518.zip No Datonis Edge 5.0 Release Notes
4.6 474 https://s3.amazonaws.com/kura-builds/rel_4.6/474/win-edge-4.6.474.zip https://s3.amazonaws.com/kura-builds/rel_4.6/474/linux-edge-4.6.474.zip No Auto upgrade support from 4.5 builds, this helps easily migrate existing configurations to newer builds without breaking backward compatibility), Edge Gateway registration support, backup and restore of configuration changes from Datonis platform, New Activity anchor that replaces existing Rules anchor on Console (it shows registered things, metric mappings, last event, last alert, ML models (beta)), New XML adapter with directory monitoring support, Improved CSV adapter with directory monitoring support, Powerful JavaScript based expression evaluation support as part of Adapter derived tags (Older JEXL is still supported), Custom event date time mapping (datetime_tag_id) to any of the existing tags, New orange status showing authentication failure, build version at lower bottom, Adapter config monitor tag id and scan tag id related fixes, MQTT topic store changes, New rule state changes, Making OPC tree browsing optional, Bug fixes, notified_at_edge flag, Issues related to large size databases. OPC DA adapter data conversion issue fix, Edge service start issue on low memory systems
4.5 311 https://s3.amazonaws.com/kura-builds/rel_4.5/311/win-edge-4.5.311.zip https://s3.amazonaws.com/kura-builds/rel_4.5/311/linux-edge-4.5.311.zip No Instruction execution as Gateway Notification Action support, Modbus endian flag bug fix, Service and Adapter property description in the UI, Sync Now support in EdgeRuleService, Auto tag name generation logic imrpovement, Derived tag expression syntax change (much simpler syntax), Tag aggregation support, OPC UA node iswritable support, Generate instruction-json button support, Improved advanced configuration validation logic, Logout feature, Template rendering support in Gateway Notification Actions, Changed minimum start-up memory requirement to 64 MB
4.5 234 https://s3.amazonaws.com/kura-builds/rel_4.5/234/win-edge-4.5.234.zip https://s3.amazonaws.com/kura-builds/rel_4.5/234/linux-edge-4.5.234.zip No Configuration of adapters via CSV (basic configuration via CSV) and advanced configuration via JSON, Rule execution at gateway with Rule UI, notifications are generated at cloud (except HTTP url notification which can be triggered locally), CSV simulator adapter to mock thing metric data, Adapter instruction config support i.e. write OPC UA tag values and Modbus registers via Datonis instruction, Re-branding to Datonis Edge, OPC UA secure communication fix, OPC DA enhancements, Improved logging
4.0 160 https://s3.amazonaws.com/kura-builds/rel_1.0/160/win-aliot-4.0.160.zip https://s3.amazonaws.com/kura-builds/rel_1.0/160/linux-aliot-4.0.160.zip No Data service and transport service fixes
4.0 118 https://s3.amazonaws.com/kura-builds/rel_1.0/118/win-aliot-4.0.118.zip https://s3.amazonaws.com/kura-builds/rel_1.0/118/linux-aliot-4.0.118.zip No Multi threaded scanning support, Less verbose Info level logs, Valid default configJson, Http client thread spawn issue fix, Device profile console error fix
4.0 95 https://s3.amazonaws.com/kura-builds/rel_1.0/95/win-aliot-4.0.95.zip https://s3.amazonaws.com/kura-builds/rel_1.0/95/linux-aliot-4.0.95.zip No Test configJson and Repeat Test feature, Modbus register address fix, Linux emulator USB support, configJson scan_tag_ids feature to allow specific tags to be sent during scan, Jexl script support
4.0 81 https://s3.amazonaws.com/kura-builds/rel_1.0/81/win-aliot-4.0.81.zip https://s3.amazonaws.com/kura-builds/rel_1.0/81/linux-aliot-4.0.81.zip No OPC UA, OPC DA and Modbus adapter fixes, experimental Test configJson feature.
4.0 53 https://s3.amazonaws.com/kura-builds/rel_1.0/53/win-aliot-4.0.zip https://s3.amazonaws.com/kura-builds/rel_1.0/53/linux-aliot-4.0.zip No As this is the first build of new Gateway, this needs to tested thoroughly before production deployment.