Show TOC

Procedure documentationStarting the SAP Web Dispatcher with the Bootstrap Option Locate this document in the navigation structure

 

The bootstrap option is used to start the SAP Web Dispatcher without the profile file. This file is then created automatically.

Prerequisites

sapwebdisp -bootstrap must be run with the user ID that

  • Has write authorization in the current working directory

  • Is the same user ID the Web Dispatcher will also be later run with

If you call sapwebdisp -bootstrap in a directory below /usr/sap/<SID>/, you need <SID>adm authorizations, whereby <SID> is the SAP system that the SAP Web Dispatcher is used for.

Procedure

  1. In the command field enter

    sapwebdisp -bootstrap

  2. Enter message server details required by the bootstrap to create the profile. Before the profile is created, the message server details are checked. If necessary you can correct the data.

    Example Example

    In this example the system that the Web Dispatcher is to be used for is called SAP; the host on which the Message Server (central instance or (A)SCS instance) is run, is called scshost. The HTTP port of the Message Server is 8081. The Web Dispatcher is to receive requests on HTTP port 8888, and is to be assigned instance number 22. (Bear in mind that an instance number can be assigned on a host once only.)

    Host Name of Message Server (rdisp/mshost): scshost

    HTTP Port of Message Server (ms/http_port): 8082

    Checking connection to message server...

    ERROR: No data from msg_server received -

    Please check that 8082 is the HTTP port and not the native message server port

    Do you want to continue with these settings? n

    Host Name of Message Server (rdisp/mshost): scshost

    HTTP Port of Message Server (ms/http_port): 8081

    Checking connection to message server...OK

    In this example an incorrect HTTP port of the message server was entered and then corrected.

    End of the example.
  3. Specify the instance number and the port of the Web Dispatcher, and also the scenario in which the Web Dispatcher is to run: with a small (s), medium (m) (default), or a large (l) system. The parameters are preconfigured accordingly. The number of sockets in the system is also checked.

    Example Example

    Unique Instance Number for SAP Web Dispatcher (SAPSYSTEM):22

    HTTP Port Number for SAP Web Dispatcher: 8888

    Create configuration for s(mall), m(edium), l(arge) system (default: medium): l

    WARNING: Maximum number of sockets supported on this system: 1021

    Please check the operating system configuration

    Here the system is warning you because the operating system only supports 1021 sockets and this is not enough for a large installation.

    End of the example.
  4. Unpack the files for the Web administration as described in Operation of the SAP Web Dispatcher Setting Up the Web Administration Interface.

Result

The bootstrap carries out the following steps:

  1. Generates the profile sapwebdisp.pfl (if it does not already exist)

  2. Creates a user for the Web administration in file icmauth.txt (if it does not already exist) and an eight character random password.

    Example Example

    The output might look like this:

    Profile "sapwebdisp.pfl" generated

    Authentication file "icmauth.txt" generated

    Web Administration user is "icmadm" with password "RdUAs27F"

    Restart sapwebdisp with profile: sapwebdisp.pfl

    sapwebdisp started with new pid 20435

    Web administration accessible with "http://scshost:8888/sap/wdisp/admin"

    End of the example.
  3. Starts the SAP Web Dispatcher with the generated profile

SAP Web Dispatcher is running.

You can now use the Web Administration Interface to monitor and manage the Web Dispatcher.

Parameter Settings Dependent on System Size

Depending on which system size you have chosen (s, m or l), different parameter values are written to the profile file. The table below contains these different values.

Setting According to System Size

Parameter

Small (s)

Medium (m)

Large (l)

icm/max_conn

100

500

16384

icm/max_sockets

1024

1024

16384

icm/req_queue_len

300

500

6000

icm/min_threads

5

10

100

icm/max_threads

15

50

250

mpi/total_size_MB

20

80

500

wdisp/HTTP/max_pooled_con and wdisp/HTTPS/max_pooled_con (see Parameter Overview

100

500

2000

More Information