Sample Profile for the ICM
The following section specifies a few sample profiles of the SAP Web Application Server. It displays only those parts that are relevant for the ICM and the ICM server cache.
You can transfer the following parameter values directly into the instance profile of a SAP Wen Application Server.
Application Server with HTTP, HTTPS and SMTP Access
If you want to configure the SAP Web Application Server for HTTP, HTTPS and SMTP, add (for example), the following lines to your instance profile.
|
# Port Definition icm/server_port_0 = PROT=HTTP, PORT=1080 icm/server_port_1 = PROT=HTTPS, PORT=1443 icm/server_port_2 = PROT=SMTP, PORT=1025
# Parameter Values for SSL Support sec/libsapsecu = $(DIR_EXECUTABLE)/libsapcrypto.so ssl/ssl_lib = $(DIR_EXECUTABLE)/libsapcrypto.so |
See also:
icm/server_port_<xx>Application Server with an Anticipated Small Load
If the anticipated load for the ICM is low, you can keep the number of threads small.
|
# Number of usable threads icm/min_threads = 10 icm/max_threads = 10 |
See also:
icm/min_threads icm/max_threadsApplication Server with a High Expected Load
If you anticipate too much load for your SAP Web Application Server, you can set the following parameters to large values.
|
# Number of usable threads icm/min_threads = 50 icm/max_threads = 100 # Increase the size of the MPI memory area mpi/total_size_MB = 80 # Number of maximum connections, length of the wait queue icm/max_conn = 1000 icm/req_queue_len = 250 |
See also:
Memory Pipes icm/max_conn icm/req_queue_lenBinding Ports Lower Than 1024 on UNIX
If you want to bind ports less than 1024 on UNIX, you can use the external additional program icmbnd. For more information, see
Binding Ports Lower Than 1024 on UNIX.|
# Use default ports # icmbnd must have superuser authorizations: # "chown root icmbnd" and "chmod 4755 icmbnd icm/server_port_0 = PROT=HTTP, PORT=80, EXTBIND=1 icm/server_port_1 = PROT=HTTPS, PORT=443, EXTBIND=1 icm/server_port_2 = PROT=SMTP, PORT=25, EXTBIND=1 |
See also:
icm/server_port_<xx>Activating the HTTP Logfile
Working with an HTTP logfile is described in
Logging in the ICM. In the following example, the file is rewritten every month.|
# HTTP logfile: The file is rewritten when the file size is 4MB and # at the start of each new month icm/HTTP/logging_0 = PREFIX=/, LOGFILE=access_log, MAXSIZEKB=4000, SWITCHTF=month, FILEWRAP=on |
See also:
icm/HTTP/logging_<xx>Activating the SAP J2EE Application Server
The SAP J2EE Application Server is integrated into SAP Web Application Server Release 6.20, although it is not started automatically. In the following example, the parameters are set so that the J2EE server is started automatically. For more information, see
Integration of the SAP J2EE Application Server.|
# J2EE server should be automatically started by the dispatcher rdisp/j2ee_start = 1 # J2EE server is running on the local host with port 33000, # maximum 20 parallel connections icm/HTTP/j2ee_0 = PREFIX=/, HOST=localhost, PORT=33000, CONN=0-20 |
See also:
icm/HTTP/j2ee_<xx>