Installation

BlueZone Web-to-Host

Manually Upgrading a Pre-3.3 Version of BlueZone Web-to-Host

Prerequisites

IMPORTANT!  This procedure is for pre-3.3 versions of BlueZone Web-to-Host only!

The procedure assumes that you have a pre-3.3 version of BlueZone Web-to-Host installed, and you wish to manually upgrade your installation to the current version and you do not want to convert over to the new 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 the current version by manually copying the necessary files from the current BlueZone Web-to-Host CD-ROM or image, to the proper locations in your current BlueZone Web-to-Host structure.

NOTE  If you are going to be using any of the new BlueZone emulators that were introduced in BlueZone version 4.0, like ICL 7561, Unisys T27 and Unisys UTS, we don't recommend manually upgrading your existing installation.  However, it is still possible to manually incorporate the new emulators into an existing BlueZone Web-to-Host installation.  Please contact BlueZone Software Customer Care for assistance.

Upgrade Description

In early versions of 4.0, the BlueZone Web-to-Host folder in the BlueZone CD image, did not contain folders for the CAB files and the Web-to-Host Control files, as in the past.  In these versions these files are stored internally, and can only be accessed after the Web-to-Host Wizard 4.0 is installed and at least one Site is created.

In versions 4.1 and higher, we added a new folder called \manual-upgrade.  You no longer have to install the Web-to-Host Wizard if all you want to do is upgrade your current installation.

We highly recommend that you make a backup copy of your current BlueZone Web-to-Host installation before attempting the upgrade.

Now that you have direct access to the needed files located in the \manual-upgrade folder, you can easily copy these files to a backup folder of your current installation.

Finally, you will edit your current Distribution Files and Object Tags to conform to version 5.0.

NOTE  This procedure covers the upgrading of all the BlueZone emulators that were available in BlueZone Web-to-Host version 3.2 and older.  If for example, you only use BlueZone Mainframe Display and Printer, you only have to upgrade the files associated with BlueZone Mainframe Display and Printer.  You do not have to upgrade the files located in the bz5250, bzFTP, and bzVT folders.

The upgrade procedure can be broken down into the following parts:

Following this outline, you will be able to test the backup copy of your Web-to-Host installation for proper operation before making the copy available as your production installation.

Procedure

Get Access to the New Files

  1. Place the BlueZone CD-ROM in your CD/DVD drive.  It will auto-run the BlueZone DemoShield and display the Welcome to BlueZone Splash screen.

  2. Exit from the DemoShield.

  3. Launch Windows Explorer and explore the contents of the BlueZone CD-ROM.

  4. Locate the BlueZone Web-to-Host folder and open it.

  5. Locate the \manual-upgrade folder and open it.

  6. You now have access to the new CAB files and Control files.

Copy Your Existing Web-to-Host Installation

  1. On your web server, copy your current BlueZone Web-to-Host installation to a new location.  For example, if your current installation is located here:

    C:\inetpub\wwwroot\bluezone

     

    Copy the bluezone folder to bluezone1.

    C:\inetpub\wwwroot\bluezone1

     

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

    assets
    bz3270
    bz5250
    bzftp
    bzvt
    docs
    options

Copy the New Web-to-Host Files to Your Current Installation

  1. Copy the BlueZone CAB files from the \manual-upgrade\cabs folder to the appropriate Product Folders in "bluezone1".  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".

NOTE  In addition to the CAB files shown in the following list, the \manual-upgrade\cabs folder will contain several additional CAB files that are new to BlueZone Web-to-Host version 5.0.  Some of the these CAB files do not have to be copied to "bluezone1", and can be ignored, and others have to be copied to the root because they are required by all applications.

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

Emulator Name

File Name

From

Copy To

iSeries Display

bzad.cab

cabs

bz5250 folder

iSeries Printer

bzap.cab

cabs

bz5250 folder

BlueZone FTP

bzftp.cab

cabs

bzftp folder and options folder

ICL Display

bzicl.cab

----

ignore this file

Kerberos CAB

bzkerb.cab

cabs

bzVT folder

TCP/IP Print Server

bzlpd.cab

----

ignore this file

Mainframe Display

bzmd.cab

cabs

bz3270 folder

Mainframe Printer

bzmp.cab

cabs

bz3270 folder

Scripting CAB

bzsc.cab

cabs

options folder

Scripting Player Only CAB

bzscp.cab

cabs

options folder

T27 Display

bzt27.cab

----

ignore this file

UTS Display

bzuts.cab

----

ignore this file

BlueZone VT

bzvt.cab

cabs

bzVT folder

Manifest CAB

crt.cab

cabs

root

SSL CAB

ssl.cab

cabs

root

 

  1. You can delete all the old CAB files (like bzmd32C5.cab) since they will no longer be used.

  2. Copy the Web-to-Host Control Module files from the \manual-upgrade\controls folder to the root of "bluezone1".  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:

File Name

From

To

sglw2hcm.jar

controls

root

sglw2hcm.ocx

controls

root

sglw2hjv-signed.jar

controls

root

unsigned_sglw2hcm.ocx

controls

root

 

  1. Copy the following miscellaneous files from the \manual-upgrade folder to their proper locations as shown here:

File Name

From

To

bzstring.dl_ *

root

root

ezclear.exe

root

root

bzimg16.dl_ *

shared

options (this file is optional)

bzimg24.dl_ *

shared

options (this file is optional)

bzimg32.dl_ *

shared

options (this file is optional)

bzimg48.dl_ *

shared

options (this file is optional)

bzprndef.ini

shared

bz3270 and bz5250 folders

bzsm.ex_

shared

options

dbcsxlat.dl_

shared

options

seaglapl.ttf

shared

bz3270

spoolinf.ex_

shared

options

unins.ex_

shared

options

 

* Indicates a new file that did not exist before version 4.1

CAUTION!  Do not copy the Software Activation File (seagull.saf) from the Site folder of your Web-to-Host Wizard installation (MySite folder).  You need to continue to use your current Software Activation File that was copied from your production installation.

Edit Your Distribution Files:

  1. 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:

Here is an example of the display.e3d file with the CAB file name shown in blue:

bzmd32C5.cab,1

mfdisp1.zmd,1

seaglapl.ttf,1

../seagull.saf,1
 

Edit the name of your CAB files as shown in red.  The product version number is no longer used in the CAB file name.  Add the corresponding printer cab (bzmp.cab) only if you use the printer emulator.  Add the crt.cab, ssl.cab and bzstring.dl_ to the end of the list as shown in red:

bzmd.cab,1

mfdisp1.zmd,1

seaglapl.ttf,1

../seagull.saf,1

../bzstring.dl_,1

../crt.cab,1

../ssl.cab,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.

If you want to take advantage of the new Windows Vista™ style ToolBar icons, it will be necessary to add the names of the icon image files to your Distribution File as shown here in red.

bzmd.cab,1

mfdisp1.zmd,1

seaglapl.ttf,1

../seagull.saf,1

../bzstring.dl_,1

../crt.cab,1

../ssl.cab,1

../options/bzimg16.dl_,1

../options/bzimg24.dl_,1

../options/bzimg32.dl_,1

../options/bzimg48.dl_,1

 

NOTE  These files are optional.  If keeping user download time to a minimum is critical, do not include these files in your download.  BlueZone will automatically revert to the old 16x16 ToolBar icons if these files are not present.

Edit Your default.ini File

  1. Using Notepad, edit your default.ini file 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

ProfileSharing=Yes

;DesktopMode=desktop.ini

EnablePowerKeys=No

FIPSMode=No

InstallForAllUsers=No

 

  1. Further down the page in the [Configuration Lock Feature] section, add the following lines shown in blue.

[Configuration Lock Feature]

Lock=0

LockFTP=0

LockTelnet=0

ShowLockedDialogs=Yes

DisableAppendToClipboard=No

 

  1. Now add this new [Session Manager] section below the [Configuration Lock Feature] section:

[Session Manager]

AutoUpdate=Yes

 

NOTE  If you are upgrading from a very old version of BlueZone Web-to-Host, you may have to add additional lines to your default.ini file.  So look it over very carefully.

Edit Your Object Tags

  1. Update all your Object Tag pages with the following ActiveX Control Module version.  Each BlueZone Product Folder contains several Object Tag pages.  These are the pages that start with obj_.  

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.

Here is an example of the 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 the OCX version 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=-1,-1,-1,-1" 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.

When all the above changes are complete, test your "bluezone1" site and make sure everything is working properly.

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