The data models for server-side and client-side have to be separated, because the data sent by the server may change over iterations or may not be in the right format, while the client side shop data handling should be stable for a long time. Therefore, each service communicating with the Intershop REST

Server-Side Rendering (SSR) The express.js image serving the Angular Universal Server-Side Rendering can be provisioned to log extended information to the console by supplying the environment variable LOGGING=true . Information logged to the console includes the following: Requests to the SSR process

To enable Store Locator, add storeLocator to the feature list in your environment file. This will enable a page where users can search for stores based on a country, city and/or postal code. Store Locator provides an optional Google Maps integration using the Google Maps JavaScript API. This feature

To enable user tracking and setting it up with Google Tag Manager, the popular library Angulartics2 is used. Note The standard Intershop PWA Google Tag Manager integration is very basic and currently only supports the tracking of route changes. Please refer to the angulartics2 documentation for information

Introduction Recipe: Configure the Order Export for the BI Data Hub Recipe: Add BI Dashboard to ICM Recipe: Create Report Based on Intershop Template Recipe: Adjust Reports Recipe: Download Default Report Templates from Intershop Introduction The BI Data Hub allows you to gain insight into different

Table of Contents Introduction Step by Step Introduction The deployment processes in ICM 7.10.38.21 lead to a failed migration preparer execution of ExecuteSQLScriptPreparer, resources/core/dbinit/scripts/sp_deleteProcesses, caused by an invalid stored procedure. Deployments, which require a DBMigrate

Table of Contents Introduction Using Your Own Code Quality Service Introduction Intershop does not provide any code quality service as part of the Intershop development environment. However, it is possible for partners to include their own services and service configurations. Therefore, Intershop provides

Table of Contents Introduction Step by Step Introduction This document provides an instruction how to deploy an ICM environment without SolrCloud cartridges. Step by Step Remove SolrCloud cartridges from the project related ICM assembly file, e.g., \a_responsive\inspired-b2c\build.gradle assembly {

Sometimes during development it might be necessary to work with mocked data. This is especially necessary when developing new features in parallel where backend and frontend are involved. In the PWA we supply a mocking mechanism so the frontend team can start implementation with mocked data until the

Table of Contents Introduction Glossary References How to Construct Customer-Specific Assortments Efficiently Target Group and Contents Target Group Contents Where is the Data Stored? Case: Few Products, Many Customers Case: Many Products, Few Customers Case: Many Products, Many Customers Extend or

Introduction Glossary References Process Description Result of Checks - Combination of Results Result of Checks - Server Status Change Mapping Health Checks Database Connection Database Configurations Sites Folder Existence HTTP Status Code Health Response Time Health Health Checks in ICM 7.10 Process

Table of Contents Introduction Migration Inspectors Self Checks Server Status Constants Server Environment, Server Information, and ServerInfoFilterCondition Eureka Server Health Disable Self Checks Disable Individual Checks Try-Run Runtime Checks Introduction This migration guide applies to 7.10.38

Table of Contents Introduction ICM <7.10.38.20-LTS ICM 7.10.38.20/21-LTS ICM 7.10.39.1/2 ICM >7.10.38.21-LTS Introduction The replication in ICM 7.10.38.20/21-LTS and ICM 7.10.39.1/2 Oracle environments does not work due to an error in the AbstractStagingJDBCUtils.executeQueryResultFunctionWithPool

Table of Contents Introduction Changes This migration guide applies for 7.10.38.20 LTS and 7.10.40.4. Introduction Deploying an environment without a_responsive results in a loss of entries in the PREFERENCEDEFINITION database table. Affected preferences are: OrderNotificationEmailFrom OrderNotificationEmailTemplate

Unit Testing with Jest Stick to General Unit Testing Rules Single Responsibility Test Functionality - Not Implementation Do not Comment out Tests Always Test the Initial State of a Service/Component/Module/... Do not Test the Obvious Make Stronger Assertions Do not Meddle with the Framework Assure Readability

The Intershop PWA features its own cookie consent implementation that allows to configure the different options a shop user should be presented with when deciding which types of cookies the user wants to allow and which not. Based on this decision, a cookie is written that stores the user's cookie consent

This document describes how to provide the Intershop PWA with a dynamic deploy URL to set up client-side retrieval of static assets and JavaScript chunks from a (possibly) different source than the URL from which the pre-rendering is delivered. Built-in Angular CLI Support By default, Angular CLI supports

Change detection is one of the core concepts of Angular. Component templates contain data bindings that embed data from the component class into the view. The change detection cycle keeps view and data in sync. To do so, Angular re-evaluates all data expressions from the templates every time the CD runs

Motivation Imagine running an Europe-wide shop with Intershop, where the website is available in 16 different countries with different languages and a varying selection of products, but only little modification of the website appearance over all. This would be set up by having 16 channels with one headless

Simple Browser-Side Rendering Angular applications are built for a static deployment by default. When running npm run build in any shape or form, the build output is aggregated in the dist folder and the resulting files can be statically served using any HTTP server that is capable of doing that (only