Program Arguments 

Definition

The program arguments of the Java startup and control framework are used by the JControl or JLaunch processes to configure or to tune some specific properties and options.

You cannot use these program arguments to configure the Java startup and control framework. These program arguments should be used for trace file analysis only.

Structure

The following is a list of the program arguments and their value resolution:

SAP Instance Profile

The SAP instance profile that contains all properties related to the J2EE instance. This file is normally created by SAPinst and contains the SAP instance properties, such as SAPSYSTEM (System number), SAPSYSTEMNAME (System ID), and so on.

●     Program Argument:           pf=<filename>

●     Internal Default Value:       jstartup.pfl for the local/developer mode.

Instance Property File

This file contains the parameters for all processes related to the J2EE instance.

●     Program Argument:           -file=<filename>

●     SAP Profile Property:        jstartup/instance_properties = <filename>

●     Internal Default Value:       instance.properties

Node Name for JLaunch

The name by which the corresponding node will be looked up in the instance property file. The node name specifies the process that should be started by JLaunch (for example, dispatcher, server<n>, and so on).

●     Program Argument:           -nodename=<nodename>

●     SAP Profile Property:        no profile value

●     Internal Default Value:       <program short name> (for example, jcontrol, jlaunch)

SAP Developer Trace File

The trace files for JControl and JLaunch. For more information, see Developer Trace and Log Files.

●     Program Argument:           -tracefile=<filename>

●     SAP Profile Property:        no profile value

●     Internal Default Value:       <home-directory>/dev_<Nodename>

Bootstrap Mode for JControl

This option allows switching on/off the bootstrapping processes launched during the startup of JControl.

●     Program Argument:           -bootstrap=[yes/no]

●     SAP Profile Property:        jstartup/bootstrap = [yes/no]

●     Internal Default Value:       [yes]

Parent Process ID (Windows Only)

This option specifies the PID of the parent process. On Windows platforms, there is no dependency between the parent process and the child process. This means that the child process does not terminate if the parent process dies. For this platform, SAP provides a functionality that emulates the UNIX fork mechanism. The child process gets the PID of the parent process by a program argument. The child process creates a thread that waits until the parent process dies. The child process terminates immediately, if it detects the end of the parent process.

In the SAP Web Application Server environment for example, the ABAP dispatcher starts JControl. JControl starts all J2EE processes by JLaunch. The ABAP dispatcher passes its PID to JControl and JControl passes its PID to the JLaunch processes. If the ABAP dispatcher terminates, JControl detects this and terminates also. The JLaunch processes detect the end of JControl and terminate. There will be no process left after the ABAP dispatcher crashes. The SAP Web Application Server is completely terminated.

●     Program Argument:           -parent=<PID of the parent process>

●     SAP Profile Property:        no property value.

●     Internal Default Value:       no internal default value.

Shared Memory Node ID for JLaunch

During the startup JControl creates a thread memory segment to share the internal administration data with all JLaunch processes. Each JLaunch process is represented by an index in a structure array. This index is called the Node ID and JControl passes this option as a program argument to the JLaunch processes. It is possible for the JLaunch processes to modify directly the information in the administration shared memory, for example the process state (STARTING, RUNNING…)

●     Program Argument:           -nodeId=<index in the shared memory administration>

●     SAP Profile Property:        no property value.

●     Internal Default Value:       [-1] (no relation to a shared memory segment)

Detailed Protocol for the Trace File/Detailed Protocol Output

This option switches on/off the detailed output of the JLaunch/JControl parameters and structures. The output is written in the developer trace file. This detailed information is used for tracing the whole program and the node options.

●     Program Argument:           -protocol=[on/off]

●     SAP Profile Property:        jstartup/protocol

●     Internal Default Value:       off

Process Mode for JLaunch

The process mode enables different internal default values for different purposes. For example, JLaunch has different internal default values for the standalone case and the case when it is started by JControl. JControl starts the JLaunch processes in the J2EE mode.

●     Program Argument:           -mode=[STANDALONE/J2EE]

●     SAP Profile Property:        no profile property value.

●     Internal Default Value:       [STANDALONE]

Java VM Output Destination for JLaunch

This option allows you to redirect the standard and the error output of the Java VM into a specified file.

●     Program Argument:           -jvmOutFile=<filename>

●     SAP Profile Property:        no profile property value.

●     Internal Default Value:       <home-directory>/jvm_<Node name>.out

Java VM Output Mode for JLaunch

This option specifies the mode for the redirection of the Java VM output. New means that JLaunch creates a new file for redirecting the Java VM output. Append means that JLaunch appends the output to an existing output file.

●     Program Argument:           -jvmOutMode=[new/append]

●     SAP Profile Property:        no profile property value.

●     Internal Default Value:       [new]

Native Output Destination for JLaunch

This option allows you to redirect the standard and error output of the native program JLaunch to a specified file.

●     Program Argument:           -locOutFile=<filename>

●     SAP Profile Property:        no profile property value.

●     Internal Default Value:       <home-directory>/dev_<Nodename>

Enable/Disable Debug Mode

This option allows you to switch on/off the debug mode for the node started by JLaunch.

●     Program Argument:           -debugMode=[yes/no]

●     SAP Profile Property:        jstartup/debug_mode

●     Internal Default Value:       no

Security Level for the J2EE Instance

This option sets the security level for JControl. This is an internal level that specifies how JControl reacts to commands issued by the Message Server. Value 3 means that no commands are allowed, value 0 means that all commands are allowed.

●     Program Argument:           -securityLevel=[0…3]

●     SAP Profile Property:        jstartup/security_level

●     Internal Default Value:       0

Start Mode for the JLaunch Processes (Windows Only)

This option describes how the JLaunch process is started on Windows NT. The value [process] means that JLaunch is started as a background program. The value [console] specifies that JLaunch is running in a separate command window.

●     Program Argument:           -start_mode=[process/console]

●     SAP Profile Property:        jstartup/start_mode

●     Internal Default Value:       process (Standalone)

Additional Environment Settings

This option allows you to add environment settings to JControl/JLaunch. The value has to be in the format: “envvar1=value”;”envvar2=value”;…

●     Program Argument:           environment=<list of environment variables>

●     SAP Profile Property:        jstartup/environment

●     Internal Default Value:       <empty>

Additional SAP Profile Properties

This option allows you to add properties to the SAP profile. The value has to be in the format: “parameter=value”.

●     Program Argument:           -sapparam:<profile parameter>=<value>

●     SAP Profile Property:        not applicable

●     Internal Default Value:       <empty>