!--a11y-->
The SAP Web Dispatcher Profile
Parameters 
The following overview describes the profile parameters of the SAP Web dispatcher.
The default values are selected so that you do not have to make any changes to these parameters. You determine the point of access to your SAP system using parameter icm/server_port_<xx>.
You can however use the parameters to adapt the configuration to specific system requirements.
See also: Example: Profile File of a SAP Web Dispatcher
Since the SAP Web dispatcher connects itself to the SAP message server and communicates with it via HTTP, the following parameters must be set correctly in the SAP Web dispatcher profile.
· rdisp/mshost: Host name of the machine on which the message server is running
· ms/http_port: The port on which the message server receives HTTP requests
The following table describes the parameters that you can use to configure the SAP Web dispatcher. You can also find the parameters and documentation in transaction RZ11.

You can also
use the parameters of the Internet Communication Manager (ICM) that do not
begin with
icm/<prot> (e.g.
icm/HTTP/...) for the SAP
Web Dispatcher. The most
important parameters are described in this documentation. For a full description of the ICM parameters see
Parameterization
of the ICM and the ICM Server Cache.
|
Parameters |
Meaning |
Unit |
Default Value |
||||||||||
|
wdisp/auto_refresh |
The period of time after which the route information tables of the SAP Web dispatcher (server tables, group tables and URL mapping tables) are periodically updated. |
Seconds |
120 |
||||||||||
|
wdisp/max_servers |
This parameter determines the maximum number of entries in the SAP Web dispatcher’s server table. |
Whole number (between 64 and 4096) |
128 |
||||||||||
|
wdisp/max_server_name_len |
This parameter specifies the maximum length of an entry in the SAP Web dispatcher’s server table, that is, the maximum length of an instance name (profile parameter rdisp/myname of the individual servers). |
Whole number (between 32 and 128) |
64 |
||||||||||
|
wdisp/max_server_groups |
This parameter determines the maximum number of entries in the SAP Web dispatcher’s group table. |
Whole number (between 32 and 4096) |
128 |
||||||||||
|
wdisp/max_server_group_name_len |
This parameter determines the maximum length of an entry in the SAP Web dispatcher’s group table. You maintain logon groups in transaction SMLG. |
Whole number (between 20 and 64) |
20 |
||||||||||
|
wdisp/max_url_map_entries |
This parameter determines the maximum number of entries in the SAP Web dispatcher’s URL mapping table. |
Whole number (between 100 and 10000) |
300 |
||||||||||
|
wdisp/max_url_map_path_len |
This parameter determines the maximum path length in the SAP Web dispatcher’s URL mapping table. |
Whole number (between 100 and 2048) |
256 |
||||||||||
|
wdisp/server_info_location |
Specifies from where the SAP Web dispatcher obtains information about the SAP Web Application Server, to which it can distribute the Web requests. The SAP Web Dispatcher gets its information from the Message Server. The parameter indicates the (relative) URL where in the Message Server this information is. |
Character string |
/msgserver/ text/logon |
||||||||||
|
wdisp/group_info_location |
Specifies from where the SAP Web dispatcher obtains information about the server groups, to which it can distribute the Web requests. The details are indicated in a URL (absolute or relative). Usually the SAP Web Dispatcher gets its group information from an application server (transaction SMLG). In this case you can specify the ICF service, where the groups are defined. If there is no message server or application server with ICF (ABAP) available, you can store this information in a file. In this case you can use this parameter to specify the file path by setting the parameter to file://<path>. |
Character string |
/sap/public/ icf_info/ icr_groups |
||||||||||
|
wdisp/url_map_location |
URL under which the SAP Web Dispatcher finds the URL mapping info. This is usually a path in the HTTP service hierarchy (transaction SICF). If there is no message server or application server with ICF (ABAP) available, you can store this information in a file. In this case you can use this parameter to specify the file path by setting the parameter to file://<path>. |
URL path name |
/sap/public/ icf_info/icr/ urlprefix |
||||||||||
|
wdisp/permission_table |
Absolute or relative path for URI permission table. Further profile parameters for configuring the URI permission table are described in section SAP Web Dispatcher as URL Filter. |
Character string (file path) |
|
||||||||||
|
Wdisp/HTTPS/dest_logon_group |
This parameter determines the logon group for load balancing requests at the SAP Web dispatcher. If a logon group is defined, the requests are passed to the servers in this group only. If no group is defined, the requests can be passed to all of the servers in the system. You maintain logon groups in transaction SMLG in the system. |
Logon group names |
|
||||||||||
|
wdisp/HTTPS/sticky_mask |
This parameter describes a bit mask for client IP addresses. The result of the bitwise AND operation on the client’s IP address and the sticky mask is used for load balancing of clients. This way you can summarize groups of client IP addresses. This functionality is required because large internet providers use several proxies (with different IP addresses) but the clients must be handled in the same way. This is imperative for applications for which the server keeps a status (stateful applications). |
Character string
|
255.255.240.0 The last 12 bits of the client IP address are no longer significant (are not distinguished). |
||||||||||
|
wdisp/HTTPS/ max_client_ip_entries |
This parameter specifies the maximum number of entries in the mapping table between the client IP address and the application server. The memory for the mapping table is allocated in the host’s shared memory.
|
Number of entries (integer value) |
50000 |
||||||||||
|
wdisp/HTTP/max_pooled_con |
This parameter determines the maximum number of HTTP connections in the connection pool from the SAP Web dispatcher to an SAP Web Application Server. You do not normally need to change the default setting. |
Number of connections |
32768 |
||||||||||
|
wdisp/HTTP/min_pooled_con |
Minimum number of HTTP connections that are kept in the SAP Web dispatcher’s connection pool for each application server. This number of connections is kept before the first HTTP request is received. |
Number of connections |
2 |
||||||||||
|
wdisp/HTTPS/max_pooled_con |
This parameter is the same as wdisp/HTTP/max_pooled_con, though for HTTPS connections.
What is important here is the protocol used from the SAP Web dispatcher to the Web AS. See SAP Web Dispatcher and SSL.
You do not normally need to change the default setting. |
Number of connections |
32768 |
||||||||||
|
wdisp/HTTPS/min_pooled_con |
This parameter is the same as wdisp/HTTP/min_pooled_con, though for HTTPS connections.
What is important here is the protocol used from the SAP Web dispatcher to the Web AS. See SAP Web Dispatcher and SSL.
Since for each HTTP connection in the pool on the Web AS, a thread is blocked in the ICM, you should not change the default value of 0! |
Number of connections |
0 |
||||||||||
|
wdisp/ssl_encrypt |
This parameter determines how the SAP Web dispatcher handles inbound HTTP(S) requests. The following values are possible: 0: Forward the request unencrypted. 1: Encrypt the request again with SSL, in case the request arrived via HTTPS protocol. 2: Always forward the request encrypted with SSL. The parameter corresponds to the SSLENC option of the ICM parameter icm/HTTP/j2ee_<xx> You can also configure the SAP Web dispatcher for End-to-End SSL, by specifying the protocol ROUTER when you define the icm/server_port_<xx> parameter. |
Whole number (0, 1 or 2) |
0 |
||||||||||
|
wdisp/ssl_auth |
This parameter determines which X.509 client certificate of the SAP Web dispatcher can be used with which application servers. The following values are possible: 0: No certificate 1: Default certificate 2: Use the certificate specified in the wdisp/ssl_cred parameter.
The parameter corresponds to the TYPE option of the ICM parameter icm/HTTP/j2ee_<xx> |
Whole number (0, 1 or 2) |
0 |
||||||||||
|
wdisp/ssl_cred |
Name of the PSE file used for the server authentication. This option is only relevant if wdisp/ssl_auth =2.
The parameter corresponds to the CRED option of the ICM parameter icm/HTTP/j2ee_<xx> |
File name/path name (corresponds to the operating system convention) |
|
||||||||||
|
wdisp/ssl_certhost |
This parameter is only relevant if you have configured the communication with certificates (wdisp/ssl_auth). If wdisp/ssl_certhost is not defined, for each application server a server certificate must be set up on the relevant host. In this parameter you can specify a host on which the server certificate is issued. Then you do not have to provide a certificate for each application server.
Your server certificate is issued on the name "www.sap.com". You activate this certificate for all application servers in transaction STRUST. You also set the value of wdisp/ssl_certhost to www.sap.com. If this parameter is not set, the host names on the message server (transaction SMLG) and the names the certificates are issued with must be the same. |
Host name |
|
||||||||||
|
wdisp/load_balancing_strategy |
Load balancing strategy of the SAP Web dispatcher, see Server Selection and Load Balancing Using the SAP Web Dispatcher |
Load balancing strategy Possible values: weighted_round_robin simple_weighted_round_robin |
weighted_round_robin
|

When you set the maximum values, note that unnecessarily large values can increase the SAP Web dispatcher’s memory consumption.
You can find a rule of thumb for memory consumption in SAP Web Dispatcher.
You can find an example of a profile file in Example: Profile File of a SAP Web Dispatcher.
Minimal Configuration for the SAP Web Dispatcher describes a minimal configuration for the SAP Web dispatcher.
