New in Version 2.9:

• Remote monitoring by FAME of EnergyServer processes and of market data capture
• Significant performance increases in data export processes
• Administration and system diagnostics enabled without disrupting active database users
• Improvements to file structures, log formats and programming environment

Remote Maintenance
With the 2.9 release, FAME has taken steps to further automate the administration of the EnergyServer database and to outsource essential daily monitoring functions to FAME. Log files are sent from EnergyServer to FAME's secure site, where they are monitored for potential issues ranging from late arrival of market data to failed user logins. New functionality includes system monitoring to ensure that the database processes running correctly and the hardware is in a healthy state. These changes are part of a continuing program of support automation which is reducing the requirement for administrative manpower at the customer site and improving the speed and accuracy with which FAME responds to any issues.

Non-Intrusive Administration
In Version 2.9, a number of administrative and diagnostic tasks which used to require the EnergyServer database to be offline can now be accomplished without any disruption to EnergyServer users. Changes to the databases and server can now be made while users continue to enjoy full access to EnergyServer. Enhancements to core EnergyServer components allow administrators to toggle on and off component tracing and detailed logging without downing the server. These changes mean that database changes, system diagnostics and testing can now be carried out during peak usage hours, improving FAME's ability to provide rapid response to customer requests and issues.

Performance Enhancements
In Version 2.9, the sorting algorithms used by the Generic Extract Process to feed data from EnergyServer to other software systems have been redesigned. The resulting performance increase is dramatic with some reports that previously took hours to run now completed in minutes.

File Structure Redesign
A significant technical change to EnergyServer in Version 2.9 has been in the redesign of the file structure. As EnergyServer takes on more and more sources of data, using a wider range of fast and flexible data loaders, the system as a whole has needed to expand to accommodate the enhancements. Limits to the current file structure design have been overcome by implementing a new structure, which those familiar with UNIX file structures will find familiar and easy to use. Binaries, configuration files, scripts and logs are now maintained within standardized directories allowing for easy navigation, upgrade and installation.

Programming Environment Changes
Every component within EnergyServer 2.9 is now referenced with an environment variable. Developers working with EnergyServer 2.9 can now write flexible scripts capable of being ported to any EnergyServer. The new environment variables also allow multiple EnergyServer databases to run on the same hardware.

New Open Logging Format
In Version 2.9, the daily logs use a new, compact format which is parsable and has each logged action contained within a single line. FAME also now provides and open programming interface to all log files. Custom software can now write directly to any of the EnergyServer logs, allowing centralized monitoring of EnergyServer processes by the customer and by FAME.

For more information about FAME EnergyServer, contact Phil Corryn in the Americas or Ian Gordon in Europe, the Middle East, Africa and Asia.