Migrating from 10.0 to 11.1

Upgrade to 11.1 is only supported from an Axon Ivy Engine 8.0 and higher. If you have an Axon Ivy Engine older than version 8.0 you need first to migrate to a newer version.

License

You need to request a new license for Axon Ivy Engine 11.1.

Axon Ivy Environments

Axon Ivy Environments have been removed, finally. We detailed the reason for this in our blog post.

Axon Ivy Environments have been used for staging and in some rare cases for multi-tenancy. If you have used them for staging, the initial use case, then you shouldn’t face any issues. Make sure that the Default configuration is correct for each of your staging Environments. If you have used it for multi-tenancy, then you need to manually migrate each tenant to either its own Axon Ivy Engine or its own Axon Ivy Application. Read more about this topic in Multi-Tenancy.

It has been possible to set the Environment on application, session, and case level. All of these APIs and configurations have been removed completely. Using Environments, you have been able to define specific configuration sets for:

• Variables

• REST Clients

• Web Service Clients

• Databases

• Business Calendar

You have been able to define the cache on the Environment level using the Data Cache Tab. This will be migrated automatically to the application level.

For Unit Tests, you have been able to set the current Environment on the AppFixture. This has been removed, too. Now, use the AppFixture#config` API to define the exact configuration which you like to override in your test case.

Axon Ivy Files have the Environment name in their path. The existing files all stay at their current path. All new files will be saved in the Default Environment. Later on, we intend to redesign the path of files completely to remove the Environment dependency.

MsSQL Server Database

The JDBC driver for MsSQL server database has been upgraded and now connects to the database with SSL by default. To change the behavior back to non SSL as in previous versions set the connection property encrypt to false. Because this is the new default behavior of the driver, both System Database and External Database configurations are affected by this change.

AJP Reverse Proxy Integration

The AJP integration for Reverse Proxy has finally been removed. You need to migrate to URL Rewrite if you still have used AJP.

Mobile Workflow REST API

We no longer use the term mobile for the Workflow REST API. Therefore we renamed the configuration property in ivy.yaml from REST.Servlet.MobileWorkflow.API to REST.Servlet.API and this REST API is now by default enabled.

URL changes

We now emphasize the security context and manage all resources under the security context. We add the name of the security context as a prefix to all URLs, e.g., /{securityContext}/{myApp}/*.

As standard, the default security context is made available under root: /{myApp}/*

The core REST endpoints now run directly under the security context and no longer under the application, for example /{myApp}/workflow/tasks has been changed to /{securityContext}/workflow/tasks.

You need to check your routing settings in the reverse proxy configuration if you only allow certain paths.

---

Tag Legend:

This migration is handled either by the Migration Wizard or by the System Database conversion. The wizard will interact with you if you are affected by this change.

This migration will change something in the engine operation. If you are responsible for the operation of an engine, check if this change affects you.

This migration highlights behaviors or features that are deprecated. That functionality will be removed soon. If you are responsible for the operation of an engine, you should check if this change affects you.

This migration will remove a behavior or feature that has been available for the engine operation. If you are responsible for the operation of an engine, check if this change affects you.

This migration is handled by the Project Conversion automatically.

This migration will change a certain behavior in the projects. If you are a project developer, check if this change affects you.

This migration will mark features or APIs as deprecated in projects. That functionality will be removed soon. If you are a project developer, check if this change affects you.

This migration will remove a behavior or feature of a project. If you are a project developer, check if this change affects you.