Migration 7.4 to 8.0

Licence

You need a new licence file for Axon.ivy Engine 8.0. Your old 7.x licence will no longer work. The new licence is no longer bound to the hostname where an Axon.ivy Engine runs but on the public URLs end users communicate with it.

Learn more about public URLs and how to install the new licence in the Engine Guide.

Furthermore, we have removed the Demo Licence file demo.lic from the [engineDir]/configuration directory. The Axon.ivy Engine 8.0 is running in demo mode by default without a valid licence file.

Portal

Portal versions 7 and earlier are no longer compatible with Axon.ivy 8.0. If you have used the Portal in your projects, you must migrate your projects to Portal version 8.0.

Portal Migration Notes

Debian Packge

The LTS debian package axonivy-engine-8 does not come with migration supports for its predecessor (the axonivy-engine-7x). These packages are designed to run independent engines on the same host at a time.

However, with a few simple manual copy tasks you can migrate leading edge engines to the LTS equivalent.

Our proposed migration strategy for leading edge debian package users:

Install the latest axonivy-engine-8 package on the host running the 7x version. The new engine will not contain any configurations or data from the 7x train yet.
Copy configuration files: sudo -u ivy -g ivy cp -rf /etc/axonivy-engine-7x /etc/axonivy-engine-8
Copy application files: sudo -u ivy -g ivy cp -rf /var/lib/axonivy-engine-7x/applications /var/lib/axonivy-engine-8/applications
Turn of the old engine: sudo systemctl stop axonivy-engine-7x && sudo systemctl disable axonivy-engine-7x
Reboot the new engine: sudo systemctl stop axonivy-engine-8 && sudo systemctl start axonivy-engine-8
Verify that Axon.ivy Engine 8 serves your workflow app as expected

Administrator Configuration

There were a hidden feature for container customers to define an administrator in a single definition way, mainly used with environment variables. This is no longer supported.

BEFORE:

IVY_ADMINISTRATOR_USERNAME=myAdmin
IVY_ADMINISTRATOR_PASSWORD=1234
IVY_ADMINISTRATOR_EMAIL=abc@domain.com

AFTER:

IVY_ADMINISTRATORS_myAdmin_PASSWORD=1234
IVY_ADMINISTRATORS_myAdmin_EMAIL=abc@domain.com

HTML Dialog Caching

For a better development experience, we disabled JSF resource caching and enabled XML validation in the Designer.

Enabling XML validation for .xhtml files can potentially cause validation errors during dialog execution, e.g. you can get a javax.faces.view.facelets.TagException when calling your Html Dialog. If you run into XML validation errors, first try to fix them. If this is not possible (e.g. because the problem is caused by a required component you don't have permission to change) you can disable XML validation (and enable resource caching) by setting the context parameter javax.faces.PROJECT_STAGE to Production in the Designer's webapps/ivy/WEB-INF/web.xml file.

Location prefix for custom error pages

If you use a custom error page (JSF) you need to add /faces prefix to the location in the web.xml.

BEFORE:

<error-page>
  <error-code>404</error-code>
  <location>/custom-404-error-page.xhtml</location>
</error-page>

AFTER:

<error-page>
  <error-code>404</error-code>
  <location>/faces/custom-404-error-page.xhtml</location>
</error-page>

Deprecated for removal: 'webapps/ivy/shared'

The resources in the webapps/ivy/shared directory are deprecated and will be removed in later releases.

They have been used in JSP layouts of older Axon.ivy projects (< 8.0). Copy all used CSS, JS-scripts and images from an old installation into your Axon.ivy projects.

Axon.ivy iOS App

Re-synchronise your device with the engine after migrating.

Tasks that are not synchronised and are being worked on may throw ViewExpiredExceptions when synchronising with the engine. This only happens the first time and won't have any side effects except that you must re-submit your data for said tasks.

After your device has been successfully synchronised with the engine you can start working on your tasks like always.