This document informs you in detail about incompatibilities that were introduced between different Xpert.ivy versions and tells you what needs to be done to get your existing projects working with the newest Xpert.ivy version.
 |
Please
note:
|
When we speak about migrating the Designer, we mean in fact Xpert.ivy Projects in your workspace (or
inside an SVN repository). It might be that the default structure of a
project has changed, that the storage format of some artifacts has been altered
or that new configuration files have been introduced with a new Xpert.ivy
version.
Usually, all of those incompatibilities can be resolved automatically by
invoking the project
conversion in the Designer.
Sometimes, however, it is necessary that you perform some changes manually.
This document and it's sub documents will guide you through this process.
Migrating a Server usually implies a conversion of the system database. This can be resolved automatically by invoking the system database conversion in the Server Configuration Tool.
If deployed Xpert.ivy projects are no longer compatible with a new server version then it is currently not possible to convert them on the server. Therefore you need to load all projects deployed to active process model versions into the Designer, convert them individually and re-deploy them into to the same process model version.
Read the migration notes of
Read the migration notes of
Read the migration notes of
No migration is necessary when upgrading from 4.1.2 to 4.1.3.
Read the migration notes of
Read the migration notes of
Read the migration notes of