Start and stop WebSphere Application Server

WebSphere Application Server runs in its own iSeries subsystem, called QEJBAS5. QEJBAS5 is installed with the product. WebSphere Application Server Network Deployment also runs in its own iSeries subsystem, called QEJBASND5. QEJBASND5 is installed with the Network Deployment product. For each WebSphere Application Server instance, the number of jobs that run in the QEJBAS5 subsystem depends on which product and which services you are using. For each Network Deployment instance, there is one deployment manager job running in the QEJBASND5 subsystem. For more information on the WebSphere Application Server jobs, see Monitor WebSphere Application Server jobs on the iSeries server.

These topics describe how to start and stop the WebSphere Application Server and WebSphere Application Server Network Deployment environments, and how to start and stop individual server processes in those environments.

Start the WebSphere Application Server environment
This topic describes how to start the WebSphere Application Server environment.

Start the WebSphere Application Server Network Deployment environment
This topic describes how to start the WebSphere Application Server Network Deployment environment.

Stop the WebSphere Application Server or Network Deployment environment
This topic describes how to shut down the WebSphere Application Server environment.

Start and stop application servers
This topic describes how to start and stop individual application servers.

Start and stop a node
This topic describes how to start and stop a node.

Start and stop the deployment manager
This topic describes how to start and stop a Network Deployment deployment manager.

Configure application servers to start automatically in Network Deployment
This topic describes how to configure an application server so that it starts automatically when you start the node agent for the node that contains the application server.

Set explicit authorities for the startServer and stopServer scripts
You can grant explicit authorities so that user profiles that do not have *ALLOBJ authority can run the startServer and stopServer scripts. This topic provides information on granting the required authorities.