Process definition settings

Use this page to configure a process definition. A process definition includes the command line information necessary to start or initialize a process.

For the WebSphere® Application Server and the WebSphere Application Server, Express® products, only the command-line information for starting or initializing a process applies.

To view this administrative console page, click Servers > Server Types > WebSphere application servers > server_name. Then, in the Server Infrastructure section, click Java and process management > Process definition.

[z/OS] On z/OS® you must then click Control, Servant, or Adjunct.

[z/OS] For z/OS, this page provides command-line information for starting, initializing, or stopping a process. Each of the commands for which information is provided can be used for the control process. Only the Start command and Start command arguments properties apply for the servant process. Specify the commands for the control process on one process definition panel and the commands for the servant process on another process definition panel. Do not specify the commands for the two different processes on the same panel.

Executable name

This command line information specifies the executable name that is invoked to start the process.

For example, if you are using a perl script as a generic server, enter the path to the perl.exe module in the Executable name field, and then enter the name of the perl script, along with any arguments, in the Executable arguments field.

[z/OS] This field is not available for the z/OS control process.

Table 1. Data type. The following table describes the data type for the Executable name setting.
Information	Value
Data type	String

Executable arguments

This command line information specifies the arguments that are passed to the executable when starting the process.

You can enter multiple arguments in this field, but they must be separated by carriage returns. Use the Enter key on your keyboard to create these carriage returns. The following example illustrates how a perl script application that requires two arguments should appear in this field:

perl_application.pl
arg1
arg2

[z/OS] This field is not available for the z/OS control process.

Table 2. Data type and units. The following table describes the data type and units for the Executable arguments setting.
Information	Value
Data type	String
Units	Command-line arguments

Start command (startCommand)

This command line information specifies the platform-specific command to launch the server process.

z/OS control process

Table 3. Data type, Format, and Example. The following table describes the data type, format, and example.
Information	Value
Data type	String
Format	START `control_JCL_procedure_name`
Example	START BBO6ACR

z/OS servant process

For the z/OS servant process, the value on the start command specifies the procedure name that workload manager (WLM) uses to start the servant process. WLM only uses this value if the WLM dynamic application environment feature is installed.

Table 4. Data type, Format, and Example. The following table describes the data type, format, and example.
Information	Value
Data type	String
Format	`servant_JCL_procedure_name`
Example	BBO6ASR

Start command arguments (startCommandArgs)

This command line information specifies any additional arguments required by the start command.

If you have two or more arguments that need to be passed for process definition settings, then you must specify the arguments on separate lines. For example, if you are specifying port 8089 and a configuration file (location and file name) as command arguments, you would specify:

<startCommandArgs>8089<startCommandArgs>
<startCommandArgs>/opt/payexpert/conf/PCPILogServer.properties<startCommandArgs>

In the administrative console, you specify this by entering each argument on a new line.

Note: Do not separate the command arguments with just a space.

z/OS control process

Table 5. Data type, Format, Example. The following table describes the data type, format, and example.
Information	Value
Data type	String
Format	JOBNAME=`server_short_name`, ENV=`cell_short_name`.`node_short_name`.`server_short_name`
Example	JOBNAME=BBOS001,ENV=SY1.SY1.BBOS001

z/OS servant process

Table 6. Data type, Format, Example. The following table describes the data type, format, and example.
Information	Value
Data type	String
Format	JOBNAME=`server_short_name`S, ENV=`cell_short_name`.`node_short_name`.`server_short_name`
Example	JOBNAME=BBOS001S,ENV=SY1.SY1.BBOS001

Avoid trouble: For z/OS, the server short name (JOBNAME) contains 7 characters by default, but you can lengthen the short name to 8 characters.gotcha

Stop command (stopCommand)

This command line information specifies the platform-specific command to stop the server process

[z/OS] For z/OS, if this field is left blank, then the MVS STOP command is used to stop the generic server.

Table 7. Data type, Format, Example. Specify two commands in the field, one for the Stop command, and one for the Immediate Stop (CANCEL) command.
Information	Value
Data type	String
Format	STOP `server_short_name`;CANCEL `server_short_name`
z/OS example	STOP BBOS001;CANCEL BBOS001

Stop command arguments (stopCommandArgs)

This command line information specifies any additional arguments required by the stop command.

Table 8. Data type, Format, Example. Specify arguments for the Stop command and the Immediate Stop (CANCEL) command.
Information	Value
Data type	String
Format	`stop command arg string`;`immediate stop command arg string`
z/OS example	;ARMRESTART In this example, Stop has no arguments. Immediate Stop has the argument ARMRESTART. A semicolon precedes ARMRESTART.

Terminate command (terminateCommand)

This command line information specifies the platform-specific command to terminate the server process.

Table 9. Data type, Format, Example. Specify arguments for the terminate command.
Information	Value
Data type	String
Format	FORCE `server_short_name`
z/OS example	FORCE BBOS001

Terminate command arguments (terminateCommandArgs)

This command line information specifies any additional arguments required by the terminate command.

The default is an empty string.

Table 10. Data type, Format, Example. Specify additional arguments for the terminate command.
Information	Value
Data type	String
Format	`terminate command arg string`
z/OS example	ARMRESTART

Working directory

Specifies the file system directory that the process uses as its current working directory. This setting only applies for IBM® i and distributed platforms. The process uses this directory to determine the locations of input and output files with relative path names.

[z/OS] This field does not display for the z/OS control process.

Avoid trouble: On z/OS, the working directory is always the UNIX System Services directory that is defined using the OMVS setting of the RACF® user profile for the user that starts the servant. Therefore, even if you specify a directory in this field, the UNIX System Services directory is used as the working directory. To provide compatibility between applications that run on a z/OS platform and on a distributed platform, set the UNIX System Services directory to the same value that you specify for the Working directory field on your distributed platform system.gotcha

Table 11. Data type. The following table describes the data type.
Information	Value
Data type	String

Executable target type

Specifies whether the executable target is a Java class or an executable JAR file.

Table 12. Data type. The following table describes the data type.
Information	Value
Data type	String

Executable target

Specifies the name of the executable target. If the target type is a Java class name, this field contains the main() method. If the target type is an executable JAR file, this field contains the name of that JAR file.

Table 13. Data type. The following table describes the data type.
Information	Value
Data type	String

File name: urun_rconfproc.html