Show TOC

Background documentationConnection Pooling Locate this document in the navigation structure

 

Normally, connection pooling in the SAP Web dispatcher can only be used for keep-alive connections from the browser.

If the browser does open a new network connection to the Web dispatcher, the Web dispatcher also opens a new network connection to the backend system.

In high workload scenarios, in particular with (re-)encryption (see SAP Web Dispatcher and SSL), system performance can be improved by using connection pooling in the Web dispatcher for new client connections too.

Parameterization

To activate connection pooling for new browser connections, set the profile parameter wdisp/HTTP/use_pool_for_new_conn=1 in the SAP Web dispatcher profile.

Configure the keep-alive timeout of the back end system (ICM or J2EE Engine) to a greater value than the keep-alive timeout of the Web dispatcher: the difference should be at least 20 seconds.

Note Note

This configuration of the keep-alive timeout values is necessary to ensure that the back end server never closes a keep-alive connection while the Web dispatcher is sending data.

End of the note.

Example

For example, you can set the following keep-alive timeout values:

  • In the Web Dispatcher Profile: icm/server_port_0 = PROT=HTTP,PORT=...,TIMEOUT=30,PROCTIMEOUT=...

  • If you are using a pure NW AS Java, in the J2EE Engine set: KeepAliveTimeout = 60

  • If you are using a NW AS ABAP or a combined ABAP/Java system, in the ICM profile set: icm/server_port_0 = PROT=HTTP,PORT=...,TIMEOUT=30,PROCTIMEOUT=...

More Information

You can find a description of the timeout parameters of ICM / Web dispatcher in Timeout Options for ICM the Web Dispatcher.