Process execution settings

Specifies the operating system priority for the process. The administrative process that starts the server must have root operating system authority to accept this setting.

This setting is not available for managed WebSphere® Application Server Liberty servers. For information about managed Liberty servers, see the Modernized Runtime Extension for Java (MoRE) documentation.

Specifies the user mask under which the process runs (the file-mode permission mask).

Beginning with version 1.0.3.0, you can set a user mask for managed Liberty servers.

Note:

To support system management functions, the deployment manager and application servers must run with the stated UMASK default value.

Information	Value
Data type	Integer
Default	022 (for UNIX)
Default	007 (for z/OS)
Default	027 (beginning with 1.0.3.0 for managed Liberty servers)

You can change the default value of UMASK for the deployment manager and application servers to a more strict UMASK setting (027 for UNIX), but this change can have unintended consequences for stack products, add-ons, non-IBM products, and legacy scripts and processes.

If the process is running in a servant, you can either specify a different user mask setting in this field or you can define a new environment variable for the servant that changes this setting. The new environment variable is _BPX_BATCH_UMASK. You define this new environment variable by using the administrative console. To view the administrative console page, click Environment > WebSphere variables. To define the new variable, select the appropriate scope from the list of available options and then click New to create the name _BPX_BATCH_UMASK and set the wanted value.

Note: After defining and setting _BPX_BATCH_UMASK, you will need to restart the server to pick up the new UMASK setting.

Specifies the user that the process runs as. This user ID must be defined to the security system.

Beginning with version 1.0.3.0, you can specify the user that the process runs as for managed Liberty servers.

This field does not apply if you are running on a z/OS operating system. z/OS users must use RACF to associate a user to an address space. A process display shows the RACF associated user as the running user.

Avoid trouble: When you use the Run As User capability, environment settings are not automatically changed. By default, the application server receives the environment settings, including the $HOME and $USER values, for the user that started the process and not the Run As User value. If any applications that are deployed on the application server require an environment setting that is set to a specific value for the Run As User, you must either:

• Define the environment setting before you start the server.
• For the $HOME value, grant write permission for the Run As User value in the operating system.

If you are using the Run As User capability, it is not recommended that you rely on environment variables, but rather specify the values directly for the application.

This field is ignored if you are running Microsoft Windows operating systems because Windows user accounts are not managed by the Application Server.

For the IBM i operating system, extra steps are required to run as a user ID other than QEJBSVR. For more information, see the Security section of the WebSphere Application Server for iSeries online documentation.

Specifies the group that the process is a member of and runs as.

Beginning with version 1.0.3.0, you can specify the group that the process is a member of and runs as for managed Liberty servers.

This field does not apply if you are running on a z/OS operating system. z/OS users must use RACF to associate a group to an address space. A process display shows the RACF associated group as the running user.

• Note: If the user is a member of secondary groups, the server process does not have the user's access permissions to those groups by default. For the process to have those permissions, set this environment variable in the operating system before starting WebSphere Application Server: __JNI_PROCESS_INITGROUPS
• Avoid trouble: When you use the Run As Group capability, environment settings are not automatically changed. By default, the application server receives the environment settings, including the $HOME and $USER values, for the user that started the process and not the Run As Group value. If any applications that are deployed on the application server require an environment setting that is set to a specific value for the Run As Group, you must either:

  • Define the environment setting before you start the server.
  • For the $HOME value, grant write permission for the Run As Group value in the operating system.

  If you are using the Run As Group capability, it is not recommended that you rely on environment variables, but rather specify the values directly for the application.

If the runAsGroup value is specified, then that value is added to the secondary group list. If the runAsGroup value specified is not the runAsUser's primary group, the primary group is included in the secondary group list only if the user is defined as part of the group list in the group database, typically /etc/group.

This field is ignored.

Specifies a specific process group for the process. A process group is a mechanism that the operating system uses to logically associate multiple processes and operate on them as a single unit. Usually, the operating system uses this mechanism for signal distribution.

This setting is not available for managed WebSphere Application Server Liberty servers.

This field does not apply if you are running on a z/OS operating system. z/OS users must use RACF to associate a process group to an address space. A process display shows the RACF associated process group as the running user.

Specific operating systems might allow other operations to be performed on a process group. Refer to your operating system documentation for more information on the operations that can be performed on a process group.

This field is ignored.