Document Properties
Last Modified
Added to KB
Public Access
Doc Type
Release Notes
ICM 7.8

Public Release Note - Intershop Commerce Management B2C/B2X 7.8

Table of Contents

Product Name

Intershop Commerce Management

Product Version


Product To Version



1 Introduction

Welcome to Intershop Commerce Management 7.8.

This Public Release Note contains information about the latest features of Intershop Commerce Management. In addition, it servers as a quick reference for the latest documentation.

2 Assemblies

2.1 Intershop Commerce Management B2C

Assembly NameDescription
com.intershop.assembly:commerce_management_b2cBase Assembly for Intershop Commerce Management B2C (this is the base of all B2C projects).
com.intershop.responsive:inspired-b2cDemo Store "Inspired" B2C (source of this assembly is the starting point for B2C projects).

2.2 Intershop Commerce Management B2X

Assembly NameDescription
com.intershop.assembly:commerce_management_b2xBase Assembly for Intershop Commerce Management B2X (this is the base of all B2B projects).
com.intershop.responsive:inspired-b2xDemo Store "Inspired" B2X (source of this assembly is the starting point for B2B projects).

3 New & Noteworthy

With Intershop Commerce Management (ICM) 7.8 we are supporting microservices for the Application Server tier for the first time. This means that Intershop provides a blue-print for building and deploying microservices which can be used from the Application Servers. Our first feature implemented with microservices is Recurring Order. This feature consists of a RecurringOrder and a Scheduling microservice.

4 Limitations

In conjunction with microservices there are some shortcomings with respect to deployment and services:

  • If you are running Eureka server as a Windows service you might experience a problem stopping the Netflix Eureka via Windows service. Temporary Solution: kill the process.
  • Microservices can be only deployed per Application Server. Host type Microservices via Gradle deployment is not working currently.
  • Installing a service via systemctl as systemd under Linux seems to fail occasionally. Temporary Solution: use init.d instead.
  • It is necessary that the following eureka attributes within the eureka extension in the settings.gradle end with an '/'
    • serverUrlPath
    • serviceUrls.default
  • If you are deploying the microservices under linux and derby is used as datasbase, the configProperties['javax.persistence.jdbc.url'] must contain an absolute path
    • e.g., configProperties['javax.persistence.jdbc.url'] = 'jdbc:derby:<SERVER_HOME>/local/microservices/runtime/testdb;create=true'

5 Release Documents

5.1 System Requirements

To read about the newest system requirement, please refer to System Requirements - Intershop Commerce Management B2C/B2X 7.8.

The Reference - CI Dependencies of Intershop Commerce Management provides a mapping of all:

  • CI-versions of the ICM
  • Intershop CI Bootstrap version
  • Intershop Gradle Tools version
  • Intershop Responsive Blueprint Store version

5.2 Feature Lists

Please see our feature lists for more details about the new release:

6 Concepts & Cookbooks

The following documents are updated or entirely new for ICM 7.8:


Intershop does not provide the "Administration and Configuration Guide" any longer. Instead this documentation is now available via the Knowledge Base.

7 Migration Guides

Intershop provides Migration Guidelines to ease the migration from 7.7 to 7.8.

8 Changelog

8.1 Release


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 Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.

Customer Support
Knowledge Base
Product Resources