You use the iSeries Web Tools Run-time Configuration wizard when you run your Web Application in either the WebSphere Test Environment on the client, or on the WebSphere Application Server on the iSeries server. The wizard is used to specify the authentication and run-time values for every host program or procedure call made by any Web interaction in the Web project.
The values that you specify in the wizard are stored in the web.xml file within the WEB-INF folder in your Web project. This file is also identified as the Deployment Descriptor, which appears under the Web project name.
Authentication values
You use the iSeries Web Tools Run-time Configuration wizard to specify how Web interactions that perform program calls to an iSeries host should be connected and authenticated. You can specify whether you want to prompt for user ID and password, to store signon credentials in the Deployment Descriptor file, and whether your password should be encoded in the Deployment Descriptor file.
In the Advanced version of the product, you can indicate whether you want to save the user ID and password in the Java Authentication and Authorization Service (JAAS) via the iSeries program call JCA connector option (Use JCA connector and JAAS credentials), or to use an Enterprise Identity Mapping (EIM) domain to provide signon authorization (the Single signon option).
Run-time configuration values
You also use the iSeries Web Tools Run-time Configuration wizard to set the run-time configuration values for the business logic of your Web application. These options include your run-time library list, your current library specification, and any initial command to invoke on your iSeries host when you run the application. You can also indicate whether or not you want to display any detailed run-time errors, specify session timeout options, and how to handle messages for data that you input in your Web application.
Your business logic
Your business logic is contained in a program or procedure on the iSeries host, which is the 3rd tier of your Web application.
The 2nd tier of your Web application contains the JSP files and iSeries run-time classes. If you want to test your Web application in the WebSphere Application Server test environment that is in the workbench, you use the wizard to set the authentication and run-time configuration values for the iSeries host.
If you move the 2nd tier of your Web application from the built-in test environment to the WebSphere Application Server on the iSeries host, you do not have to change the values you set in the wizard as long as the 3rd tier iSeries host has not changed.
However, if you move the entire application, including the business logic, from one iSeries to another, you need to change the configuration values to identify the new 3rd tier iSeries host and any potential changes to the authentication and run-time values that you set through the wizard.
(C) Copyright IBM Corporation 1992, 2006. All Rights Reserved.