Related Documents
Document Properties
Kbid
289K35
Last Modified
28-Jan-2021
Added to KB
23-Nov-2018
Public Access
Everyone
Status
Online
Doc Type
Guidelines, Concepts & Cookbooks
Product
ICM 7.10

Guide - 7.10 Build and Deployment

1 Build Configuration Changes

1.1 Update Gradle Tools from 2.11.7 to 2.11.8

  • Default configuration of messaging is changed to JGroups 

1.2 Update Gradle Tools from 2.11.8 to 2.11.9

1.3 SCM Version Plugin Update to 2.6.0

  • In case the scm-version plugin is not well configured, the ivy publishing process will now fail with the error Invalid publication 'ivy': revision cannot contain '/'.

Please correct your configuration, depending on your project style guide, e.g. for often used branch pattern:

scm {
    prefixes {
        stabilizationPrefix = 'stabilization'
        featurePrefix = 'feature'
        hotfixPrefix = 'hotfix'
        bugfixPrefix = 'bugfix'
        prefixSeperator = '/'
    }
    ...
}

2 Deployment Configuration Changes

2.1 Moving Cartridge Properties to jar

All cartridge properties (e.g. bc_mail.properties) have been moved into src/main/resources. This means the deployment cannot override or exclude these files anymore. Please validate your deploy.gradle files and remove the according section. It is possible to override the configuration depending on your needs within your projects (e.g. /staticfiles/cartridge/config/your.properties).

2.2 Moving logback-<cartridge-name>.xml

In case your deployment extensions refer to standard logback configurations, you need to adapt the location.

Old LocationNew LocationReleaseHint
bc_pricing/staticfiles/share/system/config/cartridges/logback-bc_pricing.xmlbc_pricing/staticfiles/cartridge/logback/logback-bc_pricing.xml7.10.2.2In release 7.10.1.8 the file was moved to src/main/resources and cannot be adapted.
bc_basket_service/staticfiles/share/system/config/cartridges/logback-bc_basket_service.xmlbc_basket_service/staticfiles/cartridge/logback/logback-bc_basket_service.xml7.10.2.2In release 7.10.1.8 the file was moved to src/main/resources and cannot be adapted.
bc_contract/staticfiles/share/system/config/cartridges/logback-bc_contract.xmlbc_contract/staticfiles/cartridge/logback/logback-bc_contract.xml7.10.6.1

2.3 Recommended Usage of DBPrepare

Since 7.10.14.0 Intershop provides a new tool for database preparation and migration - dbprepare. During tests of migration to 7.10.24.0 performance problems of dbmigrate with MSSQL Databases occured. Please prefer dbprepare instead of dbinit and dbmigrate to avoid long running database migrations in the future.

Switch from DBInit/DBMigrate to DBPrepare

If your system was prepared using DBInit (and optionally migrated using DBMigrate) you have to run a DBMigrate before the first run of DBPrepare. Afterwards only DBPrepare should be used for database migration.

3 Oracle Driver Update 19c

Beginning with ICM 7.10.22.1 it is possible to update to Oracle driver 19. However, the JDBC drivers version 12.2.0.1 and above are affected by (non-public) bug 30964068 which may cause failure of the DBMigrate process. See Oracle Support Document 2689134.1 for more details.

We recommend to keep using version 12.1.0.2, until this bug is fixed in the main line drivers. If, for some reason, you are required to use a more recent driver, see Support Article - Apply Patch 30964068 to Oracle's JDBC Driver for information on how to update your Oracle driver.

3.1 References

4 Introduction of Sites and Configuration Project

Configuration files should be moved to a configuration project and "sites" files should be moved to the sites project. See "responsive_config" for a configuration project and "responsive_sites" as an example for a sites project in a_responsive. These projects contain the configuration or sites files and a deployment script.

Cartridges should not contain files for folders outside the cartridge folder. 

In a future version it is required to use a site or configuration project. Furthermore a cartridge must be self contained.

5 Apache HTTPD Support for mod_status and HTTP2 (since 7.10.27.0)

Configuration support to enable HTTP2 protocol and Apache insights with 'mod_status' are prepared. Support to enable both features with deployment exists for Linux only.

Add the following lines to the file httpd/bin/envvars with your deployment to enable both features:

httpd/bin/envvars
ENABLE_HTTP2=true
ENABLE_STATUS=true

The default configuration for the 'mod_status' module restricts access to the host only.


Disclaimer

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
Tickets