Configure WebSphere Application Server Network Deployment V6.0 for OS/400

This example is for users that are not familiar with the Web serving environment. It describes all the steps necessary to get iSeries™ Access for Web running in a WebSphere^® Application Server Network Deployment V6.0 for OS/400^® environment. It also describes how to verify that the setup is working.

1. Start the IBM Web Administration for iSeries interface.
   1. Start a 5250 session to the server.
   2. Sign on with a user profile that has at least these special authorities:  *ALLOBJ, *IOSYSCFG, *JOBCTL, and *SECADM.
   3. Run the following server command to start the web administration interface job: STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
   4. Minimize the 5250 session.
2. Create an HTTP web server and a WebSphere Application Server Network Deployment V6.0 for OS/400 Web application server:
   1. Open a browser to: http://<server_name>:2001
   2. Log in with a user profile that has, at least these special authorities:  *ALLOBJ, *IOSYSCFG, *JOBCTL, and *SECADM.
   3. Select IBM Web Administration for iSeries.
   4. Select the Setup tabbed page.
   5. Under Common Tasks and Wizards, select Create Application Server.
   6. The Create Application Server page opens. Select Next.
   7. Select WebSphere Application Server Network Deployment V6.0 for OS/400 then select Next.
   8. The Specify Application Server Name page opens.   For Application server name, specify iwa60nd.  This will be the name of the WebSphere Express Web application server. Select Next.
   9. The Select HTTP Server Type page opens.  Select Create a new HTTP server (powered by Apache) then select Next.
   10. The Create a new HTTP server (powered by Apache) page opens.
       • For HTTP server name, enter IWA60ND
       • For Port, specify 2046.
       Select Next.
   11. The Specify Internal Ports Used by the Application Server page opens. For First port in range, change the default value to 21046. Select Next.
   12. The Select Business and Sample Applications page opens. Select Next until the Summary page opens. 
   13. Select Finish.
   14. The web page is re-displayed with the Manage > Application Servers tabbed page active. Under Instance/Server, iwa60nd/iwa60nd – WAS, V6.0 ND is listed with a status of Creating. From this Web page, you can manage the WebSphere application server.

       Use the refresh icon next to the Creating status to refresh the page, if the page does not periodically refresh.

   15. When the status is updated to Stopped, select the green icon next to Stopped to start the WebSphere application server. The status will be updated to Starting. Use the refresh icon next to the Starting status to refresh the page if the page does not periodically refresh. iSeries Access for Web requires that the WebSphere application server is running before it can be configured.
       Important:

       Wait for the status to be updated to Running before moving to the next step.
   16. Minimize the browser window
3. Configure iSeries Access for Web.
   1. Restore the 5250 session window.
   2. To see the WebSphere application server running, run the server command: WRKACTJOB SBS(QWAS6)
   3. Verify that IWA60ND is listed as a job running under the QWAS6 subsystem.  iSeries Access for Web requires the WebSphere application server is running before it can be configured.
   4. Verify the Web application server is ready:
      1. Enter option #5 on your IWA60ND job.
      2. Enter option #10 to display the job log.
      3. Press F10 to display detailed messages.
      4. Verify the message Websphere application server iwa60nd ready is listed.  This message indicates that the application server is fully started and is ready for Web serving.
      5. Press F3 until you return to a command line.
   5. iSeries Access for Web provides commands to configure the product. Two different commands are provided, a CL command and a QShell script command.  Both commands provide and perform the same function.  Use whichever version you prefer.
      • To use the CL command, follow these steps:
        1. Configure iSeries Access for Web for your Web application server by using the following command:  

           QIWA2/CFGACCWEB2 APPSVRTYPE(*WAS60ND) WASPRF(iwa60nd) APPSVR(iwa60nd) 

           These are the parameters used:

           APPSVRTYPE

           Tells the command which Web application server to configure.

           WASPRF

           Tells the command which profile of the Web application server to configure. In previous releases of WebSphere, the WASINST parameter was used. In WebSphere Application Server Network Deployment V6.0 for OS/400, profiles have replaced instances.

           APPSVR

           Tells the command the name of the Web application server within the profile to configure.

           For help on this command and the parameters, press F1.
           Migration Note: If you are already using iSeries Access for Web within another Web application server, refer to New Web application server considerations. This topic discusses additional CFGACCWEB2 command parameters that can be input to migrate user data from an existing configuration to this new configuration.
        2. Several messages similar to these will be displayed:  
           • Configuring iSeries Access for Web. 
           • Preparing to perform the configuration changes. 
           • Calling WebSphere to perform the configuration changes.
           • iSeries Access for Web command has completed.
           • The WebSphere instance application server must be stopped and then started to enable the configuration changes.
               
        3. Press F3 or Enter when the command completes to exit the display session.
      • To use the QShell script command, follow these steps:
        1. Start the QShell environment using the following server command: QSH
        2. Make the iSeries Access for Web directory the current directory.  Run this server command:  

           cd /QIBM/ProdData/Access/Web2/install 

        3. Configure iSeries Access for Web for the Web application server previously created:

           cfgaccweb2 -appsvrtype *WAS60ND -wasprf iwa60nd -appsvr iwa60nd

           These are the parameters used:

           -appsvrtype

           Tells the command which Web application server to configure.

           -wasprf

           Tells the command which profile of the Web application server to configure. In previous releases of WebSphere, the -wasinst parameter was used. In WebSphere Application Server Network Deployment V6.0 for OS/400, profiles have replaced instances.

           -appsvr

           Tells the command the name of the Web application server within the profile to configure.

           For help on this command and the parameters, specify the -? parameter.
           Migration Note: If you are already using iSeries Access for Web within another Web application server, refer to New Web application server considerations. This topic discusses additional CFGACCWEB2 command parameters that can be input to migrate user data from an existing configuration to this new configuration.
        4. Several messages similar to these will be displayed:  
           • Configuring iSeries Access for Web. 
           • Preparing to perform the configuration changes. 
           • Calling WebSphere to perform the configuration changes.
           • iSeries Access for Web command has completed.
           • The WebSphere instance application server must be stopped and then started to enable the configuration changes.
               
        5. Press F3 when the command completes to exit the QShell session.
   6. If the command were to fail or indicate an error, refer to the log files:

      /QIBM/UserData/Access/Web2/logs/cmds.log

      High level, cause and recovery information; translated.

      /QIBM/UserData/Access/Web2/logs/cmdstrace.log

      Detailed command flow for IBM Software Service; English only.

   7. After successfully configuring iSeries Access for Web, the WebSphere application server must be restarted to load the changes to its configuration.  This will be done later.
   8. Signoff the 5250 session window and close the window.
4. Start the Web environment.
   1. Return to the browser window that is open to the IBM Web Administration for iSeries server management page.
   2. The Manage > Application Servers tabbed page should be active. Under Instance/Server is listed iwa60nd/iwa60nd – WAS, V6.0 ND with a status of Running. Stop and restart the WebSphere application server:
      1. Select the red icon next to the Running status to stop the WebSphere server. Select the refresh icon next to the Stopping status to refresh the page if the page does not periodically refresh.
      2. When the status is updated to Stopped, select the green icon next to Stopped to start the WebSphere application server.
      3. The status will be updated to Starting. Select the refresh icon next to the Starting status to refresh the page if it does not periodically refresh.
         Important: Wait for the status to be updated to Running before moving to the next step.
         iSeries Access for Web will load and start as the WebSphere application server starts.
   3. Select the HTTP Servers tabbed page.
   4. Under Server, select IWA60ND - Apache. The current status of this Apache HTTP server should be Stopped. Select the green icon next to the status to start the HTTP server. The status is updated to Running.
   5. Close the browser window.
5. Use a browser to access iSeries Access for Web
   1. Open a browser to either of the following addresses to access iSeries Access for Web:

      http://<server_name>:2046/webaccess/iWAHome
      http://<server_name>:2046/webaccess/iWAMain

   2. Log in using an i5/OS™ user ID and password. The initial load of iSeries Access for Web might take a few seconds.  WebSphere Application Server is loading Java™ classes for the first time.  Subsequent loads of iSeries Access for Web will be faster.
   3. The iSeries Access for Web Home or Main page displays.
   4. Close the browser window.