Data/Application Server (LANSA Web Server Extension only)

When you select the Add or Change button on the Maintain Systems dialog box, the Add or Change LANSA System (as appropriate) is displayed. Add or change the Data/Application Server options as required.

LANSA System

Enter the name of the host that is acting as your Data/Application Server. This name must be known to the LANSA Communications Extensions. You must not leave this parameter blank.

User, Password and Confirm Password

Specify a user profile and its password. A user profile is required to allocate a communications conversation between the Web Server and the Data/Application Server. Confirm password must match the password.

Note: The user profile specified must exist on the Data/Application Server and must have sufficient authority. If the Data/Application Server uses a trusted connection to connect the database, the user profile (by default it is usually PCXUSER) must have sufficient authority to access the database.

Test Connection

Use Test Connection to try to establish a communication connection with the Data/Application Server with the user profile and system specified.

LANSA Library (IBM i only)

Enter the name of the LANSA Library.

The LANSA Library is required when you connect to a Data/Application Server on IBM i.

Code Page (IBM i only)

Enter the parameter to specify the Code Page translations to be applied for communications between the Web Server and the Data/Application Server.

For LANSA Web Server Extension configurations:

     if left blank, no code page translations will be performed.

otherwise:

     the value specified defines the name of the LANSA Code Page mapping table. This Code Page mapping table must be located in the LANSA Web Server Extension code page directory (by default C:\Program Files (x86)\LANSA\WebServer\IISPlugin\codepage).

If you wish to use your own customized code page files you need to add them to the code page directory. Note that if the specified file cannot be found, a file with the same name but prefixed with wpi_ will be used. This is to ensure backward compatibility. For example, if you enter cp037, the LANSA Web Server Extension will look for cp037.dat in the code page directory and if that file is not found it will then look for wpi_cp037.dat in the code page directory.

Automatic Configuration

Refresh every

Specify how often the LANSA system's configuration will be refreshed by the LANSA Web Server Extension. To disable, set the value to 0. In that case the configuration will only be loaded when the web server starts.

Use Configuration Notification

If enabled (that is, selected) changes to the configuration will be passed immediately to the web server.

Restart Delay

If the communication to the LANSA web configuration background process has been broken, the LANSA Web Server Extension will wait this setting's number of seconds before attempting to restart the web configuration background process. Within the waiting period, any changes to LANSA web configurations will not be made usable to the LANSA Web Server Extension.

Note that a shorter delay may impose more loading to the LANSA Web Server Extension, especially if the corresponding LANSA listener has been purposefully shut down.

Receive Timeout

This setting controls how the LANSA Web Server Extension communicates with the web configuration background process. For end users, this setting affects the responsiveness of the LANSA Web Server Extension upon Web Server shutdown.

A longer timeout can reduce loading for background communication, but the LANSA Web Server Extension may take longer to shut down.