• Setup of local environment

• Build tools migration to ICM 11+

• Dependencies migration to ICM 11+

• Code migration to ICM 11+

• New ICM 11 cartridge dependencies

• New structure of ICM REST API

• *.resource files in share/system/config/domains

• Other files deployed to share/system/config

• Staging/replication environment/framework

• Data migration to ICM 11+

• Test & bug fixing

• Intershop OPS support for new infrastructure

• Project management & coordination

• Tech lead involvement

• Test planning, preparation, and execution

• Additional documentation

• Additional meetings

• Support for performance testing

• Coaching and training

Precondition: Migration to ICM 7.10 base version for ICM 11 migration

Base versions for ICM 11+ migrations are ICM 7.10.38.29 and all later 7.10 versions.

The effort increases with the age of your current ICM 7.10 version.

Required only if project is on ICM 7.10 version < 7.10.38.29:

• This is a regular ICM 7.10 migration

• The older your current version is, the higher the effort

environment.bat.example and icm.properties.example

By default, there are no gradle_environment.bat/.sh and icm.properties example files anymore.

Tool: ICM Migration Support, 001_migration_7x10_to_11/901_CreateEnvironmentExampleFiles.yml

Manual Task: Adjust example files. In each local DEV environment, create the actual files from it.

The tool already creates project-specific example files.

Effort calculation based on adjustments made in these files.

75% tool coverage

Structure of directories in a cartridge

The directory structure within a cartridge has changed.

Tools:

• ICM Migration Support, 001_migration_7x10_to_11/010_MoveFiles.yml

• ICM Migration Support, 001_migration_7x10_to_11/015_MoveDBPrepare.yml

• ICM Migration Support, 001_migration_7x10_to_11/020_MoveFolder.yml

• ICM Migration Support, 001_migration_7x10_to_11/025_MoveJavasource.yml

• ICM Migration Support, 001_migration_7x10_to_11/060_AddSiteContentPreparer.yml

Effort calculation based on amount of cartridges

90% tool coverage

build.gradle replaced by build.gradle.kts

The build.gradle files contained in each cartridge’s root folder migrated to build.gradle.kts: Kotlin syntax, ICM 11+ content/syntax, changed libraries/versions/cartridges

Tools:

• ICM Migration Support, 001_migration_7x10_to_11/030_ConvertBuildGradle.yml

• ICM Migration Support, 001_migration_7x10_to_11/035_ConvertToCartridgeDependency.yml

• ICM Migration Support, 001_migration_7x10_to_11/040_RenamedDependencies.yml

• ICM Migration Support, 001_migration_7x10_to_11/045_RemovedDependencies.yml

• ICM Migration Support, 001_migration_7x10_to_11/055_MigrateVersions.yml

• ICM Migration Support, 001_migration_7x10_to_11/070_ConvertToKotlin.yml

• ICM Migration Support, 001_migration_7x10_to_11/100_DeleteObsoleteFiles.yml

Effort calculation based on amount of cartridges

90% tool coverage

Feature (ft_*) cartridges

Feature cartridges are new in ICM 11. Such cartridges did not exist in ICM 7.10.

Approach “Runnable Feature”, “Demo Feature”, “Test Feature”:

• ft_production, ft_demo, ft_test

Alternative approach using one feature cartridge per environment:

• ft_production, ft_preproduction, ft_integration, ft_development

Manual Task: Add dependencies to project cartridges

Effort calculation based on approach

Application Suite (as_*) cartridges

Application Suite cartridges configure and integrate multiple application types to form a complete business scenario, e.g.: as_headless, as_backoffice, as_sldsystem, as_smc

Manual Task: Connect the business functionality with the application types

Effort calculation based on amount of applications using custom cartridges and number of custom cartridges added to each application

ICM cartridge dependencies

Cartridges might need to declare more dependencies in the build.gradle.kts.
Error report for cartridges depend on both, front end as well as back office cartridges.

Manual Task: Declare missing dependencies

Effort calculation based on amount of cartridges

Storefront REST API

The implementation of the REST APIs has changed.

Manual Task: Check implementation of all changed/overwritten REST APIs

For effort estimation, count the overwritten implementations of intershop.WebShop.RESTAPI.*.

Effort calculation based on amount of customized REST APIs

*.resource files in share/system/config/domains

“Test System Configuration Solution Kit” (pf_configuration_fs) resource files need to be migrated to *.properties files and wired in configuration.xml files.

Tool: ICM Migration Support, 001_migration_7x10_to_11/050_MigrateConfigResources.yml

Effort depends on the amount of .resource files in config/domains/**

95% tool coverage

Custom Deployment

Files deployed to share/system/config, deployment instructions and custom fixes.

There are no deploy.gradle and assembly/build.gradle files in ICM 11+, and custom files cannot be deployed to share/system anymore.
Some files are handled by step “Structure of Directories in a Cartridge” already.

Tool: ICM Migration Support, 001_migration_7x10_to_11/010_MoveFiles.yml

Manual Task: Handle remaining files and all deployment instructions

For effort estimation, count:

• The number of deployment instructions in all deploy.gradle files and in assembly/build.gradle

• The number of files deployed to share/system/config

• The number of custom fixes replacing/overriding standard code

Effort calculation based on amount of deployment instructions, files, and custom fixes

50% tool coverage

Attention Points

• Projects might use libraries/systems/access/functionality/payment connectors, and especially microservices that are not available anymore (and no suitable replacement is available)

  • Example: External system can access database directly in an on-premise installation, but there is no way to provide such access in the cloud

• Projects might have requirements/restrictions that are not as easy to met in the Azure Kubernetes Cloud

  • Example: Latency in cloud is much higher than on-premise and where number of request (e.g., app server → database or interface) is already very high, it could not work anymore in cloud

  • There could be restrictions for interfaces, SMTP servers, etc. that do not allow connections to/from the internet

Manual Task: Create/use/include alternative implementations/tools

Staging/replication environment/framework

Changes are required for replication.xml, replication-clusters.xml, etc. for general replication as well as for the setup of staging on the local DEV system.

Manual Task: Follow instructions in Guide - 7.10 - 12 Replication and Staging Adaption

Effort depends on the complexity of the individual staging process

Logging AppServer messages and Managed Service errors/requests/responses

Log only important information using log levels ERROR, WARN & INFO.
There is no share/system/log anymore. Custom log files should be placed in subdirectories of ${intershop.logfile.Directory}

Tool: Move logback configuration

Manual Task: Adapt the log configuration to the aggregation framework as needed by project

Effort calculation based on amount of custom log files and adaptations of the log configuration

Migration to ICM 12

Tools:

• ICM Migration Support, 001_migration_7x10_to_11/065_RenamedPackages.yml

• ICM Migration Support, 002_migration_11_to_12/005_ClasspathResourceFileCopier.yaml

Effort calculation based on amount of Java code

95% tool coverage

Migration to ICM 13

Remove ~150 deprecated methods/variables/constants/classes, etc.

Tool: ICM Migration Support, 003_migration_12_to_13/005_ClasspathResourceFileCopier.yaml

Manual Task: Follow instructions in Guide - 13.0.0 API Changes

Effort calculation based on the uses of removed/changed APIs

90% tool coverage

Setup and Preparation

Developer ramp-up/training for ICM 11+

Online training about migration tools and AI support: https://public.academy.intershop.com/plus/catalog/courses/450

Gap training for new projects: https://public.academy.intershop.com/plus/catalog/courses/348

Setup of local developer environments

(Setup and configuration of new AKS environments)

Local developer environment per developer

Testing

Test Preparation

Depends on what already exists (automatic tests, QA policies, etc.) and needs to be updated

Test and Bugfixing

• Fixing all migration-related findings

Depends on amount of code changes and scope of QA

Rollout

Preparation

• OPS support and QA for new infrastructure environments

• Build/CI/CD Helm charts

Create a cutover checklist and plan in collaboration with Intershop Operations Team

Final check of configuration, esp. Build/CI/CD Helm charts

Cutover

• OPS support and regression testing

Execute cutover plan, hypercare on demand

Management and Coordination

Project Management

Depends on your specific project policies, guidelines and processes, project duration, team size, and technical complexity

Technical Lead Engineering

Depends on your specific project policies, guidelines and processes, project duration, team size, and technical complexity