Before you start take some time to review the prerequisites below. This will save you a lot of time later
A Runbook is a mandatory step that you need to do (see below)
Please review the Transport management and delivery process which Promenta follows. The process should align with your existing standard processes but it is always good to check and confirm.
Click here to review
You will be performing some BASIS functions and some configuration
Some transactions required for the successful set up are :
SICF Web services
SU01 User maintenance
SNUM : Number interval maintenance
SM59 : RFC destination (if creating service updates)
2. BSP Runtime
The BSP runtime engine should be configured as per SAP configuration procedures.
if you run any SAP web technologies (BSP, WebDynPro, Fiori) this will already be set up.
The information below should be used as a guide only.
2A SAP profile parameters – assign a port to the ICM via transaction RZ10 eg :
2B Activate ICF services
/sap/public/bc/bsp ==> If this service is inactive user display will be incorrect
default_host → sap → public → bc → uics. [See note 2389051 – ICF service for Clickjacking Framing Protection is inactive]
3. Webserver Security (SSL/HTTPS)
Install a valid SSL certificate. If SSL (HTTPS) is to be used then a valid SSL certificate must be installed on the server node or the web-dispatcher
This must not be a self-signed certificate as modern browsers increasingly do not accept them
Creation of a customer-specific runbook is a customer responsibility
The customer must maintain a runbook of activities to install Promenta and any other settings. This will be a combination of this installation guide, settings specific to your solution and other activities outside of Promenta software such as role creation, change-request tickets and any other customer-specific activities.
The customer is recommended to create the runbook while installing into the QA environment and then running the runbook in pre-production to validate that no steps are missed