Defining a no program call interaction for subfile processing

If you use an iSeries Table Web component for subfile processing, the service program used by the iSeries Table Web component is specified as one of the attributes of the table. As a result, a program call does not have to be defined in the Web Interaction wizard to populate the subfile if the service program has been coded to populate the subfile.

To open the Web Interaction wizard, select the Web project folder, then click the Create or Modify a Web interaction icon Toolbar icon for Create or Modify a Web interaction. on the toolbar. If you have not defined run-time information in the iSeries Web Tools Run-time Configuration wizard, you will receive a warning message in the first page of the Web Interaction wizard.

As you progress through the Web Interaction wizard, the options you select determine which pages of the wizard are displayed.

When you use a JSP file containing a Table Web component for subfile processing, the pages in the wizard that you work with are:

  1. Specify a Name and Location for your Web Interaction
  2. Specify the Input and Output Pages for your Web Interaction
  3. No Program Call
  4. Map and Link the Input Parameters to the Input Fields
  5. Map and Link the Output Parameters to the Output Fields

The following information describes how to complete the wizard pages:

  1. Specify a Name and Location for your Web Interaction

    See Interaction name and location for descriptions of the fields on this page of the wizard.

    1. The Destination folder defaults to the WebContent folder in your Web project. You can use the Browse button to select another folder, but it must be within the WebContent folder.
    2. Enter a name for your Web interaction in the Web Interaction name field.
    3. The Java package prefix is com.ibm followed by your Web project name. This package is created in the Java Resources folder by the Web Interaction wizard. You can change this package preface, and if the package does not exist in the Web project, the Web Interaction wizard creates it for you.
    4. By default, the Use error page option is selected. This option indicates that the error.jsp file that is copied into your Web project by the wizard, is used to display run-time errors that occur when you run your Web application.
    5. Do not select Invalidate session after the interaction occurs.
    6. Click Next to proceed to the next page in the wizard.
  2. Specify the Input and Output Pages for your Web Interaction

    See Input and output pages for descriptions of the fields and controls on this page of the wizard.

    1. Select the radio button Use input pages, click Add, browse and select the JSP file in your Web project that you want to use as the input page for the Web interaction. Click OK to add the file.
    2. Select the radio button for Use output pages, click Add, browse to and select the JSP file in your Web project that you want to use as the output page for the Web interaction. Click OK to add the file.
    3. Click Next to proceed.
  3. No Program Call

    See No program call for further information about a No program call Web interaction.

    1. When this page of the wizard is displayed, Use an iSeries program or procedure is selected by default. Select the No program call radio button to change to the No Program Call page.
    2. Click Next to open the Map and Link the Input Parameters to the Input Fields page of the wizard.
  4. Map and Link the Input Parameters to the Input Fields

    See Map and link input parameters to input fields for descriptions of the fields and controls on this page of the wizard.

    This page of the wizard shows the input page fields that you added to your JSP file. Because you selected the no program call option, there are no input parameters to link to the fields in your input JSP file because this interaction does not communicate with your program or procedure. The properties and values for the input fields are displayed at the bottom of the wizard page when you click on a field in the Input page fields area.

    1. Click Next to open the Map and Link the Output Parameters to the Output Fields page.
  5. Map and Link the Output Parameters to the Output Fields

    See Map and link output parameters to output fields for descriptions of the fields and controls on this page of the wizard.

    This page of the wizard shows the output page fields that you added to your JSP file. Because you selected the no program call option, there are no output parameters to link to the fields in your output JSP file because this interaction does not communicate with your program or procedure. The properties and values for the output fields are displayed at the bottom of the wizard page when you click on a field in the Output page fields area.

  6. Create the Web interaction
    1. Click Finish to create the Web interaction.

      Because you selected the no program call option, the action classes generated by the wizard do not call a host program. The output page that you defined for a no program call interaction immediately displays in the browser when you invoke this interaction in your Web application.

    Tip: Each Web interaction is represented by a .wit file in your Web project. To modify a Web interaction, double-click the .wit file to open the Web Interaction wizard and modify the settings for the interaction.
    Restriction: The names of the PCML file and the MPCML file generated by the Web Interaction wizard are the same as the Web project name. For example, if the Web project name is myproj, then the PCML file that is generated is myproj.pcml. Similarly, the name of the MPCML file is myproj.mpcml.
    • If you create a new Web project and then import all of the files, including the PCML and MPCML files, from another Web project, the name of the PCML and MPCML files no longer match the name of the new Web project. As a result, the Web application fails to run correctly. You must rename the PCML and MPCML files to match the Web project name to resolve this problem.
    • If you rename an existing Web project, be sure to rename the PCML and the MPCML files to match the new Web project name.