GridLink Current Release

AXIS GridLink Controller runs as a Windows service on a machine on the server farm. When a job is submitted to the farm, it receives the request, submits it to a queue and then launches the AXIS master and helpers of the specified version to run the job. In addition, it allows the user to monitor the status of the running job upon request (through the GridLink Utility).

AXIS GridLink Utility runs on the farm administrator's local machine and allows the administrator to remotely configure AXIS GridLink Controllers without logging on to the server. The utility is password-protected. The default password is "Admin" (case-sensitive). The administrator can change the password through the utility.

Please note that AXIS GridLink Controller and GridLink Utility can only run on Windows XP Professional, Vista, Windows 7, Server 2003, Server 2008 and HPC Server, and the AXIS GridLink Module requires the AXIS GridLink Module Licence.

Release Notes for Version 4.50 (August 17, 2010)

Enhancements

• GridLink - Generate Server Problem Report (Job #24748)

Now GridLink can detect potential problems on the servers and send a report to the farm administrator to review and fix.

The user can run GridLink Utility and select the menu "Tools - Get Servers’ Problem Report".

A problem may be an error (e.g. an AXIS library is not installed, displayed on RED background) or a warning (e.g. disk space is low, displayed on YELLOW background). The user can choose whether to view the complete report or the problems only.

The user can click on the "Summary" button to get a summary of the problems.

The user can also right-click on one server and select the menu "Tools - Get Server’s Problem Report" to get a report for this server only.

Bug Fixes

• GridLink - Assign New Profile Host Feature Might Not Work (Job #28712)

If the user wanted to choose a new Profile Host, after right-clicking on the server and selecting the menu "Make this server the Profile Host", in rare cases, it might fail without any error message. The Profile Host was not changed.

This bug was introduced in GridLink version 1.5 - 07 Apr 2006, and has now been fixed in 4.50.

Release Notes for Version 4.42 (July 9, 2010)

Bug Fixes

• GridLink - The Run Order of Batches Might Not Be Preserved When GridLink Local Cache Was Enabled (Job #28630)

When GridLink Local Cache was enabled, if the user submitted multiple batches and some of them were in the same datasets and some of them were in different datasets, the run order might not be preserved.

This bug was introduced in GridLink version 4.40 - 19 Apr 2010, and has now been fixed in GridLink version 4.42.