com/blog/nginx-caching-guide/ Video Tutorial - Building and Running PWA SSR and NGINX Docker Images https://support.intershop.com/kb/3084Z0 Caching Options in a PWA Environment • output. In the PWA, the ICM web adapter is used for handling and caching REST calls. It also delivers back office CMS content components to the PWA. Cache Configuration • responses should be cached. In the Dockerfile of the standard Intershop PWA under intershop-pwa/nginx/Dockerfile these variables are defined as follows: [...] ENV

Intershop Progressive Web App 2.0. This public release note contains information about the latest features of the Intershop Progressive Web App. In addition • documents: System Requirements - Intershop Progressive Web App 2.0 Feature List - Intershop Progressive Web App 2.0 (EN) Refer to the following documentation • optional link target parameter (037253c) Compatibility Intershop Progressive Web App Intershop Commerce Management B2C/B2X Version 2.0.0 7.10.38.0-LTS

enables the following features to be used in an Intershop PWA deployment: Uncomplicated caching of PWA server-side rendering responses provided by the upstream • server and be answered at the cost of a delay. Guide - Building and Running Server-Side Rendering Guide - Building and Running nginx Docker Image Concept • 6004b71a5a27703d29407d8cf9406711 GitDocument docs/concepts/pwa-building-blocks.md intershop/intershop-pwa develop

several REST endpoints to support cXML Punchout. The Intershop Progressive Web App (PWA) uses these endpoints to provide a proper cXML Punchout end to • Intershop Commerce Management SMC System Management Console PWA Intershop Progressive Web App References The following documentation is related to the cXML • </PunchOutSetupResponse> </Response> </cXML> The returned PWA URL is the External Base URL maintained in the Progressive Web App application properties (tab General) in

Mobile Order / Telephone Order PWA Progressive Web App REST REpresentational State Transfer UI User Interface References Guide - Setup Cybersource Service • Types PWA* Cybersource Service Connector 7.10.29.2+ intershop.REST 0.29.0+ 1.1.0 - 1.1.2 7.10.32.11-LTS + intershop.REST 1.4.0 1.2.5 * Please see PWA release • API, never touching your systems. This UI integration is provided by the PWA by accessing the connector through the Intershop REST API. Glossary Term Description

that decides which one to use. The PWA uses the Angular Formly framework to process web forms, see also The Formly Guide. This framework allows you to automatically • validation for this topic is also disabled in the PWA. The following table shows the mapping between existing PWA CAPTCHA topic names and the CAPTCHA channel • Introduction The PWA supports reCAPTCHA V2 as well as reCAPTCHA V3. Which CAPTCHA version is used depends on which CAPTCHA service is created and running

setting, the required flexibility for the Intershop PWA cannot be achieved. For example, if the Intershop PWA Docker image is deployed in multiple environments • and can be changed without rebuilding the Intershop PWA. Building with Dynamic Deploy URL The PWA client-side application has to be built using ng build • be solved with the Intershop PWA out of the box. CDN Support If you want to deploy all static resources of the Intershop PWA to a Content Delivery Network

Intershop Order Management (IOM), and Progressive Web App (PWA) systems are more or less complex procedures. This guide explains the various aspects of how • Production environment Software ICM Intershop Commerce Management PWA Progressive Web App (new storefront of ICM) IOM Intershop Order Management Persons in • deployment of the ICM (and IOM) and PWA takes place, the ICM (and then the IOM) is deployed first, immediately followed by the PWA deployment on the same environment

Note This migration guide applies for 7.10.26.11-LTS as well. Both storefront implementations Intershop Responsive Starter Store and PWA contain a "Contact

10 7.10 Guide - 7.10 Build and Deployment 7.10 7.10 Guide - 7.10 REST API Changes 7.10 7.10 Guide - 7.10.5 Migration Messaging 7.10 7.10 Guide - 7.10.10 • 9 7.10 Guide - 7.10.13.4 Update Assembly Geb Configuration 7.10 7.10 Guide - 7.10.14.0 DBPrepare Replaces DBMigrate and DBInit 7.10 7.10 Guide - 7.10.15 • REST Resources 7.10 7.10 Guide - 7.10.16.6 New Solr Version 8.2.0 7.10 7.10 Guide - 7.10.18.0 Kafka Appender Removed 7.10 7.10 Guide - 7.10.18.0 Security Update

graph build afterwards. 5 Configure PWA A feature toggle for SPARQUE exists. Add this to your PWA. Refer to the PWA documentation for details: https://github • Search in your PWA now is powered by Sparque. You should be able to test everything. Trigger a graph build in SPARQUE desk. Search in your PWA. 8 Post-processing • returned. Adjust the PWA, so it learns how to render the additional information. In case you have changed the API parameters, adapt the PWA so it properly uses

Docker-based PWA NGINX and SSR Containers 3.1 Support Article - Internal Names of Custom Attributes 7.0 Support Article - PWA Content Integration Guide 7.10 Support

Select Progressive Web App application. Set the configuration External Base URL as https://domain-name:port (domain-name is complete URL for your PWA shopping • Payment Service Configure the Payment Methods Localization Introduction This guide outlines the basic setup and configuration steps for the Cybersource Service • requires additional post-deployment configuration steps. For details, refer to Guide - Setup Cybersource Service Connector#Configuration. Configuration Prepare

Description Description: Caching behavior from promotion REST resources is not perfect in terms of promotion disabled/expired scenarios and iscachekey invalidation Steps to repeat: - setup ICM system define a channel TestPromotion with a valid from to date; further assign product 5079721 as item request

Labels Guide - 7.10 Migration Mockito 1 to Mockito 2 Thomas Bergmann Guide 7.10 ICM 7.10 New Labels Guide - 7.9-7.10. API Changes Mario Vesper Guide 7.10 • Thomas Bergmann Guide 7.10 ICM 7.10 New Labels Guide - 7.10 Content Model Changes Robert Karl (Deactivated) Guide 7.10 ICM 7.10 New Labels Guide - 7.10 Database • Thomas Bergmann Guide 7.10 ICM 7.10 New Labels Guide - 7.10 Migration of Cartridge Properties Thomas Bergmann Guide 7.10 ICM 7.10 New Labels Guide - 7.10 Database

Displaying the Widget (PWA) For more information on implementing CAPTCHA functionality in the PWA, see CAPTCHA in the PWA @GitHub. The PWA uses the Angular Formly • validation for this topic is disabled in the PWA as well. The following table shows the mapping between the existing PWA CAPTCHA topic names and the CAPTCHA channel • of Contents Introduction References Configuration Displaying the Widget (PWA) Verifying the Response Implementation Artifacts Java Classes Templates Introduction

Displaying the Widget (PWA) For more information on implementing CAPTCHA functionality in the PWA, see CAPTCHA in the PWA @GitHub. The PWA uses the Angular Formly • validation for this topic is disabled in the PWA as well. The following table shows the mapping between the existing PWA CAPTCHA topic names and the CAPTCHA channel • of Contents Introduction References Configuration Displaying the Widget (PWA) Verifying the Response Implementation Artifacts Java Classes Templates Introduction

File Name Conventions In accordance with the Angular Style Guide and the Angular CLI convention of naming generated elements in the file system, all file • Modules As a developer who extends and customizes the functionality of the PWA, you should only consider modifying/adding to the following modules: src/app/pages/app • only on this page As a developer who develops new functionalities for the PWA, you also have to deal with the following modules: src/app/core/X.module -

with SPARQUE APIs. References Concept - Implementing Search with Sparque Guide - Use SPARQUE with Postman Recipe: Browse Categories Problem: How to Browse • Category Tree To retrieve the category tree, you can call ...domain.../api/PWA/e/categorytree/results?config=default&count=1000 This call returns pairs of • Retrieve Products Products can be retrieved via the call ...domain.../api/PWA/e/products/results?config=default&count=30 The result is a set of products

Starting from ICM 7.10.21, a new application type Progressive Web App is available and enabled for use with PWA 0.23.0 by default. The new application type is • type has to be enabled again. To achieve this , the PWA 0.23.0 entry icmApplication: 'rest' in the PWA file environment.ts has to be set back to icmApplication: • the box with Concardis version 1.11 and higher in combination with PWA 0.25.0++. PWA 0.24.0 and Concardis 1.10 are not compatible at all due to different