Migration Notes for Axon.ivy Engine 5.1 (Lauberhorn)

This document informs you in detail how to migrate the data and projects of an existing Xpert.ivy Server 5.0 installation to a new Axon.ivy Engine 5.1 installation.

Table of Content:

New Engine licence required

The Axon.ivy Engine 5.1 requires a new licence. Please contact your sales agent to upgrade your licence.

Consult the article "Installing a Licence" in the Installation chapter of the Engine Guide to learn how to install the new licence.

Updated to JSF 2.2 & Primefaces 5.0

JSF and PrimeFaces libraries have been updated to the newest versions. You have to test your Html Dialog application with the new version before upgrading your productive environments, because there are some incompatible changes. See the Designer Migration Notes for more information.

Default keystore renamed

The default keystore file configuration/keystore has been renamed to configuration/keystore.jks. If you imported custom keys into the old keystore then you either have to re-import those keys into the new keystore or overwrite the new keystore file with the old one.

See Engine Guide > Administration > System Properties > SSL Client for more information.

Security system renamed

The name of the built-in security system has been changed from "Xpert.ivy" to "ivy Security System". The new name appears during the Application creation Dialog on the Administration UI.

There exists API that takes a security system name as parameter or returns it as result. See ISecurityContextDataProvider#getExternalSecuritySystemName() or SecurityManager#findExternalSecuritySystemProvider(String)

Valid default security system names can be accessed through the ISecurityConstants Public API. If you have been using the from now on deprecated ISecurityConstants.IVY_SECURITY_SYSTEM_PROVIDER_NAME, please migrate it to the new valid ISecurityConstants.IVY_ENGINE_SECURITY_SYSTEM_PROVIDER_NAME as future releases might remove the deprecated constant.

Windows executables renamed

The windows executables have been renamed to reflect the name change from Xpert.ivy Server to Axon.ivy Engine. If you use the *.ilc files to configure the Engine and its Java runtime, then make sure that you rename your files after copying them to the new installation. The *.ilc file must have the same file name (without extension) like the executable it is intended for.

See Engine Guide > Miscellaneous > Tool Reference > Windows Program Launcher Configuration for more information.