Ektron Product Release Notes - WebHelp - Ektron

Diagnostics
l Major improvements to log file reader
l Fixes to load balancer visualizer
l Improved EWS logging performance
l Most SQL run by eSync and load balancer actions are logged at log level 4
l More information about DB sync is logged
l Credentials are stripped from connection strings
l Log files have changed
o Name changes
o Information formatting
o EWS log creates new file on every restart
eSync Strategies
l Notification about eSync events with event information
o Can be used for cache invalidation
o Provides information about the basic eSync request
o Contains only top level rows, not their children.
l Ability to plug-in to the data being synched and modify it
o Can be used for scrubbing eSync data
o Can be used to get detailed information about every row being synched across
l All events are synchronous
o some are cancellable
l Some events are raised on a remote server (peer)
l Notification events for DB and file sync progress
l Load balancer events
Strategy Design Features
l Uses same Framework used by existing Ektron strategies
l Familiar to the developer, with minimal divergence from existing strategies
o No new dlls to reference
l Events are raised within the scope of the EWS. So, configuration files are also in the
EWS root folder.
l Unhandled strategy errors do not bring down eSync. They are logged.
l Strategy execution and errors shown in Web user interface
l Developers cannot modify eSync parameters by mistake and affect eSync.
l Not all eSync parameters can be modified (configuration, state, parameters)
l Properties are neatly categorized in new eSync API, which is different from underlying
code and, so, protected against future changes in internal architecture
l Extensive, built-in code documentation available in Visual Studio, so available during
development.
l Sample Strategies are available.
Diagnostics
Ektron Product Release Notes—All Releases 37