note 741289 - profile parameters of the j2ee engine are lost

02.12.2010 of 3

SAP Note 741289 - Profile parameters of the J2EE Engineare lost

Note Language: English Version: 8 Validity: Valid Since 16.02.2006

Summary

SymptomThe profile parameters that you create when installing the J2EE Engineare lost.You can no longer start the J2EE Engine.

Other termsRZ10, profile maintenance

Reason and PrerequisitesIn the standard J2EE installation, additional profile parameters areonly saved in the operating system files. The parametersdo not exist in the TPFHT and TPFET tables. The online profile maintenance(transactions RZ10, RZ11) edits the TPFHT and TPFET tables,and generates a copy of theparameters in the operating system files when you activate the profile forthe first time. The operating system filesare then interpreted when you start the SAP system, and the resources arecreated in the size specified. The old operating system files areprotected from being overwritten during the activation in transaction RZ10('*.BAK'), so thatyou can restore the previous version if necessary.

SolutionYou must maintain the J2EE parameters in transaction RZ10. Youcan retrieve the parameters that are generated automatically from thebackup copy of the operatingsystem file. You can display the saved file using transactionAL11 or with a suitable editor on operatingsystem level.

COMPARE:------------Use the compare function RZ10 to identify parameters that are inconsistentbetweenthe operating system file and the onlinetables. You can activate the function in the 'profile' menu:

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

IMPORT:------------Use the import function to transfer parameters from the operating systemfiles 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 inthe instance profile:

02.12.2010 of 3


exe/j2ee = $(DIR_INSTANCE)/j2ee/os_libs/jcontrol.exerdisp/j2ee_start_control = 1rdisp/j2ee_start = 1rdisp/j2ee_timeout = 600rdisp/frfc_fallback = onjstartup/trimming_properties = offjstartup/vm/home = <path to the JDK directory>jstartup/protocol = onexe/jlaunch = $(DIR_INSTANCE)/j2ee/os_libs/jlaunch.exejstartup/instance_properties = $(INSTANCE_PROPERTIES);$(SDM_PROPERTIES)ms/server_port_0 = PROT=HTTP, PORT=81<InstNo>INSTANCE_PROPERTIES = $(DIR_INSTANCE)/j2ee/cluster/instance.propertiesSDM_PROPERTIES = $(DIR_INSTANCE)/SDM/program/config/sdm_jstartup.propertiesicm/HTTP/j2ee_0 =PREFIX=/,HOST=<j2ee_host>,CONN=0-500,PORT=<j2ee_http_port>

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

jstartup/trimming_properties = offjstartup/vm/home = <path to the JDK directory>jstartup/max_caches = 500jstartup/release = 700jstartup/instance_properties =$(jstartup/j2ee_properties);$(jstartup/sdm_properties) //path separator isOS dependentj2ee/dbdriver = <path to JDBC driver jar files> // path separator is OSdependentj2ee/instance_id = <instance id>jstartup/protocol = onrdisp/j2ee_start_control = 1rdisp/j2ee_start = 1rdisp/j2ee_libpath = $(DIR_EXECUTABLE)exe/j2ee = $(DIR_EXECUTABLE)/jcontrol$(FT_EXE)rdisp/j2ee_timeout = 600rdisp/frfc_fallback = onicm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=5$$00icm/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.

Header Data

Release Status: Released for CustomerReleased on: 22.01.2007 08:41:33Master Language: GermanPriority: Recommendations/additional infoCategory: CustomizingPrimary Component: BC-CCM-CNF-PFL Profile Maintenance

Secondary Components:

02.12.2010 of 3


BC-INS Installation Tools

BC-JAS-COR Enterprise Runtime, Core J2EEFramework

The Note is release-independent

note 741289 - profile parameters of the j2ee engine are lost

Documents