Configuration of the Java Startup and Control Framework 

Purpose

Use this process when you want to tune some specific features in the Java startup and control framework. Typically, you will not need to configure the framework.

Process Flow

The Java startup and control framework can be configured by using program arguments and by modifying the properties in some of the configuration files.

Program Arguments

The program arguments are used by JControl and by the JLaunch processes. For more information, see Program Arguments.

Configuration Files

The Java startup and control framework uses the following configuration files:

●     The start profile (/usr/sap/<SID>/SYS/profile/START_<instance name>_<hostname>) – for a Java-only installation, this file contains the invocation of the JControl program. You should not edit or configure this file.

●     The instance profile (/usr/sap/<SID>/SYS/profile/<SID>_<instance name>_<hostname>) – this file contains settings that apply to the instance as a whole. For a Java-only installation, the file can be edited with any text editor (beware that the file must have an empty line at the end.); in double-stack systems, transaction RZ10 is used to maintain the instance profiles. (The RZ10 transaction has known problems with long lines. For more information, see SAP Notes 579190 and 681188. For double-stack systems, see also SAP Note 741289.)

The instance profile contains parameters for a variety of files. The parameters whose names start with jstartup are the ones used by JControl and JLaunch. The initial configuration of these parameters is created by SAPInst and these settings allow the J2EE Engine to be started. For more information about the instance profile parameters, see SAP Profile Parameters.

●     Other configurations – when you want to change the cluster setup (to add or remove cluster nodes) or to change the configuration of the nodes and the Java parameters, to specify debug mode, and so on, use the J2EE Engine Config Tool. The configuration changes are stored in the database (and they appear in the instance properties on the next restart).