WebSphere Application Server Network Deployment profiles run in
the QWAS61 subsystem and require that TCP/IP is configured and activated on
the system. This topic discusses how to prepare your system to run WebSphere
Application Server Network Deployment profiles.
Before you begin
TCP/IP must be active before the 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.
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).
About this task
Complete this task to configure your system to
- Run WebSphere Application Server Network Deployment profiles
- Configure these profiles to start automatically when the QWAS61 subsystem
starts
Procedure
- To prepare your system to run WebSphere Application Server Network
Deployment profiles, follow these steps.
- Start Transmission Control Protocol/Internet Protocol (TCP/IP).
On the i5/OS command line, enter this command:
STRTCP
- To start your application server profile, see one of these topics:
Note:
- Unlike previous releases, releases starting with WebSphere Application
Server V6 do not start the default application server when the subsystem is
started. When you use the startServer or startManager Qshell script to start
your server profile, the QWAS61 subsystem is started if it is not currently
active.
- WebSphere Application Server Network Deployment includes support for stand-alone
application server profiles, managed (federated) profiles, and deployment
manager profiles without requiring the WebSphere Application Server product
to also be installed. When you install 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.
- Use one of these methods to verify that your server is running:
- On the i5/OS command line, run the Work with Active Jobs (WRKACTJOB) command:
WRKACTJOB SBS(QWAS61)
Your
server job is listed. When the server is ready to accept requests, the joblog
contains message WAS0106: WebSphere application server serverName ready.
- In Operations Navigator, look for QIBM_WSA_ADMIN under Server Jobs.
- If your profile has authority to the QWAS61/QWASJOBD job description
and QWAS61/QWAS61 subsystem description, you can configure WebSphere Application
Server Network Deployment profiles to automatically start when the QWAS61
subsystem starts. Perform these steps for each profile:
- Create a duplicate of the job description that is used by WebSphere
Application Server Network Deployment profiles. For example, on the i5/OS
command line, run this command:
CRTDUPOBJ OBJ(QWASJOBD) FROMLIB(QWAS61) OBJTYPE(*JOBD) TOLIB(mywasjobd) NEWOBJ(mydmgr)
- 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/V61/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/V61/ND/profiles/default''
''-server'' ''server1'')'
- Add an autostart job entry to the QWAS61/QWAS61 subsystem. Enter
this command from the i5/OS command line:
ADDAJE SBSD(QWAS61/QWAS61) JOB(mydmgr) JOBD(mywasjobd/mydmgr)
You can configure the system so that the QWAS61 subsystem starts at iSeries
system startup. To enable automatic startup, add the following line to the
system startup program:
STRSBS QWAS61/QWAS61
Results
You have configured your system to run WebSphere Application Server
Network Deployment profiles, and might have configured these profiles to start
automatically when the QWAS61 subsystem starts.
What to do next
Deploy an application to get started.