WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: i5/OS

             Personalize the table of contents and search results
This topic applies only on the i5/OS operating system.

Configuring application servers to automatically start when the QWAS61 subsystem starts

WebSphere Application Server runs in its own subsystem, called QWAS61, which is installed with the product. Use these steps to configure application servers to start automatically when the QWAS61 subsystem starts.

Procedure

  1. Give your user profile authority to the QWAS61/QWASJOBD job description and QWAS61/QWAS61 subsystem description. For each profile:
    1. Create a duplicate of the job description used by WebSphere Application Server profiles. For example, issue the following command on the CL command line:
      CRTDUPOBJ OBJ(QWASJOBD) FROMLIB(QWAS61) OBJTYPE(*JOBD) TOLIB(mywasjobd) 
           NEWOBJ(myserv)
    2. Use the CHGJOBD command to change the newly created job description such that the Request data or command (RQSDTA) field starts the new server. For example, to start the default profile's application server (server1) when the subsystem is started, set the RQSDTA field as follows:
      'QSYS/CALL PGM(product_library/QWASSTRSVR) PARM(''-profilePath'' 
             ''user_data_root/profiles/default'' 
             ''-server'' ''server1'')'
      Important: If a stand-alone application server has been federated, or added, to a Network Deployment cell, specify the nodeagent server. If the node agent is not active, application servers cannot start.
  2. Configure an application server so that it is automatically started by the node agent. To configure application servers in your Network Deployment cell to start automatically when you start the node agent for the node that contains the application server:
    1. In the administrative console, click Servers > Application Servers.
    2. Click the application server that you want to start automatically.
    3. Under Server Infrastructure, click Java Process Management > Monitoring Policy and change the setting of the Node Restart property to RUNNING.
    4. Click Apply and Save to save the configuration changes.
  3. Add an autostart job entry to the QWAS61/QWAS61 subsystem. Enter the following command from the CL command line:
    ADDAJE SBSD(QWAS61/QWAS61) JOB(myserv) JOBD(mywasjobd/myserv)
  4. Optional: Configure the system such that the QWAS61 subsystem starts during system startup. To enable automatic startup, add the following line to the system startup program:
    STRSBS QWAS61/QWAS61
    Notes:
    • The system startup program is defined by the QSTRUPPGM system value.
    • TCP/IP must be active before WebSphere Application Server subsystem can start. Ensure that the STRTCP command runs before the STRSBS QWAS61/QWAS61 command in your startup program or in your autostart job.
    • For more information about the QSTRUPPGM system value, see the Work Management Guide, SC41-5306, which is available at:
      http://publib.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/QB3ALG03/CCONTENTS



In this information ...


IBM Redbooks, demos, education, and more


Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

IBM Suggests
Task topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/trun_ssenv_autostart.html