(DI-2311) SAP Web Dispatcher

Owned by DVD ROBOT
Nov 16, 2023
3 min read

According to changes introduced to SAP Web Dispatcher as of version 781, it is no longer possible to establish an authenticated HTTP connection to Web Dispatcher instances via type G RFC destination. See SAP note 3277881 for more details about this limitation. Due to this limitation, it’s only supported to monitor the locally installed SAP Web Dispatcher that is running on the application server of the monitored SAP system.

Before adding a new system for SAP Web Dispatcher monitoring, you need to distinguish between the following supported monitoring scenarios for SAP Web Dispatcher.

Monitoring of the remote SAP Web Dispatcher system

The monitoring connects to the SAP Web Dispatcher through the configured HTTP connection to the external server (type G RFC destination) and collects the required data for the monitoring through the HTTP communication. For this reason, the prerequisite in this scenario is to have a configured valid HTTP destination as described in the section Configuration of HTTP Destination.

Monitoring of the local SAP Web Dispatcher running on the SAP system

The monitoring connects through the configured Internal or ABAP connection to the SAP system where the SAP Web Dispatcher is installed and running on the specific application server. The required data for the monitoring is collected through the preconfigured commands using the program wdispmon.

The prerequisite for this scenario is to have a configured valid Internal or ABAP connection (connecting to the specific application server where the SAP Web Dispatcher is up and running) and determine the full path of the instance profile file of the SAP Web Dispatcher (mostly generated with the name “sapwebdisp.pfl”).

Add a new system for SAP Web Dispatcher monitoring

Proceed as follows to add a new system for SAP Web Dispatcher monitoring:

  1. Start transaction /DVD/MON.

  2. In the application toolbar, click Add system (SHIFT+F1).

  3. Select the main system type SAP Web Dispatcher

  4. Click Confirm.

  5. The screen System for SAP Web Dispatcher appears.

  6. In the RFC Destination field, enter the valid destination name where only HTTP, Internal or ABAP connections are supported.

    1. If you entered an Internal or ABAP connection, you also need to enter the full name (including path) of the instance profile file for the SAP Web Dispatcher in the Instance profile field (for example, /usr/sap/sapwebdisp/sapwebdisp.pfl)

    2. According to the provided RFC destination, the monitoring automatically determines the specific monitoring scenario and displays/hides the non-relevant fields for this specific scenario.

  7. Click Check connection.

    1. If any error occurred, the RFC Destination or the name/path to the Instance profile file is not configured correctly.

    2. You can check and maintain the RFC Destination by clicking Maintain destination or by calling transaction SM59.

  8. The required information is retrieved directly from SAP Web Dispatcher and relevant fields prefilled automatically.

  9. Optional: You can change the System description

  10. Optional: You can change the System name

  11. Click Confirm.

  12. A screen appears with the auto-detected server for the SAP Web Dispatcher instance.

  13. Ensure that the Monitor flag is selected.

  14. Click Confirm.

  15. The system for SAP Web Dispatcher monitoring has been added.

  16. You can start the monitoring by clicking Start default monitoring in the application toolbar. This starts the collector job with the profile WDISP_5MIN for the added system.