Introduction

This document lists and answers frequently asked questions related to ICM N.

Is There a Customized Maintenance Page for ICM N as There Was for ICM 7.10?

No. There is no special page or maintenance mode in ICM N Web Adapter containers that could be turned on. There will be no Web Adapter in new ICM versions in the near future.

How to Configure the Mail Service?

Starting with ICM N, the mail service is handled directly in the ICM application. For details, see Cookbook - Mail Service.

How to Use a Transfer Server?

The following sections describe how to set up and use a transfer server for ICM N.

Setup

The following transfer servers are available:

ops-ca-trans01.westeurope.cloudapp.azure.com (to be replaced)
ops-ca-trans02.westeurope.cloudapp.azure.com
ops-ca-dev-us-trans01.centralus.cloudapp.azure.com

To use these transfer servers for ICM N, implementation partners (DEV) must specify user access details on the customer system Confluence page. This involves determining which users can access specific SFTP user spaces and providing the corresponding public SSH keys.

There are standard SFTP users such as (CSTMR has to be replaced by CustomerID):

icm_CSTMR_int
icm_CSTMR_uat
icm_CSTMR_prd
ish_dev_dumps_CSTMR

Note

User spaces are not created automatically. If any are missing, submit a Service Now ticket and document the changes in the transfer server section of the customer system Confluence page.

Connections are established via SFTP, not SSH.

Example:

$ sftp icm_CSTMR_int@ops-ca-trans01.westeurope.cloudapp.azure.com:/home      
Connected to ops-ca-trans01.westeurope.cloudapp.azure.com.
Changing to: /home
sftp> ls -l
drwxr-xr-x    5 1001     1001         4096 Aug 29  2023 Demo
sftp> ^D

The Intershop Cloud Operations team will roll out all keys to the related transfer server.

Usage

If a SFTP user should be used for the transport framework (ICM jobs), when we need to add SSH keys for the ICM appserver users inside the ICM Pods.

Note

There is a change to ICM 7.10. The Intershop Cloud Operations (OPS) team will no longer initially create these keys.

ICM developers are responsible for generating the SSH keys themselves, placing them within the site's file system inside the Pods, and configuring the transport framework accordingly.

Typically, one key is expected for each environment: PRD (LV+ED), UAT (LV+ED) and INT LV+ED), i.e., three keys in total.

For example, in the case of a customer (CSTMR), keys are deployed to /intershop/sites/root/units/root/transportconfigs/, with private keys located in the ADO GIT within the cartridge CSTMR_migrate/src/main/resources/resources/CSTMR_migrate/sites/root/units/root/transportconfigs/” in files prd_id.rsa.

Implementation partners must decide on the SSH key naming convention for UAT and INT shares, for example "test".

Here an example:

intershop@icm-CSTMR-int-edit-icm-as-6d75675867-x66wj:/intershop $ ls -l /intershop/sites/root/units/root/transportconfigs/
-rwxrwxrwx 1 intershop intershop 1743 Mar  3 17:17 prd_id_rsa
-rwxrwxrwx 1 intershop intershop  471 Mar  3 17:17 prd.pub
-rwxrwxrwx 1 intershop intershop 1751 Mar  3 17:17 test_id_rsa
-rwxrwxrwx 1 intershop intershop  473 Mar  3 17:17 test.pub

The path to be used is like this: /intershop/sites/CSTMR-Site/units/CSTMR/impex/config
The path /intershop/sites/root/units/root/transportconfigs/ is to be used in the transport framework configs.
The keys should be created with OpenSSH, ex: ssh-keygen -t ed25519 -C "intershop@CSTMR_INT"
The implementation partner should send the created SSH public keys in a Service Now ticket, so that OPS can add them to GIT and roll them out.

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.