Migration Notes for Xpert.ivy Server 4.2 (Rigi) ... 4.3 (Pilatus)
This document informs you in detail how to migrate the data and projects of an existing Xpert.ivy Server 4.2 installation to a new 4.3 installation.

Server migration
Convert your existing server system database.

If your project uses the IvyAddOns project, please see the section below. Otherwise no migration of the already deployed 4.2-projects is necessary when upgrading to a 4.3 server installation.
Default Environment

Due to a cleanup in environment management the default environment of an application is called Default from now on.
Previous versions of Xpert.ivy server have created a different name for the default environment automatically. For example with a given application name Foo the name of the default application was set to Foo_Default.
You may either leave your environments as before or clean up them and get rid of your obsolete Foo_Default environment. You can perform this work with the Engine AdminUI of Xpert.ivy 5.1 using its improved Environment export/import feature.
IvyAddOns migration
The IvyAddOns project, which was delivered with Xpert.ivy 4.2, is not compatible with Xpert.ivy 4.3.

In every application that uses the IvyAddOns project, a 4.3 compatible IvyAddOns version must be re-deployed into the same process model version where the older version was deployed.

The latest and compatible version of the IvyAddOns project can be found in the 4.3 server's project/ directory.

Migration of 3.9 server installations
Even though the Xpert.ivy Designer supports the import of 3.9 projects since version 4.3, such projects still need considerable manual processing before they can be run on a 4.3 server.

It is not possible to upgrade a running 3.9 server installation to a 4.3 installation directly.

Please consult the Xpert.ivy 4.3 Designer Guide (> Projects > Converting old 3.x projects) to learn more about how to convert 3.9 projects so that they can be run on a Xpert.ivy Server 4.3.
Client migration
Update to Java 6

The Rich Dialog client does not support Java 5 any more. All clients using Rich Dialogs must upgrade to Java 6, if they not already using Java 6 (which is normally the case, if the JRE is configured to use automatic updates).

Users with an old JRE will be redirected to the Java 6 update when they start a Rich Dialog. If your users do not have permissions to install Java on their machines, ensure that Java 6 is installed.