dmgr settings
Use this page to stop the deployment manager, and to link to other pages that we can use to define additional properties for the deployment manager. A deployment manager provides a single, central point of administrative control for all of the elements in the WAS distributed cell. To view this console page, click System administration > Deployment manager.
Name
Logical name for the deployment manager. The name must be unique within the cell.
| Information | Value |
|---|---|
| Data type | String |
(zos) Short name
Short name of the deployment manager server.
The server short name must be unique within a cell. The short name identifies the server to the native facilities of the operating system, such as workload manager (WLM), Automatic Restart Manager, System Authorization Facility (SAF) (for example, Resource Access Control Facility (RACF )), started task control, and others.
The name can be 1-8 alphanumeric or national language characters and cannot start with a numeric.
The system assigns a cell-unique, default short name.
Avoid trouble: If we change a 7-character deployment manager short name to an 8-character short name, you must update the start command arguments for the servant to use the new 8-character short name. See Converting a 7-character server short name to 8 characters.gotcha
| Information | Value |
|---|---|
| Data type | String |
(zos) Unique ID
Unique ID of this deployment manager server.
The unique ID property is read only. The system automatically generates the value.
| Information | Value |
|---|---|
| Data type | String |
(zos) Run in 64 bit JVM mode
Whether to run the deployment manager in 64-bit addressing mode to obtain more than the virtual memory that is available to the deployment manager when the deployment manager runs in 31-bit addressing mode, which is 2 gigabytes (GB).
Deprecated feature: You should eventually convert all of your servers to run in 64-bit addressing mode because support for running servers in 31-bit addressing mode is deprecated.depfeat
| Information | Value |
|---|---|
| Default | true (checked) |
Start components as needed
Select this property if we want the server components started as they are needed for applications that run on this server.
When this property is not selected, all of the server components are started during the startup process. Therefore, selecting this property usually results in improved startup time because fewer components are started during the startup process.
Avoid trouble: If we are running other WebSphere products on top of the this product, make sure that those other products support this functionality before you select this property.gotcha
Process ID
Specifies a string identifying process.
| Information | Value |
|---|---|
| Data type | String |
| Default | None |
Cell name
Name of the cell for the deployment manager. The default is the name of the host computer on which the deployment manager is installed with Cell## appended, where ## is a two-digit number.
| Information | Value |
|---|---|
| Data type | String |
| Default | hostCell01 |
Node name
Name of the node for the deployment manager. The default is the name of the host computer on which the deployment manager is installed with CellManager## appended, where ## is a two-digit number.
| Information | Value |
|---|---|
| Data type | String |
| Default | hostCellManager01 |
State
Indicates the state of the deployment manager. The state is Started when the deployment manager is running and Stopped when the deployment manager is not running.
| Information | Value |
|---|---|
| Data type | String |
| Default | Started |
Related concepts
(zos) Switching between 64 and 31 bit modes
Related tasks
(zos) Tune storage
(zos) Converting a 7-character server short name to 8 characters
Related information: