Parameterization of the ICM and the ICM Server Cache

Use

This section explains the profile parameters relevant to the operation of the ICM and the ICM server cache.

You can display most of these parameters in the ICM Monitor and change some of them dynamically. To do this, on the initial screen choose Transaction SMICM Goto ® Parameters ® Display or Change. On the Change screen you can go directly to the RZ11 parameter documentation for the individual parameters.

You can find an example of the setting of the ICM parameter in the instance profile in Sample Profile for the ICM.

Integration

Most of the parameters are also valid for the SAP Web Dispatcher. Exceptions are parameters that control the SMTP communication, and parameters that control the communication with the backend (work process).For more information see Parameterization of the SAP Web Dispatcher

For information about parameters with the ending <xx> see Generic Profile Parameters with the Ending _<xx>.

Features

The parameters can be divided into the following groups:

ICM Parameters

exe/icman

rdisp/start_icman

icm/server_port_<xx>

icm/host_name_full

icm/min_threads

icm/max_threads

icm/min_spare_threads

icm/max_services

icm/req_queue_len

icm/listen_queue_len

icm/max_conn

icm/max_sockets

icm/accept_remote_trace_level

icm/ccms_monitoring  

icm/log_level

icm/cancel_strategy

icm/security_log

icm/authfile

HTTP Subhandler Parameters

These parameters are also valid for HTTPS, as the ICM SSL closes and processes the request in same way as with HTTP.The parameters are not valid for SMTP.

The parameters are also valid for the SAP Web Dispatcher, if HTTP or HTTPS is specified as the protocol for icm/server_port_<xx> (option PROT). See also SAP Web Dispatcher and SSL.

icm/HTTP/admin_<xx>

icm/HTTP/auth_<xx>

icm/HTTP/file_access_<xx>

icm/HTTP/logging_<xx>

icm/HTTP/redirect_<xx>

icm/HTTP/j2ee_<xx>

icm/HTTP/error_templ_path

icm/HTTP/max_request_size_KB

is/HTTP/show_detailed_errors

HTTPS Subhandler Parameters

icm/HTTPS/verify_client

ICM Server Cache Parameters

icm/HTTP/server_cache_<xx>

icm/HTTP/server_cache_<x>/max_entries

icm/HTTP/server_cache_<xx>/clear

icm/HTTP/server_cache_<xx>/expiration

icm/HTTP/server_cache_<xx>/max_name_len

icm/HTTP/server_cache_<xx>/max_ufo_entries

icm/HTTP/server_cache_<xx>/max_net_frag_size

icm/HTTP/server_cache_<xx>/size_MB

icm/HTTP/server_cache_<xx>/memory_size_MB

icm/HTTP/server_cache_<xx>/ufo_codelist

icm/HTTP/server_cache_<xx>/ufo_expiration

Memory Pipes Parameter

Memory Pipes

Timeout Handling Parameters

These parameters are used internally for optimizing the I/O throughput (network/MPI).

icm/keep_alive_timeout

icm/conn_timeout

icm/wp_mpi_available

icm/wp_roll_timeout

Work Process-Resources for ICM Requests

If an ICM is being processed in a work process, you will see an entry of type PLUGIN in the User Overview (SM04). The following profile parameters are available for configuring resources:

icm/<PROT>/context_quota

rdisp/http_check

rdisp/http_min_wait_dia_wp

The settings enable you to determine how many plug-in requests (HTTP, HTTPS, SMTP, etc.) can be processed at the same time in the application server.

See also:

Resources can also be managed for processing of RFC requests. See Configuration of System Resources for Parallel RFC.

Activities

Most of the profile parameters are preconfigured to allow the smooth operation of the ICM and the ICM server cache. Normally, you only have to set a few of the central parameters.

Example

In the section Example Profiles for the ICM you can see the possible parameter settings.