Restart a node

We can start a node using the startNode command. We can stop a node using the stopNode command. Restart a node is applicable only if your profile, also known as a node, is added to a WebSphere Application Server WAS ND domain or cell.

Before we can start and stop a node, we 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 ND environment. Before the environment can service requests, we must have the deployment manager and node started, and typically an HTTP server.

Tasks

• Start a node.

  Using one of these methods to start a node:

  • Use the startNode command.

    (iSeries) Use the startNode Qshell script to start a node from the Qshell command line of the IBM i server hosting the node.

    (Windows) 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, from a command dialog at the bin directory of the node profile:

    startNode
    

    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.

  Using one of these methods to stop a node:

  • Use the stopNode command:

    stopNode
    

    (iSeries) Use the stopNode Qshell script to stop a node from the Qshell command line of the IBM i server hosting the node.

    (Windows) 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, from a command dialog at the bin directory of the node profile:

    stopNode
    

  • Use the deployment manager administrative console.

    To use the deployment manager administrative console to stop a node:

    1. Start the deployment manager profile that manages the node.

    2. Start the administrative console for the deployment manager.

    3. Expand System Administration and click Node Agents.

    4. Select the check box for the node to stop.

    5. 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.

We have started and stopped a node.

What to do next

We can deploy applications, create a cluster, and generally administer the WAS ND environment.

Subtopics

• 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 WAS.
• 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 WAS.

(iSeries) Shutting down the QWAS85 subsystem for WAS

(iSeries) Restart the deployment manager

startNode command

stopNode command