SAP Web Dispatcher Threads Test

The SAP Web dispatcher performs load balancing, and passes requests to Internet Communication Managers (ICMs) on the connected application servers rather than to work processes. Besides the pool of worker threads, which process incoming requests, the following ICM components are also implemented as threads:

  • Thread Control: This thread accepts the incoming TCP/IP requests and creates (or wakes) a worker thread from the thread pool to process the request. From this point on, thread control initializes the connection info data.
  • Worker Threads: These threads handle connection requests and responses. A worker thread contains an I/O handler for the network input and output, diverse plug-ins for the various supported protocols (HTTP, SMTP,…), which are required to be able to decide when the sent packet is finished (depends on the protocol).
  • Watchdog: Usually, a worker thread waits for the response, regardless of whether the worker thread is a server or a client. If a timeout occurs, the watchdog takes on the task of waiting for the response. This makes the worker thread available for other requests. When the watchdog receives the response, it informs the thread control components, which then call a worker thread.
  • Signal Handler: This thread processes signals sent from the operating system or from another process (for example, the dispatcher).
  • Connection Info: This table contains information about the state of the connection, the memory pipes, and the plug-in data for every existing network connection.
  • Memory Pipes: These memory-based communication objects are used to transfer data between the ICM and work processes (AS ABAP), or between the ICM and Java server processes (AS Java). There are four pipes for every connection: One data pipe per request and response and one out-of-band (OOP) pipe. The OOB pipe is used for control data.
  • Internet Server Cache: The ICM contains another cache to enable a quick response to repeated requests. This cache is not shown in the graphic.

For each thread of the target SAP Web Dispatcher, this test reports the current state and the rate at which requests are processed by the threads.

Target of the test : A SAP Web Dispatcher

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each thread of the SAP Web Dispatcher being monitored.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed

Host

Specify the host for which the test is to be configured.

Port

The port number at which the specified host listens. The default is 2375.

WEB Dispatcher DIR

Specify the full path to the directory where the target SAP Web Dispatcher is installed.  Ensure that the location specified contains the sapwebdisp and wdispmon executables.

Profile File

Specify the full path to the profile file with which the target SAP Web Dispatcher was started. The default name of the profile is sapwebdisp.pfl.

Timeout

Specify the time for which the eG agent should wait for collecting the required metrics. By default, this is 60 seconds

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Requests

Indicates the rate at which requests were processed by this thread during the last measurement period.

Requests/sec

This measure is a good indicator of the throughput of the web dispatcher threads.

Status

Indicates the current state of this thread.

 

The values reported by this measure and their numeric equivalents are available in the table below:

Measure Value Numeric Value
Idle 0
Running 1

Note:

This measure reports the Measure Values listed in the table above while indicating the current state of this thread. However, in the graph of this measure, this measure is indicated using only the Numeric Values listed above.

The detailed diagnosis of this measure if enables lists the thread ID and the request type.