When you run the BlueZone Web-to-Host 6.2 Wizard
installer on a machine that has an older Wizard installed, such as
version 5.2, you are not upgrading the existing Wizard. You are installing
version the 6.2 Wizard
alongside of your existing Wizard. This process is called a side-by-side
installation.
The major version of BlueZone is appended to the installation
directory. BlueZone continues to use the standard working directory
to store the configuration profiles, so your users will not lose their
session customizations when they upgrade to version 6.1.
- Follow the Web-to-Host installation procedure to install
the BlueZone Web-to-Host Wizard Version 6.1. Refer to Installing BlueZone Web-to-Host for
more information.
After the
6.2 Wizard
is installed, you can still run the old Wizard. You can upgrade any
and all of the existing Web-to-Host sites to version
6.2.
Important: Do not directly upgrade a production site. It is
highly recommended that you create a copy of the site, upgrade the
copied site, and test the upgraded site before making it a production
site.
- Upgrade the user’s standard Web-to-Host mode sites. Refer
to Upgrading sites and BlueZone for more information
on upgrading the sites.
The process to upgrade your current Web-to-Host user clients
to version 6.2 works
exactly the same way as it did in previous versions of BlueZone.
You upgrade the existing Web-to-Host site to version 6.2, then
each time a user launches BlueZone Web-to-Host from their desktop
shortcut, or directly from the Web-to-Host URL, the new version 6.1
Web-to-Host Control Module is automatically downloaded and installed
with the new BlueZone Web-to-Host Version 6.2 files.
- Upgrade the user’s served desktop mode sites:
- Copy and upgrade the served desktop mode sites. Refer
to Upgrading sites and BlueZone for more information.
BlueZone served desktop mode uses the BlueZone Session Manager
to detect and download any new files. The current Session Manager
has no knowledge of the new side-by-side installation scheme and cannot
download the version
6.2 files
to the correct location. It is very important that you do not upgrade
the existing served desktop sites to version
6.2. You
must copy your existing sites to a new name and upgrade the copied
sites to version
6.2.
Important: If you do not change the name of the sites and you
upgrade the current sites to version 6.2 and your
users use their desktop shortcut to launch a BlueZone Web-to-Host
session, the new BlueZone 6.2 files
will not be downloaded to the correct place on their hard drive.
This will cause problems. The remedy if this happens is to have the
user run eZClear without deleting their user files. Then they go
to the new BlueZone Web-to-Host URL, and download the new 6.2 files
from scratch. This time the new files will go to the correct place
on their hard dive because the new Web-to-Host Control Module will
be downloaded and it will know where to place the files.
- Instruct your users to make sure that BlueZone Session
Manager and BlueZone sessions are not running.
- Instruct your users to go to the new URL, download,
and install BlueZone Served Desktop.
For example, if a site was named 3270host in
the previous BlueZone Web-to-Host installation, the URL is http://www.yourcompany.com/3270host/bluezone/default.htm.
If
you copied and renamed the site to 3270host2 and
then upgraded to version 6.2, the URL
will be http://www.yourcompany.com/3270host2/bluezone/default.htm now.
After
the download is complete, your users will launch BlueZone from their
desktop shortcut just as before.