Configuring WebSphere Application Server V6.1 for i5/OS

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 V6.1 for i5/OS^® environment. It also describes how to verify that the setup is working.

Install the latest service pack PTF. This is required for WebSphere Application Server V6.1 support. For instructions, see the Installing PTFs for the Licensed Internal Code and the operating system topic for instructions. Configuring your Web serving environment consists of these steps:

Start the IBM^® Web Administration for i5/OS interface (also known as IBM HTTP Server for iSeries). See step 1.
Create an HTTP Web server and a WebSphere Application Server V6.1 for i5/OS Web application server. See step 2.
Configure iSeries Access for Web. See step 3.
Start the Web environment. See step 4.
Use a browser to access iSeries Access for Web. See step 5.

Steps to configure the Web serving environment:

Start the IBM Web Administration for i5/OS interface.
1. Start a 5250 session to the system.
2. Sign on with a user profile that has at least these special authorities: *ALLOBJ, *IOSYSCFG, *JOBCTL, and *SECADM.
3. Run the following command to start the web administration interface job: STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
4. Minimize the 5250 session.
Create an HTTP Web server and a WebSphere Application Server V6.1 for i5/OS Web application server environment:
1. Open a browser to: http://<system_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 i5/OS.
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 V6.1 Base then select Next.
8. The Specify Application Server Name page opens. For Application server name, specify iwa61base. This will be the name of the WebSphere 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 IWA61BASE
  - For Port, specify 2050.
  Select Next.
11. The Specify Internal Ports Used by the Application Server page opens. For First port in range, change the default value to 21050. 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 Server, iwa61base/iwa61base – V6.1 Base 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.
  
  On this page, the Profile name, Server name and Product install path are listed. Make note of each value exactly as shown on this page. These values will be input to the iSeries Access for Web configuration command in a later step.
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. If you are prompted to also start the IWA61BASE HTTP server, clear the IWA61BASE HTTP server option so that it does not start at this time. 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.
  
  Wait for the status to be updated to Running before moving to the next step.
16. Minimize the browser window.
Configure iSeries Access for Web.
1. Restore the 5250 session window.
2. To see the WebSphere application server running, run the command: WRKACTJOB SBS(QWAS61)
3. Verify that IWA61BASE is listed as a job running under the QWAS61 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 IWA61BASE job.
  2. Enter option 10 to display the job log.
  3. Press F10 to display detailed messages.
  4. Verify the message WebSphere application server iwa61base 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 a QShell script command to configure the product. To use the QShell script command, follow these steps:
  1. Start the QShell environment by using the following CL command: QSH
  2. Make the iSeries Access for Web directory the current directory. Run this command:
```
cd /QIBM/ProdData/Access/Web2/install
```
  3. Configure iSeries Access for Web for the Web application server previously created:
```
cfgaccweb2 -appsvrtype *WAS61BASE -wasprf iwa61base -appsvr iwa61base 
-wasinsdir /QIBM/ProdData/WebSphere/AppServer/V61/Base
```
    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 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.
    
    -wasinsdir
    
    Tells the command the location in the i5/OS integrated file system where WebSphere Application Server V6.1 for i5/OS was installed. The default value is /QIBM/ProdData/WebSphere/AppServer/V61/Base. You were asked to make note of this value in step 2 when creating the HTTP Web server and a WebSphere Application Server environment.
    
    -wasusrid
    
    Tells the command the user ID to use for WebSphere Application Server configuration changes when WebSphere security has been enabled for the profile. In this example, security was not enabled. This parameter is not required for this example.
    
    -waspwd
    
    Tells the command the password for the user ID specified using the -wasusrid parameter. In this example, security was not enabled. This parameter is not required for this example.
    
    For help on this command and the parameters, specify the -? parameter.
    Migration
    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.
Start the Web environment.
1. Return to the browser window that is open to the IBM Web Administration for i5/OS server management page.
2. The Manage > Application Servers tabbed page should be active. Under Server is listed iwa61base/iwa61base – V6.1 Base 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. If you are prompted to also stop the IWA61BASE HTTP server, do not deselect it. It should also be stopped. 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. If you are prompted to also start the IWA61BASE HTTP server, do not deselect it. It should also be started.
  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.
    
    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 IWA61BASE - Apache. The current status of this Apache HTTP server should be Running. If the current status is 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.
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://<system_name>:2050/webaccess/iWAHome
  http://<system_name>:2050/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.

By following the preceding steps, you completed these tasks:

Created a WebSphere Web application server named iwa61base.
Created an HTTP server named IWA61BASE.
Configured iSeries Access for Web for the WebSphere application server.
Stopped and restarted the WebSphere application server and HTTP Web server. iSeries Access for Web started when the WebSphere application server started.
Verified that iSeries Access for Web can be accessed from a Web browser.

In this example, only the cfgaccweb2 command is used to configure iSeries Access for Web For more information about using all the iSeries Access for Web commands, use the CL command finder, which will find iSeries Access for Web CL commands. As shown above, there are also equivalent QShell script commands.

You can refer to the CL command online help to learn how to use the other QShell script commands. Only the QShell script commands support WebSphere Application Server V6.1 for i5/OS.

Parent topic:

Examples for configuring a new Web application server environment

Related information
CL command finder