• Version: 1.7
• Version: 1.6.2
• Version: 1.6.1
• Version: 1.6
• Version: 1.5
• Version: 1.4
• Version: 1.3.2
• Version: 1.2
• Version: 1.1
• Version: 1.0.1
• Version: 1.0
• Version: 0.6

Support for Single Sign On (Professional Edition only)

• Authentication using Environment Variables

BugFixes for handling container permissions

Check that all required Containerfields are provided with a request

Improved Complex Container Requests (Professional Edition only)

• Support for nested Tables
• Improved Logic for Inlined Steps (Inline Step into another Inline Step is possible now)
• Changes to WSDL-Structure

BugFixes within the SQL Connector

BugFixes for Complex Container Requests

BugFixes User Interface

Cached Containers (Professional Edition only)

• It it now possible to cache the results on Container Runs for performance improvements.
• Added GUI to edit caching parameters
• Caching can be turned on very easily based on default settings

New Host Connector Customizer that runs on the browser and communicates to server via AJAX

• improved logic such that the 'switch direction' issue is avoided.
• completely new backed-end layout which will provide better performance
• abilit to contruct Tables that span multiple screens

Restrict users from logging in based on their IP's or the network-part of their IP (Professional Edition only)

added displaying how long a container request took on the Sample Run page

usability improvements to the page to assign Container permissions to a user

Container Run tracing capability for the XML Connector's Requests now implemented

bugfixes in Container Deployment

bugfixes in SQL Connector Request creation/ editing

Added GUI Controls to edit the paging on Containers on the main Containers List page

added GUI Controls to quickly shrink the list of containers down based on a search-filter

Connector names are now checked to be unique (for that type of Connector)

JDBC Interface

• By providing a JDBC Interface to other applications, SAGA.M31 - Galaxy - Virtual Data Federation Server acts like a normal SQL Server. ANSI SQL compliant statements can now be used to retrieve data independently from their real source. This enables application to retrieve data from SQL, Directory Server, 3270 Mainframe Transaktions and the new XML/Web Services usingJDBC as a common implementation.

XML/Web Service Backend Connector

• The new XML/Web Service Backend Connector enables SAGA.M31 - Galaxy - to retrieve data from such servicesinto the Virtual Data Federation structure. This opens a wide range of new data layers.

XML Transformation (Professional Edition only)

• The comercial Professional Edition now has the capability to transform incoming requests and outgoingresponses by using the XML Transformation Interface. This enables organizations to use their existing standards within theimplementation of SAGA.M31 - Galaxy -. Incoming requests can be mapped by selecting necessary information from the request and and feed them into the Galaxy structure. Outgoing responses can be transformed by using XSLT that are eitheralready defined or a new created structure that will be stored for further processing. This new feature provides a smooth integrationinto existing Web Service architectures.

Extended Container Enhancements

• By enhancing the Extended Container Feature, that was introduced in Release 1.4 Professional Edition, it is nowpossible to create a join Function inside a container. This allows a recursive retrieval of information if one request provides a table as response. The results will be merged into one column so that it is now a real "view" for the data layer.

Only a Professional Edition Release (comercial version)

strong>Deployment Tool

• Container developed on a test or development platform can be deployed intothe production environment.

Extended Containers

• Using Extended Containers it is now possible to chain requests inside a container.
• Output fields from one request can now be used as input field of another request inside acontainer.

Layout enhancements

Container Information

• A Container Information page has been added to the container layout. This page provides detailed informationon the underlying requests and connectors that this container uses.

Fixing a bug in SQL-Blob Field handling

Editing Connector Requests

• Editing Connector Requests that deleted Connector Fields which were already mapped to Container Fields caused this Container to fail. Such changes are not allowed to be made anymore.

SQL Connector Requests

• When creating Containers, Users can now also select the table's Columns as output Fields
  This makes the SQL Connector Requests and Ldap Connector Requests more consistent
• SQL Connector Fields that cannot be mapped to an SQL Column produced errors. This incorrect-mapping is now reported to the User and the SQL Field filled with the text "NULL (Check SQL Request)"

Installation

• Install Page modifications that allow user to select another Database where Galaxy stores its own data
• The Log file location can now be specified via the Installation Pages

Statistics for Container

• It is now possible to select the Containers for which Usage statistics should be logged

Bugfixes

• Fixes to the Containers Page that was taking a long time to load
• Fixes in the Container Run that caused HTTP 500 Server Errors
• Fixes in Editing SQL Connector Requests page which caused Exceptions

New SQL Request Creation GUI

• The SQL Request Creation GUI has been revamped to look similar to the LDAP Request creation thus paving the way for a uniform interface to create Connector Requests
• SQL Queries now configurable to flag an error when results of a READ type request are empty
• It is now possible to create a SQL Connector Request without a live connection to the database by adding fields to requests manually
• Fixes in the Table Viewer due to errors on IBM's BD2

New Container Creation Page

Improved Sample Run Page

• XML input/output highlighted
• Detailed Connector errors are now shown in Sample Run and also in XML
• Better layout of page
• Fixes to display multiples Output-Tables

Fix for User role selection

• Improvements in assigning Container Permissions

New Connector/Request overview

• Tree structure to allow easier navigation
• Connector Requests now show the Containers that use a Request

New page to test the XML/SOAP service

• Page lets users POST an XML-request (or SOAP request) against the local or any Galaxy Server

Container Statistics Overview

• New page to show Container Statistics of all containers

Galaxy's WUI has been completely revamped and reorganized. All the pages are now better organized and structured making navigation much easier.

SQL Connector Improvements

• The SQL Connector now allows INSERT, UPDATE and DELETE SQL Statements. SQL Requests can now do more than just read.
• An SQL Query that has input variables can be previewed before it is run

LDAP Connector Improvements

• New Interface for the creation/editing of LDAP Requests.
• Add, Modify and Delete objects is supported now. LDAP Requests can now also modify the data.
• support for multi-value attributes that allow for complex LDAP Structures to be retrieved

When creating SQL Connectors a list of the most popular databases is provided and the JDBC information for these databases can be looked up and the fields pre-populated with the right values.

Container Creation/Editing Improvements

• Input and Output fields of Requests for a Connector are now shown
• Input and Output fields of a Request can be mapped independency of each other
• Users can now also see if a Connector Request is used within a Container
• Changes to allow writing Connector Requests to be used in a Container
• Strict checking is now done on Container Field Names to ensure SOAP/WSDL for a container is Standards Compliant

The Error Page now has a link to an Error Log that can be sent to SAGA for further analysis. No longer is it necessary to dig thought the server looking for the logs.

The new design of the WUI has added a column to the right side of the page. On this column, admin-users can add custom help-text. This makes it easier to keep notes and helpful messages on a page. Also the messages shown on the Login and Logout pages can be edited via the same editor. The Editor is a WYSIWYG editor, so user's don't have to know any HTML.

Bug Fixes

• Bug on the SQL Query Creation page caused some query's results to not show up

The Web Services implementation is now WS-I Basic Profile 1.1 and Basic Profile 1.0 compliant. The only changes in WSDL is that Container Input/Output fields are now sorted by name in the WSDL.

All public WSDLs are now accessable via the following URL:
http(s)://your.galaxy.server/Galaxy/wsdl
As a sample you can use our sample Galaxy Server under http://galaxy.sagadc.com/Galaxy/wsdl

The SQL Connector now has the ability to browse all the tables' contents and their structures.

The install page is not shown by default for new Galaxy Installations. It is now accessible via the following URL:
http(s)://your.galaxy.server/Galaxy/install

• Bug during Application start up fixed
• Bug in Schema/WSDL generation fixed
• Bug in editing SQL/LDAP Requests fixed

Fixed minor bug in the WSDL URL for non-admin users when the WSDL is Public

SQL Creation script was not put into the WAR file

Now multiple Containers can be chosen and have their WSDLs generated in one WSDL file.

When creating Containers, the fields from Connectors are now grouped by requests. This means that all Requests must have names. In the SQL Connector, this was not implemented, so by default the SQL Requests are named '[rename]'. You can change this by editing the query.

Connection to the LDAP Servers now done via SSL if the LDAP URL starts with "ldaps://".

It's now possible to include Environment Variables in the following locations:

• Connector Properties
• SQL Queries
• LDAP Filters

This eliminates the galaxy.properties files that was needed in the previous versions. A WUI-Installer now starts up when you first startup the Galaxy WUI.

A license key is now required to run Galaxy, without a key, Galaxy runs in Developer Edition mode.
If a change from Developer Edition to Limited Edition is wanted, a Request must be made on galaxy.sagadc.com

Since a handle is now necessary for the WSDL generation, it is now required field when creating/editing containers. If a handle was previously not specified, it will be defaulted to '[rename]'. It is recommended that you rename all handles that are called '[rename]' for the WSDL generation to work correctly.

Galaxy now comes with documentation. This is a work in progress and will be updated regularly. For updates, visit: http://galaxy.sagadc.com/.

A bug in the WUI caused some concurrency problems. This is now fixed.

Apart from the XML Service, this release features a complete Web Services interface to allow clients to make Container execution via SOAP calls. Version 0.6 allows for creation of WSDL files that are specific to Containers.

Version 0.6 allows for WSDL files that are specific to each container to be generated. These WSDL files can be:

• Public: accessible via a URL to anyone
• Private: accessible only via the Galaxy Web User Interface (WUI) to administrator users

In order to improve interoperability between the Windows and other platforms, we created this new XML Response/Response structure. But what does this mean for a user? As an example, thanks to the Version 2 XML, you can now run a Container via Microsoft Office Product and have the data incorporated into any Microsoft Office Document. A demo of how to do this will be available soon.

Galaxy Version 0.6 also introduces an Eclipse Plugin for Eclipse versions 3.0.x. This makes integration of Container data in your Java projects a breeze. The Eclipse Plugin uses the XML Service, so a java clients needs only HTTP access to your Galaxy Server. Additional features of the Eclipse Plugin are:

• Access multiple Galaxy Servers
• Ability to see all the Containers that a user has access to
• Ability to see all the input and Output Fields of the Container
• Do a Sample Run and view the data
• Create Container-Run Requests which allow you to run Containers and get results via a simple Java API

Now useful messages about the status of a running Galaxy Server are available via the WUI. This makes it easy to see:

• When connectors where created/modified
• When Container Requests Failed and where they failed
• Galaxy startup and shutdown messages

Containers can now be taken "offline". This allows for temporary disablement of Containers to allow for maintenance windows. Deactivated Containers cannot be run via the XML Services or the Web Services interface.

Container Statistics now record the IP Address of the client making a Container Run. This allows for better tracking and analysis of usage statistics.

A new and improved layout for the XML Container Usage Statistics has been included in Version 0.6 of Galaxy.