There is nothing to configure in order for standard Web-to-Host deployment mode to work since it is the default mode for BlueZone
Web-to-Host. However, you can change some of the standard Web-to-Host deployment mode features.
Configuration method: Web-to-Host Wizard
Feature scope: Launch folder level feature
By default, BlueZone Web-to-Host will operate in the standard Web-to-Host deployment mode. That is to say that served desktop
mode and embedded client mode are not enabled.
Using the Web-to-Host Wizard, using all default settings, creating a site, a launch folder, and one session, produces the
following results:
|
• |
Allow User to Save Changes Locally - Yes |
|
• |
Prompt for LU or Device Name - No |
|
• |
Use the launch pad Feature - Yes (with Toolbar, Launch Buttons and Border enabled) |
|
• |
Served desktop mode - No |
|
• |
Enable Launcher/Session Manager on Desktop - Yes |
|
• |
Use Personal Folder as Working Directory - Yes |
|
• |
Base Registry Setting - 2 |
|
• |
BlueZone Feature Locks - None |
|
• |
BlueZone FTP Feature/Function Locks - None |
|
• |
Use ActiveX for Internet Explorer - Yes |
|
• |
Use Java for Non-Internet Explorer Browsers - Yes |
|
• |
Include Scripting/Automation/ and HLLAPI Components - No |
|
• |
Include BlueZone FTP - No |
|
• |
Include Mainframe Printer with Display Session - No |
|
• |
Include iSeries Printer with Display Session - No |
|
• |
Close the Browser Window After Session Launch - No |