You can run a region-compatible version of the following executables, if available, instead of automatically downloading the most recent executable:
Eagle Data Services (EDS)
Integration & Workflow Studio (IWS)
EJM Monitoring Tool (MT)
Historically, IWS and related applications used the Microsoft Click-once deployment model. This model always downloaded and installed the most recent version of the application on the user’s desktop regardless of the application server version. This approach could cause feature compatibility issues in situations when the graphical user interface (GUI) was much newer than the underlying EagleML. It became practically impossible to test the GUI against any possible past version of the back end. The region compatibility approach is intended to solve this problem.
The system determines whether to launch the compatible version or to launch the most recent version based on the EagleML version in that target environment, or region where you are using it.
Deployment with EagleML
EagleML delivered a region-compatible version of Monitoring Tool (v1.0.10.39) to the application server in its November 2020 release, Monitoring Tool was selected as first step in the phased feature adoption approach. EDS was added to EagleML the same way in January 2021, and IWS was added in February 2021.
Region-compatible binaries reside in the tpe/dynamic/iws/modules folder.
All the deployed files are signed using standard Eagle build certificate to prevent any chance of malicious alteration.
Perform the Version Check
At login time, the system executes special common code. This functionality is available starting with IWS v1.0.10.47, MT v1.0.10.39 and EDS v2.0.10.44. This “launcher” code checks for the pre-installed version of the binary on the server. If it is available, the system uses it rather than downloading the latest version from the tools.eagleaccess.com.
In other words, after you log in to the application, the system knows the region where you are going. The downloaded application checks if the EagleML package in that target environment already has a compatible version of the Monitor Tool. If so, the system launches that compatible version from the region instead of launching the most recent version.
This allows you to tie the application user interface to the underlying EagleML. It ensures that the GUI is not newer that the EagleML back end/rules, and it launches the GUI provided with the EagleML package. All of this occurs behinds the scenes.
For older EagleML versions, the functionality remains as it was previously. If the system does not find the pre-installed binary, IWS downloads the latest one from tools.eagleaccess.com.
Note that as a result of the launcher functionality, the version number shown on login screen can differ from the version actually launched. The version number of the opened application can show a lower version that that shown in the login screen. This is normal behavior.
Local Cache Impact
Local cache allows the system to avoid multiple downloads of the same binary from different servers with the same version of EagleML. Once downloaded into your desktop, the system stores the particular version of IWS in local cache, and reuses it when necessary. The specific location is %LOCALAPPDATA%\eis\appcache.
0 Comments