Profile Parameters for the SAP J2EE Engine
The following overview describes the profile parameter within the SAP J2EE Engine.
You can also find the parameters and documentation in Transaction RZ11.
|
Parameters |
Meaning |
Unit |
Default Value |
|
icm/HTTP/j2ee_<xx> |
You use this parameter to determine the ICM’s communication with the J2EE server. icm/HTTP/j2ee_<xx> = HOST=<host>, PORT=<port>, CONN=<Anzahl Verbindungen> Meaning: < xx> stands for the number of the entry to be specified. Several assignments between the URI prefix and the J2EE server, numbered in ascending order from 0, can be specified.<port> : Port number or name of the list port of the J2EE server to which the ICM should connect.<Number of connections> : The number of network connections to the J2EE server 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 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.
icm/HTTP/j2ee_0 = PREFIX=/, HOST=localhost, CONN=0-30, PORT=21 icm/HTTP/j2ee_0 = HOST=192.55.76.20, PORT=8080, CONN=50
This parameter only makes sense if the parameter rdisp/j2ee_start is also set. |
Character string |
- |
|
icm/dpj2ee |
If the system is not started using the SAP dispatcher "disp+work", but using the standalone dispatcher "dpj2ee" instead, the ICM must be informed about this using this parameter, and the value of the parameter must therefore set to True. If you try to start the standalone dispatcher although the parameter has the value FALSE, the standalone dispatcher dpj2ee ends immediately. |
Logical value |
FALSE |
|
rdisp/j2ee_error |
Number of incorrect attempts to start a J2EE server before the restart is deactivated. By dynamically switching using parameter rdisp/j2ee_start, you can reactivate the restart. |
Integer (number of attempts) |
10 |
|
rdisp/j2ee_start |
You can use this parameter to activate or deactivate starting the J2EE Engine. The start of the J2EE Engine is automatically deactivated if a specific number of attempts (rdisp/j2ee_error) to start the server failed. You can reactivate the start by dynamically changing this parameter to the value of 1. |
Logical value |
0 |
|
rdisp/j2ee_start_lazy |
If this parameter is set to 1, the following applies: If an SAP J2EE Engine should be started (parameter rdisp/j2ee_start ), it is not started until the ABAP runtime environment has been fully initialized. This avoids problems that are caused by a long initialization phase. If the parameter has the value 0 (default), then the SAP J2EE Engine can be started without waiting for the ABAP initialization. |
Logical value |
0 |
|
rdisp/j2ee_timeout |
Within this time span, the J2EE Engine must log on to the dispatcher. If not, it is assumed that the J2EE Engine had problems starting and it is started again. You can determine the number of incorrect start attempts using parameter rdisp/j2ee_error. If this number of start attempts failed, this deactivates the J2EE Engine from starting. By dynamically switching using parameter rdisp/j2ee_start, you can reactivate the restart. |
Seconds |
60 |
