(iSeries)

Manage the QWAS85 subsystem for WAS

WebSphere Application Server runs in its own subsystem, called QWAS85, which is installed with the product. For each WAS profile, the number of jobs that run in the QWAS85 subsystem depends on which product and which services we are using.

For each WAS ND profile, one deployment manager job is running in the QWAS85 subsystem.

We can perform the following tasks within this subsystem.

Tasks

• Prepare the subsystem to run WAS profiles.

• Start the WAS appservers environment.

  When we start the default server created when we install the product, SERVER1 is listed as a started job.

• Restart generic application servers.

• Configure application servers to start automatically.

• Set explicit authorities for the startServer and the stopServer scripts.

  *ALLOBJ authority must be set before we can run the startServer and the stopServer scripts from the HTTP Administration forms.

• Shut down the WAS subsystem.

Subtopics

• (iSeries) Starting the application server environment in the QWAS85 subsystem
  WAS runs in its own subsystem, called QWAS85, which is installed with the product. Use these steps to prepare the system to run WAS profiles.
• (iSeries) Configure application servers to automatically start when the QWAS85 subsystem starts
  WAS 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 WAS
  We can shutdown the WAS subsystem in order to completely shutdown the WAS environment.

(iSeries) Starting the WAS ND environment

(iSeries) Restart a node

(iSeries) Restart the deployment manager