Node agent server settings
Use this page to view information about and to configure a node agent. A node agent coordinates administrative requests and event notifications among servers on a machine. A node agent is the running server that represents a node in a WAS Network Deployment environment. To view this console page, click System administration > Node agents > node_agent.
A node agent must be started on each node for the deployment manager node to collect and control servers configured on that node. If we use configuration synchronization support, a node agent coordinates with the deployment manager server to synchronize the configuration data of the node with the master copy that the deployment manager manages.
We must initially start a node agent outside the console. For information on how to initially start a node agent, see the addNode command and the startNode command.
The Runtime tab displays only when a node agent runs.
Name
Logical name for the node agent server.
| Information | Value |
|---|---|
| Data type | String |
Node
Name of the node for the node agent server.
| Information | Value |
|---|---|
| Data type | String |
(zos) Short name
Short name of the node agent 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.
(zos) Unique ID
Unique ID of this node agent server.
The unique ID property is read only. The system automatically generates the value.
(zos) Run in 64 bit JVM mode
Whether to run the node agent in 64-bit addressing mode to obtain more than the virtual memory that is available to the node agent when the node agent 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 the process.
| Information | Value |
|---|---|
| Data type | String |
Cell name
Name of the cell for the node agent server.
| Information | Value |
|---|---|
| Data type | String |
| Default | hostNetwork |
Node name
Name of the node for the node agent server.
| Information | Value |
|---|---|
| Data type | String |
State
Indicates whether the node agent server is started or stopped.
| Information | Value |
|---|---|
| Data type | String |
| Default | Started |
Current heap size
Indicates the current heap size that the server JVM uses, in megabytes.
Maximum heap size
Indicates the maximum heap size that the server JVM can use, in megabytes.
Related concepts
(zos) Switching between 64 and 31 bit modes
Related tasks
(zos) Tune storage