(iSeries)

Starting the WAS, Network Deployment environment

WebSphere Application Server WAS, Network Deployment profiles run in the QWAS85 subsystem and require that TCP/IP is configured and activated on the system. Learn how to prepare your system to run WAS, Network Deployment profiles.

TCP/IP must be active before the product can start. Ensure that the STRTCP command runs before the STRSBS QWAS85/QWAS85 command in your startup program or in your autostart job.

The system startup program is defined by the QSTRUPPGM system value. For more information about the QSTRUPPGM system value, see the Work Management Guide (SC41-5306) (http://publib.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/QB3ALG03/CCONTENTS).

Complete this task to configure your system to

• Run WAS WAS, Network Deployment profiles

• Configure these profiles to start automatically when the QWAS85 subsystem starts

Tasks

• To prepare your system to run WAS, Network Deployment profiles, follow these steps.

  1. Start Transmission Control Protocol/Internet Protocol (TCP/IP). On the IBM i command line, enter this command:

     STRTCP
     

  2. To start the application server profile, see one of these topics:

     • Starting an application server

     • Starting and stopping the deployment manager
     • Unlike previous releases, releases starting with WAS Version 6 do not start the default application server when the subsystem is started. When we use the startServer or startManager Qshell script to start the server profile, the QWAS85 subsystem is started if it is not currently active.
     • WAS, Network Deployment includes support for stand-alone application server profiles, managed (federated) profiles, and deployment manager profiles without requiring the product to also be installed. When we install WAS, Network Deployment, two profiles are created: the default profile and the dmgr profile. The default profile is a stand-alone application server profile and the dmgr profile is a deployment manager profile.

  3. Using one of these methods to verify that the server is running:

     • On the IBM i command line, run the Work with Active Jobs (WRKACTJOB) command:

       WRKACTJOB SBS(QWAS85)
       

       Ythe server job is listed. When the server is ready to accept requests, the joblog contains message WAS0106: WAS serverName ready.
     • In System i Navigator, look for QIBM_WSA_ADMIN under Server Jobs.

• If our profile has authority to the QWAS85/QWASJOBD job description and QWAS85/QWAS85 subsystem description, we can configure WAS, Network Deployment profiles to automatically start when the QWAS85 subsystem starts. Perform these steps for each profile:

  1. Create a duplicate of the job description used by WAS, Network Deployment profiles. For example, on the IBM i command line, run this command:

     CRTDUPOBJ OBJ(QWASJOBD) FROMLIB(QWAS85) OBJTYPE(*JOBD) TOLIB(mywasjobd) NEWOBJ(mydmgr)
     

  2. Specify the name of the user profile associated with the mydmgr job description.

     The user profile must be QEJBSVR:

     CHGJOBD JOBD(mywasjobd/mydmgr) USER(QEJBSVR)
     

  3. Use the CHGJOBD command to change the newly created job description so that the Request data or command (RQSDTA) field starts the server. For example, to start the default deployment manager server (dmgr), set the RQSDTA value as follows:

     'QSYS/CALL PGM(product_library/QWASSTRSVR) 
     PARM(''-profilePath''      ''/QIBM/UserData/WebSphere/
     AppServer/V85/ND/profiles/
     dmgr''     ''-server'' ''dmgr'')'
     

     To start the default application server (server1), set the RQSDTA value as follows:

     'QSYS/CALL PGM(product_library/QWASSTRSVR) PARM(''-profilePath'' 
         ''/QIBM/UserData/WebSphere/AppServer/V85/ND/profiles/default''
         ''-server'' ''server1'')'
     

  4. Add an autostart job entry to the QWAS85/QWAS85 subsystem. Enter this command from the IBM i command line:

     ADDAJE SBSD(QWAS85/QWAS85) JOB(mydmgr) JOBD(mywasjobd/mydmgr)
     

     We can configure the system so that the QWAS85 subsystem starts at system startup. To enable automatic startup, add the following line to the system startup program:

     STRSBS QWAS85/QWAS85
     

We have configured your system to run WAS, Network Deployment profiles, and might have configured these profiles to start automatically when the QWAS85 subsystem starts.

What to do next

Deploy an application to get started.

Starting an application server

Starting and stopping the deployment manager

Starting the application server environment in the QWAS85 subsystem