The following table provides an overview of the profile parameters of the SAP Web Dispatcher.
Parameters that are used for the Internet Communication Manager (ICM) too are described under Profile Parameters for ICM and SAP Web Dispatcher.
Parameter |
Meaning |
Unit |
Default Value |
Starting point for requests, protocols, timeouts, and so on. You have to define this parameter. |
Character string |
- |
|
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 |
25 |
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) |
100 |
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 application servers, to which it can distribute the Web requests. SAP Web Dispatcher gets its information from the message server. The parameter indicates the (relative) URL where this information is in the message server. |
Character string |
/msgserver/text/logon?version=1.2 |
wdisp/group_info_location |
Specifies from where 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 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 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 SAP Web Dispatcher finds the URL mapping info. This is usually a path in the HTTP service hierarchy of the application server (transaction SICF). If there is no 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/server_info_protocol wdisp/group_info_protocol wdisp/url_map_protocol |
Protocol that SAP Web Dispatcher should use for communicating with the message server and the application servers for exchanging metadata (server list, logon groups, URL mapping). With HTTPS you can make this communication secure, see Metadata Exchange Using SSL. |
Protocol name, possible values: HTTP or HTTPS |
HTTP |
wdisp/enable_j2ee_groups |
Allow logon groups for AS Java (see Configuring Logon Groups on AS Java). |
Logical value |
FALSE |
wdisp/J2EE/group_info_location |
URL under which the Web Dispatcher receives the information about the logon groups in AS Java. |
URL path name |
/J2EE/icr_groups |
wdisp/J2EE/url_map_location |
URL under which the SAP Web Dispatcher finds the URL mapping info for AS Java. |
URL path name |
/J2EE/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/shm_attach_mode |
This parameter determines what should happen to the shared memories of the SAP Web Dispatcher. The possible values and their meaning are the values of the start option -shm_attach_mode of the Web Dispatcher. They are described in section Starting the SAP Web Dispatcher.
If the command line option is set explicitly to a different value when the Web Dispatcher is started, this value is definitive and the parameter value is overwritten. |
Whole number between 1 and 7 (bit mask) |
6 |
wdisp/HTTP/use_pool_for_new_conn |
Activates the connection pooling for new browser connections too If the parameter has the default value FALSE, the connection pooling is used only for keep-alive connections to the browser.
Note the requirements for activating the parameter in Connection Pooling. |
Truth value (TRUE,1, FALSE,0) |
FALSE |
wdisp/HTTP/max_pooled_con |
This parameter determines the maximum number of HTTP connections in the connection pool from SAP Web Dispatcher to an application server. You do not normally need to change the default setting. |
Number of connections |
Depends on the start option |
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/dest_logon_group |
See SSL Parameters |
||
wdisp/HTTPS/sticky_mask |
|||
wdisp/HTTPS/ max_client_ip_entries |
|||
wdisp/HTTPS/context_timeout |
|||
wdisp/HTTPS/max_pooled_con |
|||
wdisp/HTTPS/min_pooled_con |
|||
wdisp/ssl_encrypt |
|||
wdisp/ssl_auth |
|||
wdisp/ssl_cred |
|||
wdisp/ssl_certhost |
|||
wdisp/load_balancing_strategy |
Load balancing strategy of SAP Web Dispatcher, see Server Selection and Load Balancing Using SAP Web Dispatcher |
Load balancing strategy Possible values: weighted_round_robin simple_weighted_round_robin |
weighted_round_robin
|
wdisp/max_permitted_uri_len wdisp/permitted_uri_char_range wdisp/max_permission_table_size wdisp/max_permission_table_entry_size |
Parameters to configure SAP Web Dispatcher as a URL Filter |
|
2048 - 300 256 |
wdisp/add_xforwardedfor_header |
The parameter determines whether SAP Web Dispatcher includes the IP address of the client in the header field x-forwarded-for. If it does, the application on the application server can read the route that the request has taken. If the parameter has the value false, Web Dispatcher leaves the header field unchanged. |
Truth variable (true or false) |
false |
wdisp/add_client_protocol_header |
This parameter determines whether the protocol between the browser and Web Dispatcher (HTTP or HTTPS) is notified to the application server. This information is sent in the header field clientprotocol. If there is a change in protocol in Web Dispatcher, the application server requires this information, to generate absolute URLs (it can get Web Dispatcher host and port names from the header field Host). |
Truth variable (true or false) |
false |
wdisp/handle_webdisp_ap_header |
With this parameter Web Dispatcher notifies the application server of its ports (access points) for the different protocols in an HTTP header. In the application server the protocol can be switched without any manual configuration (for example, from HTTP to HTTPS), or a redirect can be programmed.
The header field set by Web Dispatcher has the syntax: x-sap-webdisp-ap: http=<port>, https=<port>, <protocolXYZ>=<port>
For example: x-sap-webdisp-ap: http=80,https=443 x-sap-webdisp-ap: http=80 |
Integer between 0 and 3; the values mean the following: 0: No action (old behavior) 1: Header field with it own access information (if this field exists, it is set) 2: Set header field if not already set. 3: Delete header field if it exists. |
0 |
wdisp/enable_sap_hostid |
If the value of this parameter is true, a server destination can be specified explicitly in the request URI using the form field sap-hostid, to directly override the load balancing. This is needed, for example, for debugging server nodes or for test purposes.
webdisp.wdf.sap.corp:4711/sap/public/icman/ping?sap-hostid=binmain_BIN_53
Since with this form field server load balancing can be bypassed (denial of service attacks), the default is this behavior is deactivated and must be explicitly activated using the parameter above. |
Truth variable (true or false) |
false |
wdisp/redispatch_foreign_sessions |
If the value of this parameter is true, Web Dispatcher tries to find an alternative server using stateless load balancing for failed stateful requests (incorrect session cookie or the target server cannot be accessed). This has the following advantages: The relevant backend (Java, ABAP) returns more meaningful error pages (such as "Please log on again"). The Web Dispatcher remains transparent for the user. A real session failover is made possible, if the relevant server backend is in the position to transfer external sessions
Web Dispatcher receives a request for a logon group "WEB", yet no server from the "WEB" group can be accessed. Web Dispatcher then tries to find an alternative server among all the accessible servers and forwards the request to it. You can override this behavior by setting the parameter to false. In this case Web Dispatcher returns an error. |
Truth variable (true or false) |
true |
wdisp/HTTP/esid_support wdisp/HTTP/jsessionid_tab_support wdisp/HTTP/max_session_tab_logon_groups wdisp/HTTP/max_session_tab_entries wdisp/HTTP/context_timeout |
The parameters below are used to configure the session dispatching. They are described in Parameter Settings for Session Dispatching. |
|
|