Start and stop the application server
There are several methods available for starting and stopping application servers. This topic describes how to start and stop application servers from the OS/400 command line and from the administrative console. For information on starting and stopping application servers using the WebSphere administration scripting environment, see The command-line administrative client.
Note: Certain methods are only available when using a Network Deployment deployment manager to administer your WebSphere Application Server instance (node).
Start an application server
Use one of these methods to start an application server:
Use the startServer Qshell script
The startServer Qshell script allows you to start a single application server. For information on how to start an application server using the startServer script, see The startServer script.Use the Submit Job (SBMJOB) CL command
You can run this CL command from an OS/400 command line:SBMJOB CMD(CALL PGM(QEJBAS5/QEJBSTRSVR) PARM('-instance' '/QIBM/UserData/WebAS5/Base/instance' '-server' 'server')) JOB(server) JOBD(QEJBAS5/QEJBJOBD) JOBQ(QEJBAS5/QEJBJOBQ) USER(QEJBSVR) LANGID(*USRPRF) CNTRYID(*USRPRF) CCSID(*USRPRF)where instance is the name of the instance that you want to start and server is the name of the server in that instance.
Use the Network Deployment deployment manager administrative console
If you are using a Network Deployment deployment manager to administer your instance (node), you can start application servers for the node through the administrative console for the deployment manager by performing these steps:
- Ensure that the node agent for your WebSphere Application Server instance is started. For information on how to start a node, see Start and stop a node.
Note: If the node agent does not start, run the startNode command from Qshell and then run the startServer command. After the default node agent for an instance stops running and remains stopped, you cannot restart the node agent from the administrative console page. You must start the default node agent from a command line. For more information about the scripts, see The startNode script and The startServer script.
- Start the administrative console. For more information, see the Start the deployment manager administrative console topic in Installation.
- Expand Servers and click Application Servers.
- Select the checkbox next to the application server you wish to start.
- Click Start.
Stop an application server
Use one of these methods to stop an application server:
Use the stopServer Qshell script
The stopServer Qshell script allows you to stop a single application server. For information on how to stop an application server using the stopServer script, see The stopServer script.Use the End Job (ENDJOB) CL command
To use the ENDJOB CL command to end an application server, enter this command:ENDJOB JOB(jobNumber/QEJBSVR/jobName) OPTION(*CNTRLD) DELAY(delayTime)where jobNumber is the job number, jobName is the name of the application server job, and delayTime is the amount of time to wait for the job to end in seconds. It is recommended that delayTime be 600 seconds initially.
Use the Network Deployment deployment manager administrative console
If you are using Network Deployment deployment manager to administer your WebSphere Application Server instance (node), you can end application servers from the administrative console for the deployment manager by performing these steps:
- Start the administrative console. For more information, see the Start the deployment manager administrative console topic in Installation.
- Expand Servers and click Application Servers.
- Select the checkbox next to the application server you wish to stop.
- Click Stop.
Note: If you do not have Network Deployment installed, you cannot use the WebSphere Application Server administrative console to stop the application server. You should use one of the methods above to end the application server.