(iseries)Manage the QWAS85 subsystem for WebSphere Application Server
WebSphere Application Server runs in its own subsystem, called QWAS85, which is installed with the product. For each WebSphere Application Server profile, the number of jobs that run in the QWAS85 subsystem depends on which product and which services you are using.
For each WebSphere Application Server Network Deployment profile, one deployment manager job is running in the QWAS85 subsystem.
We can perform the following tasks within this subsystem.
- Prepare the subsystem to run WebSphere Application Server profiles.
- Start the WAS environment.
When you start the default server created when you install the product, SERVER1 is listed as a started job.
- Start and stop generic application servers.
- Configure application servers to start automatically.
- Set explicit authorities for the startServer and the stopServer scripts.
Avoid trouble: *ALLOBJ authority must be set before we can run the startServer and the stopServer scripts from the HTTP Administration forms.gotcha
- Shut down the WAS subsystem.
Subtopics
- (iseries) Start the application server environment in the QWAS85 subsystem
WebSphere Application Server runs in its own subsystem, called QWAS85, which is installed with the product. Use these steps to prepare the system to run WebSphere Application Server profiles.
- (iseries) Configure application servers to automatically start when the QWAS85 subsystem starts
WebSphere Application Server runs in its own subsystem, called QWAS85, which is installed with the product. Use these steps to configure application servers to start automatically when the QWAS85 subsystem starts.
- (iseries) Shutting down the QWAS85 subsystem for WebSphere Application Server
We can shutdown the WAS subsystem in order to completely shutdown the WAS environment.
Related tasks
(iseries) Start the WAS Network Deployment environment
(iseries) Start and stop a node
(iseries) Start and stop the deployment manager