How to Manually Upgrade an Existing Installation

Prerequisites

The procedure assumes that you have a pre-3.3 version of BlueZone Web-to-Host installed, and you wish to manually upgrade the version to version 3.4, and you do not want to install or use the Web-to-Host Wizard.  Also, it assumes that you are very familiar with your current BlueZone Web-to-Host installation and the operation of your web server.

Who Should Use This Method

Some BlueZone Web-to-Host Customers have made extensive customization changes to their Web-to-Host installations.  For example, you may have made web page and file structure changes in order to incorporate BlueZone Web-to-Host into a portal web site.  If this is the case, you can still upgrade to version 3.4, by manually coping the necessary files from the BlueZone Web-to-Host version 3.4 CD-ROM or image, to the proper place in your current BlueZone Web-to-Host structure.

Upgrade Description

The recommended procedure is make a complete copy of your current BlueZone Web-to-Host installation by manually copying your files to a new location on your web server.  Then, copying the necessary BlueZone version 3.4 files from the BlueZone CD-ROM or image, to the new location.  The final step involves editing several HTML and text files so that the new BlueZone files are being used in place of the old ones.

Using this method, you will be able to test the copy before making the copy your production installation.

Procedure

1. Place the BlueZone version 3.4 CD-ROM in the CD drive of the web server, or copy an image of the BlueZone CD in a location where you have access to the files.  Using Windows Explorer, navigate to the BlueZone Web-to-Host folder.

2. Copy your current BlueZone Web-to-Host installation to a new location on your web server.  For example, if your current installation is located here:

C:\inetpub\wwwroot\bluezone

then copy the bluezone folder to bluezone1

C:\inetpub\wwwroot\bluezone1

Your folder file structure of "bluezone1" should look something like this: (unless it was previously customized)

assets
bz3270
bz5250
bzftp
bzvt
docs
options

3. Using Notepad, edit all your default.ini files (or any other .ini files that you may have created), and add the following lines shown in blue, to the [BlueZone] section as shown here:

[BlueZone]

RegistrationKey=

;0-Application Settings in HKEY_LOCAL_MACHINE, Session Settings in HKEY_CURRENT_USER

;1-All Settings in HKEY_LOCAL_MACHINE

;2-All Settings in HKEY_CURRENT_USER (default mode)

BaseRegistry=2

UsePersonalFolderAsWorkingDir=Yes

UseAllUsersCommonFolderAsWorkingDir=No

ProfileMode=Yes

;DesktopMode=desktop.ini

NOTE  Depending on what version of BlueZone you are upgrading from, you may have to add additional lines to your default.ini file.

4. Copy the BlueZone CAB files from the BlueZone CD or image to the appropriate Product Folders in "bluezone1".  All the version 3.4 BlueZone CAB files are located in the "cabs" folder.  In "bluezone1", the CAB files are stored in the corresponding Product Folder.  For example, copy the bzmd.cab file to the bz3270 folder on "bluezone1".

The following table shows where the CAB files need to be copied:

5. Copy the Web-to-Host Control Module files from the BlueZone CD or image to the root of "bluezone1".  All the version 3.4 BlueZone Control Module files are located in the "controls" folder.  In "bluezone1", the Control Module files are stored in the "root".  For example, copy the sglw2hcm.jar to the "root" of "bluezone1".

The following table shows where the Control Module files need to be copied:

6. Copy the following miscellaneous files to their proper locations:

7. Update your Distribution Files so that the version 3.4 CAB files are downloaded.  In each Product Folder on "bluezone1", you will find one or more Distributions Files.  The Distribution File is used to tell the Web-to-Host Control Module what files to download.  For example in the bz3270 folder there are at least two Distribution Files.  display.e3d and printer.e3d.  Use Notepad to edit these files as shown here.

The default display.e3d file with the CAB file shown in blue:

bzmd32C5.cab,1

mfdisp1.zmd,1

seaglapl.ttf,1

../seagull.saf,1
 

Change it to look like this (changes are shown in red):

bzmd.cab,2

mfdisp1.zmd,1

seaglapl.ttf,1

../seagull.saf,1

NOTE  If your current installation has been customized, your Distribution Files may look different from the example.  Also, you may have additional Distribution Files.  Make sure that you update ALL Distribution Files located in ALL the Product Folders with the new CAB file names.

8. Update your Object Tags with the new ActiveX Control Module version.  Each BlueZone Product Folder contains one or more HTML pages that contain Object Tags.  You must edit these pages with Notepad and change the OCX version number.  For example, in the bz3270 folder each HTML page that begins with obj_ has an Object Tag and must be updated.

The default obj_d_3.htm file with the OCX version shown in blue:

<OBJECT ID="Seagull Web-to-Host Control Module v3"

CLASSID="clsid:037790A6-1576-11D6-903D-00105AABADD3"

CODEBASE="../sglw2hcm.ocx#Version=3,2,5,362" HEIGHT=0 WIDTH=0>

<PARAM NAME="IniFile" VALUE="default.ini">

<PARAM NAME="Sessions" VALUE="MD_S1">

<PARAM NAME="MD_DistFile" VALUE="display.e3d">

<PARAM NAME="MD_S1" VALUE="mfdisp1.zmd">

<PARAM NAME="MD_S1_Save" VALUE="Yes">

</OBJECT>

Change it to look like this (changes are shown in red):

<OBJECT ID="Seagull Web-to-Host Control Module v3"

CLASSID="clsid:037790A6-1576-11D6-903D-00105AABADD3"

CODEBASE="../sglw2hcm.ocx#Version=3,4,0,451" HEIGHT=0 WIDTH=0>

<PARAM NAME="IniFile" VALUE="default.ini">

<PARAM NAME="Sessions" VALUE="MD_S1">

<PARAM NAME="MD_DistFile" VALUE="display.e3d">

<PARAM NAME="MD_S1" VALUE="mfdisp1.zmd">

<PARAM NAME="MD_S1_Save" VALUE="Yes">

</OBJECT>

NOTE  Make sure you update ALL your Object Tag pages.

9. Test your "bluezone1" site and make sure everything is working properly.

Congratulations!  You have successfully upgraded you BlueZone Web-to-Host installation.