Installation manual

Chapter 2. Planning for Host On-Demand

v Deployment strategy considerations

v Before installing Host On-Demand

v Supported server operating systems

v Supported client operating systems

v Disk space requirements

v Supported browsers

v Packaging

Deployment strategy considerations

Host On-Demand provides access to host applications from a Web browser. The

browser downloads the Host On-Demand Java applet from the Web server (flow

A) and then connects to any Telnet server to access host applications (flow C). The

configuration servlet is part of the Web server. The Host On-Demand applet needs

configuration information to determine which host to connect to and other host

session properties. This configuration information can be provided to the Host

On-Demand applet from an HTML file or using the Host On-Demand

configuration server.

Understanding the HTML-based model

You can use the Deployment Wizard to create HTML files that contain

configuration information for host sessions. Therefore, you are not required to use

the Host On-Demand configuration server to specify sessions. If you allow users to

save changes to the host session configuration information, their changes are stored

on the local file system where the browser is running. This option of defining

configuration information is called the HTML-based model.

Understanding the configuration server-based model

In the configuration server-based model, host session information is maintained on

the configuration server using the administration utility, and the information is

defined using a user and group structure. The configuration server normally stores

its data locally on the Host On-Demand server machine, though it can be

configured to use LDAP instead. Users access their configurations using either

custom HTML files created in the Deployment Wizard or by using one of several

HTML files that are provided as part of Host On-Demand. Each user has a unique

user ID defined in the configuration server, and in most cases the user needs to log

on to the Host On-Demand server before viewing his sessions. If administrators

allow users to save changes, user preferences are stored in the configuration server

by user ID.

Figure 1. How Host On-Demand Components Integrate with Other Components