This page explains how to prepare a SAP S/4HANA Cloud Private Edition managed system for the execution of the Simple System Integration.
Currently, the following monitoring applications are supported for SAP S/4HANA Cloud Private Edition systems:
Please be aware the setup needs to be supported by SAP Enterprise Cloud Services.
| Task | Actions |
|---|---|
| Preparation Tool (optional) | In order to automate certain tasks, you can use the Preparation Tool |
| Run Outside Discovery on the Host | As prerequisites, you shall install the SAP Host Agent and run Outside Discovery as described in Preparing Outside Discovery page. |
Install SAP NetWeaver ABAP SAP Focused Run supports the latest SAP NetWeaver version | Install/Upgrade to the latest SAP NetWeaver version from support.sap.com/swdc Note: SAP Note 2188401 shall be implemented for NetWeaver ABAP < 740 SP13 |
ABAP ST-PI version ABAP-specific SAP Focused Run functions are delivered with ST-PI | If possible, please use the latest version and keep it up to date. It is recommended to update ST-PI always together with the regular product stack support packages to benefit from latest functionality and patches. Please note that these software components may not be part of the regular support package stack but have to be downloaded separately. For ST-PI refer to SAP Note 539977 Release strategy for add-on ST-PI. |
ABAP ST/A-PI version Application-specific SAP Focused Run functions are delivered with ST/A-PI | If possible, please use the latest version and keep it up to date. It is recommended to update ST-A/PI always together with the regular product stack support packages to benefit from latest functionality and patches. Please note that these software components may not be part of the regular support package stack but have to be downloaded separately. For ST-A/PI refer to SAP Note 69455 Servicetools for Applications ST-A/PI (ST14, RTCCTOOL, ST12). |
Change the Default Profile The Default profile needs to be updated with sapadm user to allow the communication between the Simple Diagnostics Agent and the Managed System. | Add the following line to the profile DEFAULT.PFL: service/admin_users = sapadm Multiple users (e.g. daaadm, dazadm) must be separated by space. Note: can be automated by OS scripts |
| Check if an SLDR is needed | As prerequisites, you need to choose, according to your landscape, if an SLDR is required see Preparing System Landscape Data Router page. |
| Implement SAP Note for the License Management Information | Implement SAP Note 1977240 - Extension of the AS ABAP SLD Data Supplier (RZ70), so that the License Management information are reported into LMDB |
Configure ABAP Data Supplier (RZ70) to send the ABAP Technical System (BCSystem) Data Supplier information This Data Supplier can be setup to either send the payload directly to SAP Focused Run LMDB, or to the SLDR, and in addition the classical Solution Manager 7.x SLD | NW 750, SP0 / NW 740 SP13 and higher already contains the new UI. For NW ABAP < 740 SP13, Import SAP Note 2188401 with SNOTE and transport according to transport policy. The SAP note provides function module to create SM59 HTTP destination and assign it to RZ70. Enabling of HTTP in RZ70 is only supported in SAP_BASIS ≥ 700 SP4.
It is possible to call the function module remotely for SM59 creation and RZ70 assignment. Note: If you have enabled HTTP destination creation with the SAP Note 2188401: execute RZ70 without any specific options. |
Configure SAP Start Service Data Supplier Configure this service to send the payload of all instances:
| Run as <sid>adm: /usr/sap/<SID>/ASCS<InstNbr>/exe/sldreg -configure/usr/sap/<SID>/SYS/global/slddest.cfg -usekeyfile Specify the HTTP connect information: [User, Password, Host, Port, HTTP/HTTPS] Of the SAP Focused Run SLDR or SAP Solution Manager SLD. Note: SECUDIR must point to directory containing client PSE and credentials (for more information check the respective SAP Help). Restart the sapstartsrv: sapcontrol -nr <Central Instance Number> -function RestartService Note: The Service needs to be restarted for all instances of the system. Check logs and XML /usr/sap/<SID>/<Instance>/work/ and /usr/sap/<SID>/D*<Instance Number>/work/ if the dev_sldregk, dev_sldregs, dev_krnlreg and sapstartsrv_sld.xml are correctly generated Check HTTP response: Success. HTTP status code: 200. |
Create SDAGENT User User to authenticate RFC calls by the simple Diagnostics Agent for data collection | Create SDAGENT user with required roles as described in the Security Guide. Per FRUN 1.0 FP03, instead of working with the SDAGENT User, it is also possible to use Certificate Based Authentication. Information on how to configure Certificate Based Authentication between the Simple Diagnostics Agent and the ABAP System is provided in SAP Note 2607542. Also see section “Edit Configuration in Simple System Integration” below. |
| Check LMDB | Optional operation From the LMDB (Technical System view), check the last data changes from the data supplier. Check the Software / Product Instance and Software Component Version sections, to see what has been reported by the Data Supplier. |
| Implement SAP Note dedicated to S/4HANA Improvements | Optional operation Implement SAP Note 2382263. |
| Implement SAP Note dedicated to EarlyWatch Alert (EWA) | See Preparing FRUN Applications page. |
| Edit Configuration in Simple System Integration | FRUN 1.0 < FP03, enter values for the following parameters:
FRUN 1.0 >= FP03, when selection Communication Mode “RFC with Basic Authentication”, enter values for the following parameters:
FRUN 1.0 >= FP03, when selection Communication Mode “RFC via SNC with Certificate Based Authentication”, enter values for the following parameters:
Information on how to configure Certificate Based Authentication between the Simple Diagnostics Agent and the ABAP System is provided in SAP Note 2607542. FRUN 2.0 >= FP01, an option for adding, editing and deleting additional monitoring clients, in addition to the default monitoring client, has been added. This option can be used to specify dedicated monitoring clients for the FRUN supported use cases, if required. FRUN 2.0 >= FP02, there is an option for specifying a pre-defined logon group. |