wdisp/system_<xx>
With this profile parameter you can configure multiple back-end systems for the SAP Web Dispatcher. One or more back-end systems can be configured (maximum: 1024 / default: 64). This profile parameter overrides the values of parameters rdisp/mshost and ms/server_port. It is no longer recommended that you use this profile parameter.
Structure:
|
Work area |
SAP Web Dispatcher |
|
Unit |
Character string |
|
Default value |
- |
|
Dynamically changeable |
Yes |
Syntax:
wdisp/system_<xx> = SID=<sap-sid>,
{
MSHOST=<ms-host>,
{MSPORT=<ms-http-port>, | MSSPORT=<ms-https-port>,}
[NR=<scs-sys-no>,] [SCSHOST=<scs-host>,]
[CLIENT=<target-client>,] |
XSSRV=<hana-xs-server-list>, |
[PINGURL=<ping-path>,]
EXTSRV=<external-server-list>,
[STICKY={true|false}]
[PROXY=<proxy-url>,] |
SILOC=file://<filename>,
}
{
SRCSRV=<source-services>,
SRCURL=<source-urls>,
SRCVHOST=<virtual-hosts>,
}
[SSL_ENCRYPT={0|1|2},]
[CONFIG_PROTOCOL={http|https},]
[STANDARD_COOKIE_FILTER={<filter-expression>|ON|OFF},]
[SSL_CLIENT_PSE=<filename of client PSE>,]
[SSL_IGNORE_HOST_MISMATCH={true|false},]
[SSL_CERTHOST=<hostname>,]
[RUNLEVEL={ stopped|running|internal},]
[CACHE_INFO_URL=<path> [, CACHE_INFO_POLL_INTERVAL=<interval in seconds>],]
Conditions of the Subparameters:
Profile parameter wdisp/system is configured using various subparameters. Not all subparameters can be combined with one another. The table below contains an overview of the combination options:
| Place for Meta Information | Mandatory Subparameter | Optional Subparameter |
|---|---|---|
| MSHOST |
|
|
| XSSRV |
|
|
| EXTSRV |
|
|
| SILOC |
|
|
Description of the Subparameters
The following subparameters can be configured:
| Subparameter | Description |
|---|---|
| SID | Three letter SAP system ID |
| MSHOST | Specifies the host name of the SAP Message Server. |
| MSPORT | Specifies the HTTP port of the SAP Message Server for MSHOST. |
| MSSPORT | Specifies the HTTPS port of the SAP Message Server for MSHOST. |
| XSSRV | Specifies the URL of one or more XS engine instances. |
| EXTSRV | Specifies the URL of one ore more external systems. |
| PROXY | Optionally specifies for EXTSRC a system that can be accessed only through a proxy server. |
| SILOC | Specifies the name of the configuration file containing the metadata of the application servers of the system. |
| NR | Optionally specifies the SAP system number of the Message Server for MSHOST. Required for the registration on SLD. |
| SCSHOST | Optionally specifies the host name of the SCS instance for MSHOST. Required for the registration on SLD. |
| CLIENT | Optionally adds the SAP client header to all requests for MSHOST. |
| SRCSRV | Optionally specifies the host/port combinations for MSPORT/XSSRV/EXTSRC/SILOC. |
| SRCURL | Specifies for MSPORT/XSSRV/EXTSRC/SILOC the possible URL prefixes in a list separated by semicolons. |
| SRCVHOST | Optionally specifies the host/port combinations for MSPORT/XSSRV/EXTSRC/SILOC. |
| SSL_ENCRYPT | Optionally specifies or MSPORT/XSSRV/EXTSRC/SILOC the SSL setting for systems connected separately. |
| CONFIG_PROTOCOL | Optionally specifies the protocol to use for MSHOST/XSSRV. |
| STANDARD_COOKIE_FILTER | Optionally specifies for MSPORT/XSSRV/EXTSRC/SILOC whether cookies from inbound requests are to be removed. STICKY is not supported together with STANDARD_COOKIE_FILTER. |
| STICKY | For EXTSRV as an option you can specify that requests from a client are always forwarded to the same application server for load balancing. STICKY is not supported together with STANDARD_COOKIE_FILTER. |
| PINGURL | For XSSRV as an option you can specify the URL that you want to use for pings instead of the standard URL or the URL specified in wdisp/abap_ping_url. |
| SSL_CLIENT_PSE | Specifies the name and path of the client certificate that has to be used for SSL connections to servers of this back-end system. If this subparameter is not set, the name of the PSE file is taken from the globally valid profile parameter wdisp/ssl_cred if this is set to wsidp/ssl_auth = 2. If you use this subparameter, you do not need to set the value of wdisp/ssl_auth to 2.
(For more information, see: 2066738 |
| SSL_IGNORE_HOST_MISMATCH | If this subparameter is set to TRUE, SAP Web Dispatcher ignores inconsistencies between the actual server host name and the host name in the server certificate for this back-end system. If this subparameter is not set, the value is taken from the globally valid profile parameter wdisp/ssl_ignore_host_mismatch.
(For more information, see: 2066738 |
| SSL_CERTHOST | Specifies the server host name for SSL connections for each back-end system. The subparameter overwrites the actual host name of the server for this back-end system. Use this subparameter only if the server certificate is issued to a host name that is not the actual host name of the server. If this subparameter is not set, the value is taken from the globally valid profile parameter wdisp/ssl_certhost.
(For more information, see: 2066738 |
| RUNLEVEL | With this subparameter access to a back-end system can be restricted. This subparameter cannot be dynamically changed.
Possible values: Running: No access restriction. Internal: Access for end users is denied and HTTP status code 503 "Service unavailable" is returned. Internal users, such as system administrators can continue to access the back-end system. Internal users are specified with profile parameter icm/internal_request_criteria. Stopped: No access. HTTP status code 503 "Service Unavailable" is returned to all requests. |
| CACHE_INFO_URL | Specifies the path to an HTTP application that decides whether the cache is invalidated. Periodic invalidation takes place only if this subparameter is set. Every CACHE_INFO_POLL_INTERVAL seconds a request is sent to CACHE_INFO_URL. This request must be responded to with a value (maximum 256 bytes). Each time this value changes, the cache for the respective back-end system is invalidated. |
| CACHE_INFO_POLL_INTERVALL | Specifies the interval for periodic cache invalidation in seconds. The default value is 60 seconds. Every CACHE_INFO_POLL_INTERVAL seconds a request is sent to CACHE_INFO_URL. This request must be responded to with a value (maximum 256 bytes). Each time this value changes, the cache for the respective back-end system is invalidated. |
