-
Non-Product Related Assistance
Request for existing cases, user IDs, Portal navigation support and more
Request for existing cases, user IDs, Portal navigation support and more
This page explains how to prepare a SAP Web Dispatcher managed system for the execution of the Simple System Integration
Currently the following monitoring application are supported for SAP Web Dispatcher systems:
| Task | Actions |
|---|---|
| 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 Web Dispatcher 7.1 Version and higher | Install SAP Web Dispatcher from support.sap.com/swdc |
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 page Preparing System Landscape Data Router. |
Configure SAP Start Service Data Supplier Configure this service to send the payload of all instances:
| Run as <sid>adm /usr/sap/<SID>/W<InstNbr>/exe/sldreg -configure /usr/sap/<SID>/SYS/global/slddest.cfg -usekeyfile Specify the HTTP connect information: [User, Password, Host, Port, HTTP/HTTPS] 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 Check logs and XML /usr/sap/<SID>/W<Instance Number>/work/ if the dev_sldregk, dev_sldregs and sapstartsrv_sld.xml are correctly generated Check HTTP response: Success. HTTP status code: 200. Remark: in case of the embedded deployment of SAP Web Dispatcher please follow the steps described in 3115889 - SAP Web Dispatcher embedded deployment in an ASCS/SCS instance(opens in new tab) in order to send the required SLD payload of WebDispatcherInstanceKernel. |
| Restart Web dispatcher service to activate the settings and send the payload | As user <sid>adm to perform the following command: sapcontrol -nr <Web Dispatcher Instance No> -function RestartService Note: can be automated by OS script |
| Check the return code | Optional operation Check in the output for return code 200 from LMDB registration (in work directory dev_sldregk) |
| Check LMDB | Optional operation From the LMDB (Technical System view), check the latest Data changes from the Data supplier. The "Software" / "Product Instance" Section the Product Version reported by the SLD data supplier: for instance SAP WEB DISPATCHER 7.40 |
| Data Supplier Completeness Check | Prior SAP Focused Run release 5.0 FP02, the data supplier completeness check was only verifying the status of the ComputerSystem and not the relevant Web Dispatcher payloads. Starting with 5.0 FP02, the status of BCControlInstance and WebDispatcherInstanceKernel is being checked as well. A downport is available via 3628411 - Enhancement of SAP Web Dispatcher Data Supplier Completeness Checks(opens in new tab) SAP note for SAP Focused Run 5.0 SP0 - FP01. |