WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

282 WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

For more information about Repository checkpoints service, refer to the IBM WebSphere

Application Server V8.5 Concepts, Planning, and Design Guide, SG24-8022-00.

7.5 Working with nodes in a Network Deployment environment

Managing nodes is a concept specific to a Network Deployment environment. Nodes are

managed by the deployment manager through a process known as a

node agent that resides

on each node. To manage a node in a Network Deployment environment, the node must be

defined, and the node agent on each WebSphere Application Server node must be started.

Nodes are created when you create a profile. Nodes are added to a cell through federation

(See 3.3.7, “Federating nodes to a cell” on page 83 for more details).

7.5.1 Starting and stopping nodes

A node consists of the node agent and the servers. There are several ways to start and stop a

node and node agent or to stop them individually. Before using any of these methods, be sure

to note whether it affects the entire node, including servers, or just the node agent.

In this section, we cover the following topics:

 Starting a node agent

 Starting a node on z/OS using the START command

 Stopping a node agent

 Stopping a node on z/OS using the STOP command

 Stopping a node (the node agent and servers)

 Restarting a node agent

Starting a node agent

When a node agent is stopped, the deployment manager has no way to communicate with it.

Therefore, the node agent cannot be started using the administrative console and has to be

started with the startNode command run from the profile node system.

startNode command

The syntax of the startNode command is:

startNode.bat(sh) [options]

The options are shown in Example 7-11.

Example 7-11 startNode command

Usage: startNode [options]

options: -nowait

-quiet

-logfile <filename>

-replacelog

-trace

-script [<script filename>] [-background]

-timeout <seconds>

-statusport <portnumber>

-profileName <profile>

-recovery

-help

Chapter 7. Administration of WebSphere processes 283

For information about the use of the startNode command, go to the following information

center website:

http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/topic/com.ibm.websphere.nd.multipla

tform.doc/ae/rxml_startnode.html

See Example 7-12 for use of the startNode command. Note that a user ID and password are

not required.

Example 7-12 startNode command example for a node agent: AIX operating system

/opt/IBM/WebSphere/AppServer85/profiles/AppSrv85_01/bin/startNode.sh

ADMU0116I: Tool information is being logged in file

/opt/IBM/WebSphere/AppServer85/profiles/AppSrv85_01/logs/nodeagent/startServer.log

ADMU0128I: Starting tool with the AppSrv85_01 profile

ADMU3100I: Reading configuration for server: nodeagent

ADMU3200I: Server launched. Waiting for initialization status.

ADMU3000I: Server nodeagent open for e-business; process id is 712746

Starting a node on z/OS using the START command

To start a node agent on z/OS using the START command, use the following format:

START nodeagent_procname,JOBNAME=server_shortname,

ENV=cell_shortname.node_shortname.server_shortname

For example:

START WPACRA,JOBNAME=WPAGNTA,ENV=WPCELL.WPNODEA.WPAGNTA

Stopping a node agent

To stop the node agent and leave the servers running, compete the following actions,

depending on your preferred method. You can use the administrative console or a command

prompt.

To stop a node from the administrative console:

1. In the administrative console, click System administration  Node agents.

2. Select the box beside the node agent for the server, and click Stop.

To stop a node using a command prompt:

1. Open a command window.

2. Enter the stopNode command.

stopNode command

The syntax of the stopNode command is:

stopNode.bat(sh) [options]

The options are shown in Example 7-13.

Example 7-13 The stopNode command

Usage: stopNode [options]

Note: After you stop the node agent, the deployment manager has no way to communicate

with the servers on that node. The servers might be up and running, but the administrative

console cannot determine their status.