This document informs you in detail about incompatibilities that were introduced between
different Axon.ivy versions and tells you what needs to be done to get
your existing projects working with the newest Axon.ivy version.
Please note:
- Changing from an older Axon.ivy version to a newer one requires
you to perform the necessary migration steps one after another from
the oldest to the newest one.
- If deployed Axon.ivy projects are not compatible with a
new Engine version then you will have to convert them first on the
Axon.ivy Designer and then redeploy them to the upgraded Engine
installation afterwards.
Xpert.ivy becomes Axon.ivy
With version 5.1 the product is renamed from Xpert.ivy to Axon.ivy. Moreover, the Xpert.ivy Server is renamed to Axon.ivy Engine.
If previous versions of the product are referenced in this document then still the old names Xpert.ivy and Server are used.
When we speak about migrating the Designer, we mean in fact Axon.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 Axon.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 an Engine usually implies
a conversion of the system database. This can be resolved automatically by
invoking the system
database conversion in the Engine
Configuration Tool.
Project Conversion
If deployed Axon.ivy projects are no longer compatible with a new Engine
version then it is currently not possible to convert them on the Engine. 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.
Update Apache Tomcat Connector
If the Axon.ivy Engine is integrated with a reverse proxy (e.g. IIS or Apache),
it is best practice to check if the most recent Apache Tomcat Connector is installed.
For further information look at Update Apache Tomcat Connector.
Read the migration notes of
Read the migration notes of
Read the migration notes of