Do I Need ez2update?

If you want to obtain data through our ez2update data feed, then you should install and configure ez2update before you install and configure ez2view.

You will need ez2update if

• You have licensed TNSP data from us
or
• You wish to obtain AEMO data from us

You do not need ez2update if

• You are only using AEMO data and you are going to read this from your InfoServer database
or
• You are installing a Trial license of ez2view

You can get all the software and documentation required to install ez2update from this page.

---

Downloads for ez2update

The following components make up the ez2update package.

• Licence Agreement
  Please review this agreement, which will apply to your trial or full licence of ez2update.


• Installation Instructions
  Please use these instructions for installing either of the ez2update packages below.


• Install Packages
  You will need one of these packages to install ez2update onto a server machine. If in doubt, you probably need the Full Executable.
  
  
  • Full Executable Installer
    This download contains all the prerequisites that you will need to install ez2update.
  
  
  • MSI Installer
    This download is smaller than the executable above, but it does not contain any prerequisites. To use this MSI you will require the .NET 4.0 Framework, and any other items identified by the MSI when you run it.
  
  
• Database Maintenance Scripts (the Reaper) Version 6
  You will need these scripts to maintain your database at a manageable size - without them your database will constantly grow until all sorts of problems arise...
  This file is zipped - you will need to extract the SQL script to run it.
  This script is for MSSQL databases - if you need an Oracle script please Contact Us.

---

Recent Releases

ez2update Version 4.1.220 - Released March, 2012

This is the current production version of ez2update.

ez2update now delivers the MTPASA_REGIONSOLUTION, MTPASA_REGIONAVAILABILITY and STPASA_REGIONSOLUTION data sets. These data sets are required to use the new PASA functionality in ez2view version 4.1.22X and above.

ez2update Version 4.1.203 - Released December, 2011

ez2update now delivers an additional range of data related to stations, units, participants, interconnectors, and regions. This version of ez2update can be used in conjunction with ez2view version 4.1.203 and above.

Note that the database upgrade for this version of ez2update is built into the software, and you do not need to run any database upgrade scripts to apply this release. See the Installation Instructions for details.

ez2update Version 4.1.160 - Released 15 August 2011

ez2update now delivers AEMO Constraint data. This change to ez2update allows customers who do not have their own InfoServer database to receive this data, and to display it using ez2view version 4.1.163 or above.

By default ez2update communicates with our data servers over the HTTP protocol, which means that all data is transmitted over the network in clear text. ez2update now supports SSL encryption of this communication channel. If you would like us to turn this on for your deployment of ez2update, all you have to do is contact us.

ez2update Version 4.0.114 - Released 4 May, 2011

ez2update now delivers the SCADA Unit Generation data that AEMO recently started publishing as described in AEMO Change Notice 791. This change to ez2update allows customers who do not have their own InfoServer database to receive this new data, and to display it using ez2view version 4.0.72 or above.

ez2update is now released in combination with SQL scripts that can be used to manage the size of your database. The reaper scripts are available above, and instructions for customizing and deploying the scripts can be found in the ez2update Australia Installation and Upgrade Manual.

We have made significant architectural changes that have improved the reliability and responsiveness of both the ez2update service, and the ez2update application that is used to monitor and control it. These changes have been tested to confirm that they address the specific issues listed below, however we believe that these changes will also address certain other undiagnosed intermittent issues that have arisen on customer sites from time to time.

EZTUA-58: ez2update periodically stops updating when running as a service
The reliability of the update service has been significantly improved, and it has undergone continuous hours of operation testing. If the host machine goes into power-saving mode, or hibernates, or is restarted, then the service resumes when the system returns to normal operations, and the updater updates the data to the current period.

EZTUA-61: The Service can get into a state where it is downloading files, but not processing them There has been a significant architectural revision to the Updater and this error is resolved as a result of these changes.

EZTUA-67: ez2update not always responsive to stop command
The service previously waited until all pending processing operations were complete before exiting. This has been modified so that the service will cancel these pending operations and will exit in a timely way in response to a stop command initiated by an end user.

EZTUA-19: Running multiple copies of the ez2update GUI at once causes the updater to stop updating.
This scenario has been re-tested and no problems were found when running multiple copies of the ez2update GUI in the specific case where ez2update is running as a service. Global-Roam recommends, however that you do not run more than one instance of the ez2update GUI at any one time as this can cause problems when running in Application mode.

EZTUA-80: Service does not automatically start after restart
The ez2update service would occasionally fail to start when the host machine was restarted on Windows XP. This problem was due to timeout issues when ez2update was trying to make use of system resources that were themselves restarting. This problem has been resolved and the ez2update service should now restart as expected when the host machine is restarted.

EZTUA-88: If the program cannot contact the global-roam hosted configuration service, and you already have configs, you cannot continue (but you should be able to).
ez2update will now restart normally in circumstances where it cannot contact global-roam servers to refresh its locally cached configuration files.

EZTUA-60: Items logged in the EventLog are always classified as Information, regardless of content.
Logging has been revised and log messages now contain correct data when being written to the Windows EventLog.

EZTUA-81: ez2update Australia's event log entries are missing event source information
Logging has been revised and log messages now contain correct data when being written to the Windows EventLog.

TOI-77: Upgrade ez2update to .NET 4
The application now runs against .NET 4.0.