You will be performing some BASIS functions and some configuration
Some transactions required for the successful set up are :
- SAINT Add-on installer
- SM30 Table maintenance
- SICF Web services
- SU01 User maintenance
- SE09/SE10 to create transports
2. 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
2C Install 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
3. Object overwrite checks
Promenta Webflow is an SAP certified product. As such 99% of all all R/3 development components are delivered within the /PROMENTA/ reserved namespace.
However there are a few areas of the SAP R/3 ERP system that do not allow the use of an explicit namespace. Examples objects are: security roles, authorisation obejcts and number range objects.There is a small chance that development objects which fall into this category already exist on the customer’s system
To mitigate this risk Promenta deliver a pre-install checker program (in the promenta namespace) which checks for the existence of objects that are at risk of being overwriten BEFORE the application of the main package
3A. Run check
use transaction SE16 in non-production system (eg development)
On the selection screen enter the following seelctions
PGMID (Program Id)
OBJECT (Object Type)
OBJ_NAME (Object Name)
Ensure no objects are found