Federator 2.1

Compatibility

Java	Federator 2.1 must be run under Java 1.5 or newer.
Databases	MySQL 5, Microsoft SQL Server 2005, Oracle 10g, and Sybase 12.5
DataSynapse Grids	GridServer: 4.2 update 10 and up; all versions of GridServer 5.x FabricServer: 2.6 and 3.0
Amazon EC2	EC2 DevPay functionality requires GridServer 5.0 SP3 with EC2 patch or GridServer 5.1 SP1. DevPay is not supported on FabricServer at this time.
Demand Based Policies	Demand Based Policies require GridServer 5.x.

See the Federator User Guide for installation instructions.
NOTE: Federator 2.1 must be deployed on FabricServer 3.0 or above.

Prepare the Federator database. To do this:

Shutdown Federator if it's currently running.
Connect to the Federator database with your SQL client of choice.
Update the runtime_variable db table such that the value column does not allow null values. See your database documentation for more information.

Upgrade the Federator archive in your current deployment. To do this:

Extract the file federator.war from the 2.1 version of the federator gridlib with your archive tool of choice.
Shutdown your current Federator deployment if it's running.
Edit the Federator application component and navigate to "Add/remove archive files."
Select federator.war and click Remove.
Click add and browse to the federator.war file which was unpacked from the 2.1 gridlib, click OK, the click Menu.
Navigate to "Add/override/customize Container and component-specific config files."
Remove the current startup scripts (startup.sh and startup.bat).
Add the startup files from the new Federator gridlib (ds_config/bin/startup.sh.unix, ds_config/bin/startup.bat.win).
Be sure to drop the platform extension (e.g., the file should be called startup.sh not startup.sh.unix).
Ensure that the Relative Path is set to bin, the appropriate OS is selected, and that Resolve Variables is checked.
Click OK to upload the script and click Finish to save your changes.
Deploy the updated application component.
Install the latest enablement on your managers as per the Federator User Guide.
Start Federator.

Upgrading from versions of Federator prior to 2.0 is not supported.

Federator now supports Demand Based Policies for GridServer 5.0 and GridServer 5.1. See the Federator User Guide for details.
A new View-Only role was added for users.
The Shared Resource page has been split into two pages: Static Resources and Active Resources. See the Federator User Guide for details.

As this is a major release, the web services API has changed. Users should generate new stubs and adjust their code as necessary.
SSL errors may be encountered while contacting Amazon EC2 or managers that have SSL certificates from
certain issuers. Install the ssl.keystore file shipped with Federator 2.0 on all engines that will host
Federator to correct this.
The Squid grid library for Windows must be deployed even when running
under non-Windows platforms.
Users accessing Federator's SOAP interface via .NET may need to manually toggle the fieldSpecified flag for
primitive object members, e.g., Ec2ResourceManagerInfo.instanceLimit.

Ec2ResourceManagerInfo info = new Ec2ResourceManagerInfo(); info.name = "foo"; info.instanceLimit = 10; info.instanceLimitSpecified = true; ...