This document outlines the migration process from ICM 11 to ICM 12. It includes the automated steps performed by the migration tool, as well as the manual steps required afterward.
The automated steps for migrating from ICM 11 to ICM 12 are defined in: src/main/resources/migration/002_migration_11_to_12.
Example command:
gradlew migration:migrateAll -Ptarget=$ICM -Psteps=src/main/resources/migration/002_migration_11_to_12
Migrator: ClasspathResourceFileCopier
This adds Intershop's migration recipes to the root of the project for use with OpenRewrite.
Run OpenRewrite to apply Jakarta EE migration recipes to the migration project:
gradlew --init-script rewrite.gradle rewriteRun
Note:
The migration process, especially when running OpenRewrite or other code transformation tools, may require a significant amount of memory.
Intershop recommends increasing the maximum heap size for Gradle by setting theGRADLE_OPTSenvironment variable, for example:
set GRADLE_OPTS=-Xmx4G(on Windows) orexport GRADLE_OPTS=-Xmx4G(on Linux/macOS).
setEnableJobProcessors(Collection<String>)createJobCrontabTimeCondition(Domain, Date, String)isJobAllowedOnServer(ServerInfo, JobConfiguration) The ISML expression logic contained an evaluation failure if a conditional value was undefined. The issue was fixed in ICM 12, but requires an adaption of the ISML expressions in the project code.
See [Guide - 12.x.x API Changes](https://knowledge.intershop.com/kb/index.php/Display/312H13) for more details.
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Website, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.