+

Search Tips   |   Advanced Search

(iSeries)

Product library, directories, subsystem, job queue, job description, and output queues

An IBM i platform uses different configurations than installations of WebSphere Application Server on other platforms.

This topic describes the product library, directories, subsystem, job queue, job description, and output queues that WAS uses on the IBM i platform.


Product library and directories

In a default installation, all editions of WAS for IBM i use the following library and directories:

QWAS85 library

Product library

/QIBM/UserData/WebSphere/AppServer/V85 directory

Root directory for user data that is common to all editions of the product.

/QIBM/ProdData/WebSphere/AppServer/V85/ND directory

Root directory containing product data shared by all WAS WAS ND profiles. Additionally, the master copies of the files that make up a profile are stored here. Do not modify files under this directory structure.

/QIBM/UserData/WebSphere/AppServer/V85/ND directory

Root directory for WAS WAS ND profile information. All profiles of WAS ND are created under this directory structure.


Subsystem

All editions of the product for IBM i use the QWAS85 subsystem. The subsystem description for QWAS85 is located in the QWAS85 product library. The application server, node agent and deployment manager processes run in this subsystem.


Job queue

All editions of the product for IBM i use the QWASJOBQ job queue. The job queue is in the QWAS85 product library. The application server, node agent, and dmgr processes are all submitted to this job queue when you invoke the startServer, startNode, or startManager scripts. The QWASJOBQ job queue is associated with the QWAS85 subsystem.


Job description

All editions of the product for IBM i use the QWASJOBD job description. The job description is in the QWAS85 product library. The application server, node agent, and dmgr processes use this job description when submitted to run in the QWAS85 subsystem.

The QWASJOBD job description has the following default settings:

 Display Job Description
 System:   MYISERIES
 Job description:   QWASJOBD       Library:   QWAS85

 User profile . . . . . . . . . . . . . . . . . . :   QEJBSVR
 CL syntax check  . . . . . . . . . . . . . . . . :   *NOCHK
 Hold on job queue  . . . . . . . . . . . . . . . :   *NO
 End severity . . . . . . . . . . . . . . . . . . :   30
 Job date . . . . . . . . . . . . . . . . . . . . :   *SYSVAL
 Job switches . . . . . . . . . . . . . . . . . . :   00000000
 Inquiry message reply  . . . . . . . . . . . . . :   *RQD
 Job priority (on job queue)  . . . . . . . . . . :   5
 Job queue  . . . . . . . . . . . . . . . . . . . :   QWASJOBQ
   Library  . . . . . . . . . . . . . . . . . . . :   QWAS85
 Output priority (on output queue)  . . . . . . . :   5
 Printer device . . . . . . . . . . . . . . . . . :   *USRPRF
 Output queue . . . . . . . . . . . . . . . . . . :   QWASOUTQ
   Library  . . . . . . . . . . . . . . . . . . . :   QWAS85
 Message logging:
   Level  . . . . . . . . . . . . . . . . . . . . :   4
   Severity . . . . . . . . . . . . . . . . . . . :   0
   Text . . . . . . . . . . . . . . . . . . . . . :   *SECLVL
 Log CL program commands  . . . . . . . . . . . . :   *NO
 Accounting code  . . . . . . . . . . . . . . . . :   *USRPRF
 Print text . . . . . . . . . . . . . . . . . . . :   *SYSVAL

 Routing data . . . . . . . . . . . . . . . . . . :   QCMDI

 Request data . . . . . . . . . . . . . . . . . . :   *NONE

 Device recovery action . . . . . . . . . . . . . :   *SYSVAL
 Time slice end pool  . . . . . . . . . . . . . . :   *SYSVAL
 Job message queue maximum size . . . . . . . . . :   *SYSVAL
 Job message queue full action  . . . . . . . . . :   *WRAP
 Allow multiple threads . . . . . . . . . . . . . :   *YES
 Initial ASP group  . . . . . . . . . . . . . . . :   *NONE
 Spooled file action  . . . . . . . . . . . . . . :   *SYSVAL
 Text . . . . . . . . . . . . . . . . . . . . . . :   WEBSPHERE JOB DESCRIPTION

Use the Request data parameter to specify information to start a WAS profile when the QWAS85 subsystem is started. For more information on how to start an application server when the subsystem starts see Starting the application server environment in the QWAS85 subsystem. We can modify the job description if the values do not meet your requirements. However, we must not change the Allow multiple threads value. Because the product processes contain a Java virtual machine that is multithreaded, this value must be *YES.


Output queues

All editions of the product for IBM i use the QWASOUTQ output queue. The output queue is in the QWAS85 product library. By default, this output queue stores job logs for these processes:

This queue also stores other spooled files. The public authority to the output queue is *USE. This setting ensures that the user profile specified for the USER parameter (on the SBMJOB command) has the necessary authority to the output queue when it submits the WAS job to the job queue. The default user profile is QEJBSVR.

We might want to clear the output queue periodically if the number or size of the spooled files becomes large.

  • Starting the application server environment in the QWAS85 subsystem