FW: J2EE Addin parameters missing in the profile, j2ee no longer starts

J2EE Addin parameters missing in the profile, j2ee no longer starts
Symptom
The profile parameters that you create when installing the J2EE engine are lost.
You can no longer start the J2EE engine.
Other terms
RZ10, profile maintenance
Reason and Prerequisites
In the standard J2EE installation, additional profile parameters are only saved in the operating system files. The parameters do not exist in the TPFHT and TPFET tables. The online profile maintenance (Transaction RZ10 and Transaction RZ11) edits tables TPFHT and TPFET, and generates a copy of the parameters in the operating system files when you activate the profile for the first time. The operating system files are then interpreted when you start the SAP System, and the resources are created in the defined size. During the activation in Transaction RZ10, the old operating system files are protected from being overwritten ('*.BAK') so that you can restore the previous version if necessary.
Solution
You must maintain the J2EE parameters in Transaction RZ10. You can retrieve the parameters that are generated automatically from the backup copy of the operating system file. You can display the saved file with Transaction AL11 or with a suitable editor on operating system level.

COMPARE:
------------
Use the comparison function in Transaction RZ10 to identify parameters that are inconsistent between the operating system file and the online tables. You can activate the function in the 'Profile' menu:

'Profile -> Comparisons -> Profile in database -> Against active profile'

IMPORT:
------------
Use the import function to import the parameters of the operating system files into the online tables. You can activate the import in the 'Profile' menu in Transaction RZ10:

'Profile -> Import'

Refer to the online documentation for more information.


For J2EE Engine 6.30/6.40, you must maintain the following parameters in the instance profile:

exe/j2ee = $(DIR_INSTANCE)/j2ee/os_libs/jcontrol.exe
rdisp/j2ee_start_control = 1
rdisp/j2ee_start = 1
rdisp/j2ee_timeout = 600
rdisp/frfc_fallback = on
jstartup/trimming_properties = off
jstartup/protocol = on
exe/jlaunch = $(DIR_INSTANCE)/j2ee/os_libs/jlaunch.exe
jstartup/instance_properties = $(INSTANCE_PROPERTIES);$(SDM_PROPERTIES)
ms/server_port_0 = PROT=HTTP, PORT=81
INSTANCE_PROPERTIES = $(DIR_INSTANCE)/j2ee/cluster/instance.properties SDM_PROPERTIES = $(DIR_INSTANCE)/SDM/program/config/sdm_jstartup.properties
icm/HTTP/j2ee_0 = PREFIX=/,HOST=,CONN=0-500,PORT=


For NetWeaver 2004s
the following parameters must be maintained in the instance profile:

jstartup/trimming_properties = off
jstartup/vm/home =
jstartup/max_caches = 500
jstartup/release = 700
jstartup/instance_properties = $(jstartup/j2ee_properties);$(jstartup/sdm_properties) //path separator is OS dependent
j2ee/dbdriver = // path separator is OS dependent
j2ee/instance_id =
jstartup/protocol = on
rdisp/j2ee_start_control = 1
rdisp/j2ee_start = 1
rdisp/j2ee_libpath = $(DIR_EXECUTABLE)
exe/j2ee = $(DIR_EXECUTABLE)/jcontrol$(FT_EXE)
rdisp/j2ee_timeout = 600
rdisp/frfc_fallback = on
icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=5$$00
icm/server_port_0 = PROT=HTTP,PORT=80$$


Note that the above example applies to Windows platforms and the ".exe" extension must be removed for other platforms.