Overview of Parameters

icm/server_port_<xx>

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.

The parameter also defines the frequency of ping of requests to the application servers (see below).

Seconds

25

wdisp/info_ timeout

Timeout for retrieving configuration data in the application servers. If the Web Dispatcher receives no response within this time, it asks the next server.

The parameter also defines the timeout for the ping of requests to the application servers (see below).

Seconds

180

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.

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.

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?version=1.2

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. 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 the SAP Web Dispatcher finds the URL mapping info.

Path in the HTTP service tree of the application server (AS ABAP).

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/system_ <xx>

Used to configure the Web Dispatcher for multiple back-end systems.

For more information, see wdisp/system_<xx>

wdisp/server_ info_protocol

wdisp/group_ info_protocol

wdisp/url_ map_protocol

wdisp/ping_ protocol

Protocol that the SAP Web Dispatcher should use for communicating with the message server and the application servers for exchanging metadata (server list, logon groups, URL mapping) or for performing the ping request on the application server.

You can secure the conenction using HTTPS.

For more information, see Metadata Exchange Using SSL .

Protocol name, possible values: http or https

http

wdisp/enable_ j2ee_groups

Allow logon groups for AS Java.

Truth 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/ping_ abap_url

URL that the SAP Web Dispatcher uses for ping requests - for ABAP Servers, Java Servers and external systems.

The ping requests that can be configured with these parameters are used for the health check of the instances.

The specified request is sent periodically to each application server (that is, to each instance). If the specified request for a server does not respond positively within a defined time (HTTP status code 200 (OK)), this server is removed from the Web Dispatcher load balancing. You can configure the frequency with which a request is sent to each instance in parameter wdisp/auto_refresh (see above). The time allowed for receiving the response can be configured in parameter wdisp/info_timeout.

For more information, see SAP Web Dispatcher for Multiple Systems

URL path name

/sap/public/ icman/ping

wdisp/ping_ java_url

-

wdisp/ping_extsrv_url

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)

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 the SAP Web Dispatcher to an application server.

You do not normally need to change the default setting.

Number of connections

dependant on the size which is selected at bootstrap or the installation with SAPInst.

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 for the Web Dispatcher

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.

More information: Server Selection and Load Balancing Using the SAP Web Dispatcher

Load balancing strategy

Possible values:

weighted_round_robin

simple_weighted_round_robin

adaptive

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 the SAP Web Dispatcher as a URL Filter

wdisp/add_ xforwardedfor_ header

The parameter determines whether the 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 , the 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 the 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 the Web Dispatcher, the application server requires this information, to generate absolute URLs (it can get the 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 the 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 the 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

Truth variable ( true or false )

false

wdisp/redispatch_ foreign_sessions

If the value of this parameter is true , the 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 (AS Java, AS 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

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 .