Start and stop a node
We can start a node using the startNode command. We can stop a node using the stopNode command. Starting and stopping a node is applicable only if the profile, also known as a node, is added to a WAS WebSphere Application Server Network Deployment domain or cell.
Before we can start and stop a node, you must federate the node into a cell.
Start the deployment manager and add the node as a managed node of the deployment manager. Adding the managed node federates the node.
Start or stop a node as need in administering the WAS Network Deployment environment. Before the environment can service requests, you must have the deployment manager and node started, and typically an HTTP server.
- Start a node.
Use one of these methods to start a node:
- Use the startNode command.
For example, from a command dialog at the bin directory of the node profile, run the serverStatus -all command. Suppose running the command shows that the node profile is named nodeagent. To start the node, run the following command from a command dialog at the bin directory of the node profile:
After starting the node, running the serverStatus -all command shows that the nodeagent status is STARTED.
- (iseries) Use the Submit Job (SBMJOB) CL command.
We can run this CL command from an IBM i command line:SBMJOB CMD(CALL PGM( product_library/QWASSTRSVR) PARM('-profilePath' 'profile_root' '-server' 'node agent')) JOB(server) JOBD(QWAS85/QWASJOBD) JOBQ(QWAS85/QWASJOBQ) USER(QEJBSVR) LANGID(*USRPRF) CNTRYID(*USRPRF) CCSID(*USRPRF) OUTQ(QWAS85/QWASOUTQ) ALWMLTTHD(*YES)where
- profile_root is the profile root of the node agent.
- node agent is the name of the node agent server to start.
- Stop a node.
Use one of these methods to stop a node:
- Use the stopNode command:
For example, from a command dialog at the bin directory of the node profile, run the serverStatus -all command. Suppose running the command shows that the node profile is named nodeagent. To stop the node, run the following command from a command dialog at the bin directory of the node profile:
- Use the dmgr console.
To use the dmgr console to stop a node:
- Start the dmgr profile that manages your node.
- Start the console for the deployment manager.
- Expand System Administration and click Node Agents.
- Select the check box for the node to stop.
- Click Stop.
- (iseries) Use the End Job (ENDJOB) CL command
To use the ENDJOB CL command to end an application server, enter this command on an IBM i command line:
ENDJOB JOB(jobNumber/QEJBSVR/jobName) OPTION(*CNTRLD) DELAY(delayTime)
where jobNumber is the job number, jobName is the name of the application server job for the deployment manager, and delayTime is the amount of time to wait for the job to end in seconds. Set the value to 600 seconds initially. To find out what the appropriate delayTime value is, see Shutting down the WAS subsystem.
You have started and stopped a node.
What to do next
We can deploy applications, create a cluster, and generally administer the WAS Network Deployment environment.
- Directory conventions
References in product information to app_server_root, profile_root, and other directories imply specific default directory locations. Become familiar with the conventions in use for WebSphere Application Server.
(iseries) Shutting down the QWAS85 subsystem for WebSphere Application Server
(iseries) Start and stop the deployment manager
startNode command stopNode command