Uh-oh, you may have already noticed – we released Axon Ivy 12 yesterday! 😊
And today, I’ve already migrated all my running Axon Ivy Engine instances to LTS 12. For those who know me, you’ll know that I exclusively manage Docker-based Axon Ivy instances. The upgrade went smoothly, but there’s one important detail to keep in mind when migrating to LTS 12.
For the first time, we’ve changed the installation paths for the Axon Ivy Engine within the Docker image. This adjustment was made to ensure more consistent and simplified installations in the future. Before Axon Ivy 12, the Axon Ivy Engine was installed in the following path: /usr/lib/axonivy-engine
. Additionally, Debian-style paths like /etc/axonivy-engine
were supported using symlinks.
Starting with Axon Ivy 12 LTS, the Axon Ivy Engine is now directly installed in the /ivy
folder. It’s short, straightforward, and minimizes the variety of possible paths when setting up a Docker instance.
To ensure a successful migration, follow these steps:
- Stop the current container.
- Adjust the volume mounts. Wherever you mount configurations, data, etc., into the container, you must now point to
/ivy
. For example: /etc/axonivy-engine/ivy.yaml
should now be updated to /ivy/configuration/ivy.yaml
or
/usr/lib/axonivy-engine/applications
should now point to /ivy/applications
.
- Update the version number to the latest 12.x version, e.g., 12.0.0.
- Start the container.
The Axon Ivy Engine will greet you in maintenance mode, which will guide you through the migration wizard. Follow the steps in the wizard and then restart your engine. In the Cockpit, you can either convert individual projects or entire applications to the latest version. Alternatively, you can deploy new versions of projects directly. Be sure to review the migration documentation for additional details about the whole migration process.
https://dev.axonivy.com/doc/12.0/axonivy/migration/major/index.html
If you encounter any pitfalls or inconsistencies, we’d love to hear from you here so we can continue improving our product.