Table of Contents Introduction Migration Support Migration Guidelines Introduction A migration from ICM 7.10 to the new ICM generation (11+) is officially supported from ICM 7.10.38.29 and later to ICM 12.1.0 and later. The migration documents describe the migration from ICM 7.10 to 11. Mostly, there

Description The customer tried to change the log level in production (seceral application servers) and got this exception in the log: [2023-11-14 12:59:11.698 +0100] WARN <Server Name> ES6 appserver0 [SMC] [-] com.intershop.beehive.core.internal.request.RequestHandlerServlet [] [Storefront] [ornEyy6

Description OPS and Support must check the pods on which processes were executed / currently running in an ICM 11 cluster (e.g. for creating thread dumps or restarting the pods). This was easily possible with ICM 10 by checking the process details in the SMC. With ICM 11, the "Host Name" and "Server

Description Sometimes ProcessCXMLPunchOutSetup-Start and ProcessCXMLOrderInjection-Start requests get stuck during the DTD validation Http request. At this point all new requests queue up in state BLOCKED waiting for the hanging request to get finished. Once all allowed application server requests are

Description replication from Edit to Live for our (one) organization and (one) channel. After each replication the DB table CustomerAccountMgrAssignment is empty in the Live system. Means: In back office the list at "Channel > Customers > Customers & Users > #Customer# - Account Managers" is empty and

Description Slow request response in case of REST categories access. Steps to Repeat ICM 11.3.1 project does execute REST categories request by using URL: https://localhost:8443/INTERSHOP/rest/WFS/inSPIRED-inTRONICS-Site/rest;loc=de_DE;cur=EUR/categories?view=tree&limit=2&omitHasOnlineProducts=true The

Description When trying to get a Basket using the "GetBasket" pipelet very fast a deadlock could occure. Steps to Repeat Difficult to repeat. The customer is calling the recommendation engine service via AJAX requests and the "GetBasket"-Pipelet is called very frequently (nearly in parallel). During

Description According the ADR 12 the PUT request (create or recreate) should return code 200 (it's more implicitly mentioned) PUT request gives HTTP code 201 when first creating and HTTP code 200 on recreate Also see: - https://intershop.atlassian.net/wiki/spaces/ISEA/pages/16061394462/ISH-ADR-0007+

Description Affected validation classes are UserROValidator:170 only seems to be used in back office REST API (AppBoRestCustomerHandlerModule) verify if true, this class doesn't have to be changed PrivateCustomerROValidatorImpl:150 SMBCustomerUserROValidatorImpl:147 customer.credentials.login.not_unique

Description When creating a recurring basket, the start/end date of the recurrence interval is stored in the database together with a timestamp, resulting in a different display of the start/end date depending on the time zone used by the application. In the basket: Set recurring interval start date