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.
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 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.
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.
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.sudo -u ivy -g ivy cp -rf /etc/axonivy-engine-7x /etc/axonivy-engine-8
sudo -u ivy -g ivy cp -rf /var/lib/axonivy-engine-7x/applications /var/lib/axonivy-engine-8/applications
sudo systemctl stop axonivy-engine-7x && sudo systemctl disable axonivy-engine-7x
sudo systemctl stop axonivy-engine-8 && sudo systemctl start axonivy-engine-8
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.
IVY_ADMINISTRATOR_USERNAME=myAdmin
IVY_ADMINISTRATOR_PASSWORD=1234
IVY_ADMINISTRATOR_EMAIL=abc@domain.com
IVY_ADMINISTRATORS_myAdmin_PASSWORD=1234
IVY_ADMINISTRATORS_myAdmin_EMAIL=abc@domain.com
For a better development experience, we disabled JSF resource caching and enabled XML validation in the Designer.
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.
If you use a custom error page (JSF) you need to add /faces
prefix to the location in the web.xml.
<error-page> <error-code>404</error-code> <location>/custom-404-error-page.xhtml</location> </error-page>
<error-page> <error-code>404</error-code> <location>/faces/custom-404-error-page.xhtml</location> </error-page>
The resources in the webapps/ivy/shared
directory are deprecated and will be removed in later releases.
Re-synchronise your device with the engine after migrating.
After your device has been successfully synchronised with the engine you can start working on your tasks like always.