Installation post-processing

Check that HTTP(S) service is active

Make sure that at least one HTTP service is active using transaction SMICM before continuing with the next step.

See transaction: SMICM, Goto, Services <Shift-F1>

Transaction SMICM, Goto, Services

Run the post-installation wizard

Run the post-installation wizard in every Solution Manager client where Protect4S needs to run, by executing transaction: /n/ESEC/SA_PI. Do this with a user that at least has the role /ESEC/SA_ADMINISTRATOR. The wizard will activate the necessary SICF services (see appendix D). It will also prompt for the license installation and Quick setup.

Post installation wizard (1)

License installation

  • ✔ Protect4S needs an installed and valid license in order to execute. The first time that Protect4S is started, this license must be installed. A valid license file will be supplied by the ERP-SEC Support team during the purchasing process.

  • ✔ Should you have lost this file or never received it, please contact the ERP-SEC support team via:

Protect4S License Administration

In this screen, press the button labeled: "New".

This will start up a new screen in which you can upload and save the license key file:

Upload License Key file

After uploading and saving the license key file, you will be able to see the license in the overview in the License Administration:

License overview

You may inspect it by selecting the "Display" button:

License display

Continue with the Post installation wizard

Post Installation wizard (2)

After having installed the license: select yes.

Post Installation wizard (3)

Press Close in order to inspect the Application settings.

After confirmation of this popup, you must supply data for the application settings: a background user that runs the scan jobs (This must be a user with the role /ESEC/SA_BACKGROUND_EXECUTOR), an optional server group to limit the amount of dialog work processes used for parallel scan processing and a reply-to email address for the notification mails send from Protect4S. Make sure to also set the Background job in the lower part of the screen to Active to make sure notifications are received if desired.

Application settings

Continue with the post installation wizard

Post Installation wizard (4)

Select Yes in order to start the Protect4S launch pad

Protect4S is started via transaction: /n/ESEC/SA_LPAD, which opens the Protect4S launch pad menu. Please take into account that the initial load generation might take some time. Should the transaction timeout, please refresh the page again with the key or set a higher value for SAP parameter rdisp/plugin_auto_logout usingtransaction: RZ11.

You may have to restart transaction /n/ESEC/SA_LPAD several times before all necessary objects have been generated. After that, the protect4S launch pad will appear and the application is ready for the license installation.

Protect4S launch pad

  • Every menu Item selected will start in a new browser tab. When you have finished using an item, you may simply close the tab.

Protect4S Fiori Post-Install

In the active Solution Manager client, use SM30 to add the following table entry to view /IWFND/V_MGDEAM

  • Service Doc. Identifier = /ESEC/SA_RISK_OVRVW_SRV_0001

  • SAP System Alias = LOCAL_SM

  • Default System = X

  • Tech. Svc. Name = /ESEC/SA_RISK_OVRVW_SRV

  • Ext. Service Name = SA_RISK_OVRVW_SRV

Protect4S startup via Technical Monitoring menu

Protect4S is configured as a Solution Manager work center in the Technical Monitoring area and can also be started from there.:

Protect4S workcenter