Installation manual
Cached clients
A cached client can be any client where you choose to cache the applet on the
user’s machine. Most likely, the HTML is created using the Deployment Wizard;
however, it could be HODCached.html, as well. The cached client
(HODCached.html) provides all the Host On-Demand functions including problem
determination and the Screen Customizer. It is cached on your local disk the first
time you download it. The next time you start the emulator session, only a small
applet downloads from the server, reducing the time needed to start the session.
The applet that is downloaded checks to see if the software on the server is more
recent than the software that has been cached. If so, the cached software is
updated. The cached client is recommended for users with slow connectivity (such
as dial-up phone lines) where downloading a large applet would take a long time.
Note: Using the cached client with Netscape 6.x or another Java2-enabled Web
browser causes the hoddbg.jar file to be downloaded. This gives the client
full Host On-Demand functionality; however, the resulting download will be
approximately 4.5MB. It is recommended that you use the Deployment
Wizard to customize your HTML files to include only those components that
are needed.
The cached client is persistent across operating system restarts and browser
reloads. If you want to remove it, you must load
http://server_name/hod_alias/HODRemove.html in your browser, where
server_name is the name of your Web server and hod_alias is the alias you selected
during installation.
For more information on removing the cached client from a JRE 1.3 client, see
Netscape 6.0 and Java2-enabled Web browser issues.
In order for you as a client-side user on Windows 2000 Professional to
successfully install the Host On-Demand cached client, you must have sufficient
permissions set to change the system registry. A Windows 2000 ″Restricted User
(Users group)″ user cannot successfully complete a Host On-Demand cached
client installation unless granted ″Standard User (Power Users group)″ access.
Cached client support across the Internet
If you deploy the cached client to the Internet, consider that your users might use
Host On-Demand with other business partners running Host On-Demand servers
at different service levels. This could be a problem if your user needs different
functions when accessing servers at different service levels. Components of
different service levels are not supported within a single cached client, and there
can be only one cached client on a machine. Host On-Demand Version 5.0.4 or
higher is required to run the cached client across the Internet.
To prevent complications, you can do some or all of the following:
v Select all the functions a user needs (across all sites the user accesses) in a
preload list when you create an HTML page using the Deployment Wizard
v Use the disable function of the Deployment Wizard to disable all functions not
in the preload list and the functions that are not needed for your users
v Create separate HTML pages for different user groups
v Give your HTML pages a name that identifies your company
v Always install Screen Customizer to prevent users who are accessing your server
from losing Screen Customizer functions when accessing other sites
Chapter 8. Loading the Host On-Demand clients 39