WAS v8.5 > Reference > Sets
Process execution settings page
Overview
To change the process execution settings for a server process, from the dmgr console page for an application server, click...
-
Servers | Server Types | WebSphere application servers | server_name | Server Infrastructure | Java and process management \ Process execution
Process Priority
The operating system priority for the process. The administrative process that launches the server must have root operating system authority in order to honor this setting.
| Information | Value |
|---|---|
| Data type | Integer |
| Default | 20 |
UMASK
User mask under which the process runs (the file-mode permission mask).
The deployment manager and application servers must run with a 007 umask in order to support system management functions. Therefore, IBM recommends that we do not change the default value of this setting for the deployment manager or the controller.
| Information | Value |
|---|---|
| Data type | Integer |
| Default | 007 |
Run As User
User the process runs as. This user ID must be defined to the security system.
For the Application Server to transition to the user specified in this option, the user that launching the process must be a root user. This is a restriction of the operating system.
When we 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 deployed on the application server require an environment setting set to a specific value for the Run As User, either:
- Define the environment setting before you launch the server.
- For the $HOME value, grant write permission for the Run As User value in the operating system.
If we 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.
| Information | Value |
|---|---|
| Data type | String |
Run As Group
Specifies the group the process is a member of and runs as.
When we 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 deployed on the application server require an environment setting set to a specific value for the Run As Group, either:
- Define the environment setting before you launch the server.
- For the $HOME value, grant write permission for the Run As Group value in the operating system.
If we 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.
This field is ignored.
| Information | Value |
|---|---|
| Data type | String |
Run In Process Group
Process group for the process. A process group is a mechanism 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.
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.
| Information | Value |
|---|---|
| Data type | Integer |
| Default | 0, which indicates the process is not assigned to a specific process group. |
Related
Define application server processes
Related information:
WebSphere variables page