Parameterizing 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.

ICM Parameters

exe/icman

rdisp/start_icman

icm/plugin_<xx>

icm/server_port_<xx>

icm/host_name_full

icm/min_threads

icm/max_threads

icm/req_queue_len

icm/listen_queue_len

icm/max_conn

icm/max_sleep

icm/accept_remote_trace_level

icm/ccms_monitoring

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 HTTPSis specified as the protocol for icm/server_port_<xx> (option PROT). See also: SAP Web Dispatcher and SSL

icm/HTTP/file_access_<xx>

icm/HTTP/logging_<xx>

icm/HTTP/redirect_<xx>

icm/HTTP/j2ee_<xx>

icm/HTTP/error_templ_path

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>/size_MB

icm/HTTP/server_cache_<xx>/memory_size_MB

icm/HTTP/server_cache_<xx>/ufo_list

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

The profile parameters are also described and documented in the system (transaction RZ11).

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 same parameters are used to configure the available resources as are used for parallel RFCs (see Configuring System Resources for Parallel RFCs).

The number of plug in requests (HTTP, HTTPS, SMTP,...) that can be processed simultaneously in the application server, is determined by the number of configured dialog work processes less the number of dialog processes that must be kept free:

# Dialog WP - rdisp/rfc_min_wait_dia_wp