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

Use this information to configure iSeries™ Access for Web for WebSphere^® Application Server Network Deployment V6.0 for OS/400^®.

Note: WebSphere profiles that are federated to the Network Deployment environment are not supported by iSeries Access for Web.

To configure iSeries Access for Web for WebSphere Application Server V6.0 for OS/400, do the following:

Sign on to your server.
Start the WebSphere subsystem in which you want iSeries Access for Web to run. Enter the server command STRSBS QWAS6/QWAS6.
Start the WebSphere application server in which you want iSeries Access for Web to run by following these steps:
1. Run the server command STRTCPSVR *HTTP HTTPSVR(*ADMIN).
2. Open your browser to http://<server_name>:2001.
3. Select the IBM^® Web Administration for iSeries link.
4. Navigate to your HTTP server and start it if it is not already running.
5. Navigate to your WebSphere application server and start it if it is not already running.
6. Wait for the application server to show a status of running.
7. Minimize the browser window. You will return to this window in a later step.
Use the iSeries Access for Web CL or script configuration command.
- To use the CL command, run this server command:
  QIWA2/CFGACCWEB2 APPSVRTYPE(*WAS60ND) WASPRF(was_profile_name) APPSVR(app_svr)
- To use the script command, run these server commands:
  STRQSH
  cd /QIBM/ProdData/Access/Web2/install
  cfgaccweb2 -appsvrtype *WAS60ND -wasprf was_profile_name -appsvr app_svr
The configuration commands use these variables:
was_profile_name

The name of the WebSphere application server profile you are using. If you are using the default WebSphere profile with the CL command, specify *DEFAULT.

app_svr

The name of the application sever within the profile being configured.

For more information about either value, refer to the help text for the appropriate field.
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.
Return to the Web administration browser interface window that you minimized in step 3.g, then stop and restart the WebSphere application server.
Open your browser to http://<your_server_name>:port/webaccess/iWAMain. Be sure the case matches the example.

The iSeries Access for Web main page opens.

Note: The first call of the iWAMain page might take a few minutes, but subsequent calls should not take as long.

Start of change 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 CL commands, use the CL command finder. End of change