icm/HTTP/j2ee_<xx>

Use

This parameter controls the ICM’s communication with the J2EE Engine.

If the ICM receives an HTTP request and a J2EE Engine is running on its instance, the ICM must check whether the request is intended for Java or for ABAP (a BSP Application). In the case of HTTPS the ICM decodes the request so that it can proceed with the check. If the request is to be sent to the J2EE Engine – the Java Dispatcher, you can specify the dispatch attributes in this.

<xx> stands for the number of the entry being specified. Several assignments between the URL prefix and the J2EE Engine, numbered in ascending order from 0, can be specified.

Prerequisites

This parameter only makes sense if the parameter rdisp/j2ee_start is also set. For more information see Profile Parameters for the J2EE Engine.

Properties

Work area

Internet Communication Manager

Unit

Character string

Standard value

Parameter not set

Dynamically changeable

No

Value Range and Syntax

The parameter has the following syntax:

icm/HTTP/j2ee_<xx> = PREFIX=<uri-prefix>, HOST=<host>, CONN=<Number of connections>, PORT=<port>

The table below shows the possible options.

Option

Value

Description

PREFIX

<uri-prefix>

All the HTTP-URLs beginning with this character string are checked whether they should be directed to the J2EE Engine.                   

HOST

<host>

Host on which the J2EE Engine is running. If the parameter is not defined, the localhost is accepted.

If SSL is to be forwarded to the J2EE Engine, the subject CN in the SSL server certificate of the J2EE Engine (name of the host on which the certificate is issued, for example, "help.sap.com") must be the same as this value.

CONN

<number_of_connections>

The number of network connections to the J2EE Engine can be defined with this parameter. You can configure either a fixed number of connections or an area (min-max). If an area is specified, the ICM opens min connections to the server. If necessary, new connections are opened until the maximum value max is reached. If you specify a fixed number (or if the minimum value is the same as the maximum value), these connections are already opened when the server starts.

PORT

<HTTP_port>

<port>: Port number or name of the HTTP list port of the J2EE server, to which the ICM should connect.

SPORT

<HTTPS_port>

<port>: Port number or name of the HTTPS list port of the J2EE server, to which the ICM should connect.

SSLENC

<n>

Specifies, whether the data stream is to be SSL encrypted again. The following values are possible:

0: Data will not be SSL-encrypted.

1: Data will be SSL-encrypted, if it arrived encrypted at the ICM (HTTPS).

2: Data will always be SSL-encrypted.

If nothing is specified (value 0), the data will not be encrypted. See also SAP Web Dispatcher and SSL.

TYPE

<t>

Specifies whether client authentication is to be used and which X.509 certificate the ICM is to use for it. The following values are permitted:

0: No certificate   

1: Default certificate  

2: Uses the certificate specified in parameter CRED.

CRED

<credentials_file>

Name of the PSE file used for the server authentication. This option is only relevant if <t>=2.

Examples

The following settings for example could be made for the prefix /.

icm/HTTP/j2ee_0 = PREFIX=/, HOST=localhost, CONN=0-10, PORT=21    

icm/HTTP/j2ee_0 = PREFIX=/, HOST=192.55.76.20, PORT=8080, CONN=50

icm/HTTP/j2ee_0 = PREFIX=/, CONN=0-10, PORT=50000,SPORT=50003, SSLENC=1,TYPE=1

icm/HTTP/j2ee_0 = PREFIX=/, CONN=0-10, PORT=50000,SPORT=50003,                    SSLENC=1,TYPE=2,CRED=SAPSSLC.pse

More Information

Note the following documentation:

Administration der J2EE Engine