Common Migration Steps
After running Operating System specific migration steps:
Restart the Axon Ivy Engine.
Very likely you will need a new license after a major version change.
Request a new license as described in the Licensing your Engine chapter.
Copy the new license to the
configuration
directory or upload it using the Engine Cockpit
Migrate the Database to the latest version: System Database Conversion
Either convert the system database with the Engine Cockpit
or set the
autoConvert
property in the ivy.yaml totrue
and it will be done with the next Axon Ivy Engine restart.
Test your workflow app for braking changes and identify them using the Migration Notes document.
Examine the logs for errors while an automated test or a business user clicks through important workflows.
Project-Migration
If you face incompatibilities in the UI or see errors in the logs while using the new Axon Ivy Engine, here’s how you make your projects compatible with the new Axon Ivy Engine version.
Download the latest Axon Ivy Designer which is available for the release you are migrating to.
Import the version that is deployed on your Axon Ivy Engine from your source repository into your Axon Ivy Designer workspace.
Migrate the project according to the description in section Converting Projects of the Axon Ivy Designer Guide. Usually, this is achieved by invoking the project conversion action on each project. Some manual adaptations may be necessary.
Test the migrated project in the Axon Ivy Designer.
All migrated projects must be re-deployed to the new, upgraded Axon Ivy Engine version.
Not only the
RELEASE
process model version (PMVs) must be updated and re-deployed, but allDEPRECATED
projects too.Other versions in the states
PREPARED
orARCHIVED
may be easier to delete, rather than updating and redeploying.