persistent-3.6.3

Version 3.6.2

• Fix bug where history sync CRON pattern was not being saved on publisher
• Add support to see the location and view the contents of the data source and publisher log files
• Add support to get the publisher status via REST and UI to use it
• Add support to start a sync via REST and UI to use it

Version 3.6.1

• Add publisher support to UI

Version 3.6.0

• Upgraded to work with core version 3.6.x
• Expose settable as configurable property on received points
• More reliably attribute publishing on failed attempts to publish point attributes
• Added support to the new UI data sources page
• Bump protocol version to allow for versioned models for publisher and data source to be exchanged upon connection

Version 3.5.6

• Fix NPE from pre-3.5.x publishers

Version 3.5.5

• Fix concurrency issue for reliability publishing where all are marked unreliable but updating

Version 3.5.4

• Change translation about accepting data point settings updates on a Persistent data source point, this previously referred to the settings as attributes.

Version 3.5.3

• Fix bug where the publisher could not be configured to allow settable data points on the receiving data source

Version 3.5.2

• Default publisher to sending attributes
• Publishers configured to send attributes will do so during point connection in addition to when they change and during snapshot sends
• Data source will flag a point unreliable while the point is not connected
• Data source will flag a point reliable upon connection if the publisher cannot, either it is not configured to send attributes or it is a legacy publisher that cannot
• Use ‘Max point values to send in packet’ value to also limit the number of point attribute groups that can be sent in one Point Attribute packet
• Fix errors around closed connections

Version 3.5.1

• Publish point attributes if configured after connection established

Version 3.5.0

• Upgraded to work with core version 3.5.x
• Fix publisher points table message column to displayed sync’ed from time, even on disabled publishers
• Fix data point’s data type id on edit page to enable manually creating points
• Flag all points as unreliable if there are no connections to the data source, reliable if a connection exists
• Making Persistent Data Source points ‘settable’ so the value set is sent to the publishing side and not saved on the data source side
• Optionally allow publishing reliability attribute of points
• Include simplify settings in data point transmission

Version 3.4.6

• Fix bug in casing of table name for case sensitive database types

Version 3.4.5

• Fix bug in encryption to ensure encrypted messages are properly padded
• Add persistentSyncs table for tracking sync times, mitigate runaway H2 database growth

Version 3.4.4

• Make a copy of the data point’s unmodifiable tags map for mixing tags in

Version 3.4.3

• Empty override permissions on publishers means transmit null such that data source will not overwrite user configured permissions

Version 3.4.2

• Adding option to encrypt data using AES 128, 192 or 256 bit key lengths (256 bit supported in Java 8u161+)
• Fix XID length validation to 100 characters.
• Version compatibility where permissions are not repeatedly nulled because the sender isn’t up to date enough to send them

Version 3.4.1

• Bugfix in tags transmission / mixing in

Version 3.4.0

• Upgraded to work with core version 3.4.x
• Transmit points, rollups, chart settings, and permissions to received points
• Add tags to all points being sent from a publisher, or all points received by a receiver
• Add port into connection description
• Optionally override data point permission fields at the publisher or the data source
• Tags added to receiver points persist if not conflicting trasmitted tags

Version 3.3.1

• Improved performance of multi-threaded history sync

Version 3.3.0

• Upgraded to work with core version 3.3.x

Version 3.2.2

• Fix for long disable time during point init exchanges

Version 3.2.1

• Fixing bug with correcting sender times of -1 in rtdata when startTimes is null

Version 3.2.0

• Upgraded to work with core version 3.2.x
• Fixed bug with sync time tracking on points that were first sync’ed without data.

Version 3.1.1

• Ensure cleaner shutdown when Mango stops

Version 3.1.0

• Upgraded to work with core version 3.1.x

Version 3.0.0

• Upgraded to work with core version 3.0.x
• Added validation to system settings.

Version 1.7.2

• Fix for NPE when not using NoSQL

Version 1.7.1

• Check for deleted points when starting publisher and do not attempt to publish them

Version 1.7.0

• Upgraded to work with core version 2.8.x
• Adding metrics points to allow monitoring receivers
• Publisher alarm levels now configurable
• Adding rolling logs
• Adding throttle threshold to Data Source to limit incoming data
• Adding XID column to data point table views

Version 1.6.5

• Update to allow publishing more than 65535 points
• Adding sync overlap setting to allow syncing large blocks of data at the cost of duplicating data (only to be used with Time Series data stores)

Version 1.6.4

• Fixing setupUI bug in 1.6.3

Version 1.6.3

• UI Improvements for large sets of data points

Version 1.6.2

• i18n translation spelling fixes

Version 1.6.1

• Upgraded to work with core version 2.7.x

Version 1.6.0

• Upgraded to work with core version 2.6.x

Version 1.5.9

• Added sync range count request timeout setting for publisher
• Added logic to publisher to allow reconnecting syncs even if the connection is terminated
• Added a column for the date/time that all data points are synced to on the edit page
• Improved sync from time tracking accuracy within the sync handler
• Added Device Name column to points list

Version 1.5.8

• Bugfix to ensure that the new sync from time gets set and the publisher does not have to be re-started.

Version 1.5.7

• Bugfix where not every point was getting the sync from time set on the page.

Version 1.5.6

• Added ability to set the sync from time on the edit page.
• Added socket timeout setting
• Added test connection period setting
• Added sync response timeout setting

Version 1.5.5

• Compression for all packet types
• Compression is only used for payloads that are reduced in size
• Save realtime data option on data source
• Sync tasks configurable up to 65,535

Version 1.5.4

• Further improved reliability
• Added optional CRC32 checksum

Version 1.5.3

• Improved reliability in connection
• Improved historical sync performance
• Added setting to increase historical sync threads (use with caution as Mango defaults to 100 threads max)

Version 1.5.2

• Fixed bug where Historical Queue use was blocking the database writes and causing system wide slow down
• Added some Warn level logging to process log to indicate if the Max point values to send are too low
• Added help to explain max point values to send per packet

Version 1.5.1

• Fixed bug with compression where CPU usage could spike to 100% during decompression

Version 1.5.0

• Fixed packet count statistics for Publisher and DataSource so they line up
• Alarm on publisher queue exceeding limits will no longer happen when set to not transmit Realtime data
• Added ability to set logging levels for Publisher and Data Source

Version 1.4.9

• Upgraded to core 2.5.0
• Changed Real Time data to be sent across only for viewing, the only way to persist data is to use Historical Synchronization
• Added Unit tests for Historical Synchronization and Real Time data transfer

Version 1.4.8
*Fixed JSON publisher import

Version 1.4.7

• Fixed up compression for Real time data transmission, found bug where failures were occurring and data was being lost
• Changed core to count and collect the same number of points values, previously this was off by 1 (would only be an issue in transmitting to/from NoSQL systems)

Version 1.4.6

• Upgraded to work with core version 2.4.x

Version notes for 1.4.5

• Fixed bug where Timed output stream was never being closed
• Added ability to choose to send real time updates
• Added ability to choose to send point hierarchy updates
• Added option to choose how close to NOW to sync the history
• Improved Historical Sync to be more robust during outages
• Added a Reset sync History button to allow a re-check and publish of data point histories
• Added adjustable packet size to improve speed and bandwidth use

Version notes for 1.4.4

• Upgraded to work with core version 2.3.x

Version notes for 1.4.3

• Allowing point add filter to remain open to add multiple points

Version notes for 1.4.2

• Core 2.2
• Made cron pattern for sync fully custom
• Changed the name to Mango Persistent TCP

Version notes for 1.4.1

• Improved point sync processing
• Additional process logging statements
• Updated to work with core 2.1

Version notes for 1.4.0

• Ported changes from Mango M2M
• Updated to work with core 2.0

Version notes for 1.3.0

• Added packet send rate information
• Updated to work with core 1.3

Version notes for 1.1.0

• Added packet send rate information
• Added status panels to data source and publisher
• Performance improvements
• License enforcement
• Allow manual start of historical data sync
• Added documentation