Configuring integrated Web application server

 

This example describes all the steps necessary to get iSeries™ Access for Web running in an integrated Web application server environment. It also describes how to verify that the setup is working.

Before you can configure iSeries Access for Web for the integrated Web application server, ensure that the required PTFs are applied or superseded on your system. These PTFs make the integrated Web application server available and provide an HTTP Web server for iSeries Access for Web to use. Use these commands to verify that you have the correct PTFs applied or superseded:

Configuring iSeries Access for Web for the integrated Web application server consists of these steps:

Steps to configure iSeries Access for Web for the integrated Web application server:

  1. Sign on to your system.
  2. 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:
      cfgaccweb2 -appsvrtype *INTAPPSVR
      These are the parameters used:

      -appsvrtype

      Tells the command which Web application server to configure.
      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.

      For example, if you currently use iSeries Access for Web within the ASF Tomcat environment, the cfgaccweb2 command can migrate your iSeries Access for Web ASF Tomcat configuration to the integrated Web application server environment. To do this, run the command:

      cfgaccweb2 -appsvrtype *INTAPPSVR -srcsvrtype *ASFTOMCAT -srcsvrinst 
                 iwatomcat -shrusrdta *NO

    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.
    5. Press F3 when the command completes to exit the QShell session.

  3. If the command were to fail or indicate an error, refer to the log files:

  4. Stop and start the integrated Web application server to enable the changes made to the configuration. Start the iSeries Access for Web HTTP Web server. Use the following commands to enable the configuration changes and start the Web serving environment on your system:
    ENDTCPSVR SERVER(*HTTP) HTTPSVR(ADMIN) 
    STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)  
    STRTCPSVR SERVER(*HTTP) HTTPSVR(IWADFT)
  5. Use a browser to access iSeries Access for Web.

    1. Open a browser to the following address to access iSeries Access for Web Be sure enter it exactly as shown here:

      http://<system_name>:2020/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. The integrated Web 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 Main page displays.
By following the preceding steps, you completed these tasks:

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. 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 the integrated Web application server.

 

Parent topic:

Examples for configuring a new Web application server environment