Configuring your iSeries run time

Use the iSeries Web Tools Run-time Configuration wizard to specify the authentication and run-time values for every host program or procedure call made by any Web interaction in the Web project.

To open the wizard you can either:

  1. Use the first page of the wizard, Configure authentication, to specify how Web interactions that perform program calls to an iSeries host should be connected and authenticated.
    • If you select Prompt for user ID and password, a logon JSP page opens at run time to prompt the user for an ID and password for the iSeries host program call. For further information about the logon page and the change password page, click The logon and change password pages link below.When you select this option, the Host name field is still available, but User ID, Password, Enable password-encoding, Use JCA connector and JAAS credentials, and Single signon are disabled.
    • If you select Sign on with specified values, the values you enter for host name, user ID, and password are stored in the Web Deployment Descriptor file in your Web project. When you run your Web application, these values are used when the iSeries host program or procedure is called.
      1. In the Host name field, enter the name of the iSeries host where your program is located.
      2. Enter your user ID and password for the iSeries host in the appropriate fields.
      3. Enable password-encoding is selected by default. This option ensures that the password appears in encoded format in the Web Deployment Descriptor file. If you clear the check box for this option, the password appears as plain text in the Web Deployment Descriptor file. (The Web Deployment Descriptor file, which is under your project folder in the Project Navigator view, is the same as the web.xml file, which is in the WebContent > WEB-INF folder within your project folder.)
    • Use JCA connector and JAAS credentials

      Information for the Advanced edition of the product This function is available only in WebSphere Development Studio Client Advanced Edition for iSeries, V5.x, and WebSphere Developer for iSeries, V6.0.

      If you intend to use the JNDI name of the JCA connector when testing your Web application locally, you need to install the JCA connector to the WebSphere test environment, and then define the connection factory of the JCA connector, in which you define the JNDI name. See Setting up the JCA connector for the WebSphere test environment for information about completing these tasks. Once this has been done, you can specify the options in the iSeries Web Tools Run-time Configuration wizard as follows:

      1. If you entered values for iSeries host name, User ID, and Password, these values are ignored when the Use JCA connector and JAAS credentials option is selected.
      2. Enter the JNDI name you specified in the connection factory, in the Specify the JNDI name field.
    • Single signon

      Information for the Advanced edition of the product This function is available only in WebSphere Development Studio Client Advanced Edition for iSeries, V5.x, and WebSphere Developer for iSeries, V6.0.

      1. In the Host name field enter the name of the iSeries host where your program is located.
      2. The EIM resource reference entry defaults to eis/IdentityToken_Resource_Reference. This entry needs to match the Resource Reference that you define on the References tab of the References page in the Web Deployment Descriptor file.
        In addition to defining the single signon options in the wizard, you also need to:
        • Enable and configure WAS security
        • Install and configure the Lightweight Directory Access Protocol (LDAP)
        • Configure Enterprise Identity Mapping (EIM)
        • Configure security for your application
        Click here for additional information about completing these tasks.
      3. Click Next to go the second page in the wizard.
  2. Use the second page of the wizard, Configure Run Time to define the run-time configuration values for Web interactions that perform program calls to an iSeries host.
    1. Add any run-time libraries that your program requires in the Run-time library list area. This results in the libraries being added to the library list on the iSeries server when the job is first created and before the first interaction in the application.
      1. Enter the name of the library in the Library field and click Add to add it to the list.
      2. Click the Library Position field to select *FIRST or *LAST for the library that you are adding to indicate whether it should be added as the first or last library in the list, respectively. Press Enter to save the entry in the library list. The libraries in the list are used by the program at run time.
      3. To remove a library from the list, select the library and click Remove.
      4. Use Move up and Move down to change the order of the libraries in the list.
    2. If you select *CRTDFT for the current library, no library is the current entry of the library list. If objects are created into the current library, the QGPL library is used as the default. If you select *USRPRF, then the setting in the user profile is used. If you specify a library name, then the specified library will replace the current library entry in the library list for the job.
    3. Specify the host command to execute after signing on to the host system in the Initial command field. For example, you can specify a CL setup program to set the environment before invoking applications. This program could add additional libraries to the library list, depending on the user ID.
    4. Select the Display detailed run-time errors check box if you want to see the details for any errors that occur during the run time of your Web application. This is useful for tracing and debugging development errors that may occur.
      Note: Ensure that an error page has been specified on the first page of the Web Interaction wizard, Specify a Name and Location for your Web Interaction. For further information about the error page, click The error page link below.
    5. Indicate how you want to handle a session timeout:
      1. Use Library to enter the name of the library where the program object is located.
      2. Add the name of the program or service program in the Program object field.
      3. If you are using a service program for session time-out purposes, add the service program procedure name in the Entry point field. This field is disabled if program type is *PGM.
      4. Select *SRVPGM or *PGM from this list to indicate the Program type associated with the program object. If you select program type *PGM, the entry point field is disabled.

      The program or service program procedure that you specify is invoked when the session times out. No parameters are passed to the procedure. The program or service program can perform any defined cleanup routines.

    6. Message handling
      1. Specify the message file used for message handling in the Message resource field. This file is a properties file unless you check Use iSeries message file. The properties file must be created in the JavaSource folder, or in a folder within the Java Resources folder. Selecting Browse allows you to browse the JavaSource folder for the properties file.

        If you check Use iSeries message file, it indicates that the message resource is an iSeries message file. Selecting Browse allows you to browse a remote host for the message file. For an iSeries message file, *LIBL and *CURLIB are supported.

        If only the message file name is specified, it is qualified as *LIBL.

      2. Select Use iSeries message file if the message file you specified in the Message resource field is an iSeries message file is on an iSeries host.
  3. Click Finish to save the information in the web.xml file in your Web project.

Additional considerations

In addition to using the iSeries Web Tools Run-time Configuration wizard to define authentication and run-time values, you need to ensure that host servers are running on your iSeries host when you run your Web application. The servers are *SRVMAP, *CENTRAL, *RMTCMD, and *SIGNON.

You start a host server with the STRHOSTSVR command. For example, enter:
STRHOSTSVR *RMTCMD
to start the *RMTCMD server. To start all host servers, use the command:
STRHOSTSVR *ALL

To test iSeries Web interactions in the WebSphere Application Server Test Environment, you need a TCP/IP connection to your iSeries host, and the user profile QUSER must be enabled.