Scope
The purpose of this procedure is to upgrade any version of BlueZone Web-to-Host to any higher version of BlueZone Web-to-Host including maintenance releases. This procedure assumes that you have at least BlueZone Web-to-Host version 3.0 installed and working on a web server, and that you wish to upgrade to a higher version of BlueZone Web-to-Host or maintenance release.
What’s New
BlueZone Secure FTP Changes
If you are currently launching BlueZone FTP from within a BlueZone display session by adding the bzftp.exe file to the BlueZone Distribution File, you will have to make some small changes in order for BlueZone Web-to-Host versions 3.0 and higher to work properly.
 For detailed instructions on making these changes, click here.
New default.ini Page
Starting with BlueZone Web-to-Host version 3.1, the default.ini page has changed slightly. The primary difference is that the way you create desktop shortcuts has changed. Also, you will notice that the BlueZone CD Version number is now stored in the default.ini file, and support for the Served Desktop Client mode has been added.
For more in depth information on the new default.ini file, please consult the BlueZone Web-to-Host Administrator’s QuickStart Guide on this CD.
Here is a link the the BlueZone Web-to-Host Administrator’s QuickStart Guide.
What’s Provided
The BlueZone CD-ROM that you have been provided, contains all the latest BlueZone products. The BlueZone Web-to-Host files are located in a folder called BlueZone Web-to-Host and contain the entire family of BlueZone emulation products.
These emulation products include:
- BlueZone 3270 Display Emulator
- BlueZone 3270 Printer Emulator
- BlueZone 5250 Display Emulator
- BlueZone 5250 Printer Emulator
- BlueZone FTP Client
- BlueZone VT - VT100, VT220, VT320, VT420 Emulator
The BlueZone Web-to-Host emulators provided are by default pre-configured to connect to various host systems. You will of course, change the default configurations to connect to your host systems. See the following chart for a list of default pre-configured hosts.
Pre-configured Host Settings |
|
BlueZone 3270
|
Library of Congress Mainframe
|
|
BlueZone 5250
|
SEAGULL iSeries
|
|
BlueZone FTP
|
Microsoft FTP Site
|
|
BlueZone VT
|
Library of Congress Telnet Host
|
|
Upgrade Description
The technique used in this upgrade involves installing the new version of BlueZone Web-to-Host along side of your existing BlueZone Web-to-Host installation. The BlueZone Web-to-Host setup program will create a new installation directory (with user intervention) and copy the new BlueZone Web-to-Host files.
When the upgrade is complete, you will essentially have two working versions, your original BlueZone Web-to-Host version and the new BlueZone Web-to-Host Maintenance Release version. Using this method protects your current production installation of BlueZone Web-to-Host and allows for testing and configuration of the new BlueZone Web-to-Host files before cutting over to production.
There are five steps to the BlueZone Web-to-Host upgrade:
- Installation - Copy the BlueZone Web-to-Host files to your web server.
- Setting “The Path” to support Netscape browsers.
- Test to insure that BlueZone is working with our default pre-configured hosts.
- Copying your Configuration and Modifying the Distribution Files.
- Updating the default.ini file.
NOTE to Existing BlueZone Customers We are in the process of changing to a new software licensing scheme. This new Software Activation Feature, is currently not required to be used by existing BlueZone Customers. If you are an existing Customer, no changes are needed at this time. You can continue to use the current BlueZone licensing scheme.
However, if you would like to learn more about our new Software Activation Feature, click here.
The installation process is very simple. In fact, it is more of a copying process than an installation process. In other words, the BlueZone Web-to-Host files are simply copied to the appropriate folders or directories on your web server as static files. There is no associated BlueZone Web-to-Host application that runs on the web server.
Installation - Microsoft IIS Web Servers - From the BlueZone CD
- Insert the BlueZone CD-ROM into the CD drive of the server. The CD will “autorun” and you will be presented with the SEAGULL BlueZone Software contents page.
- Click the BlueZone link followed by the BlueZone Web-to-Host link. You will be presented with the BlueZone Web-to-Host Setup page.
- The BlueZone Web-to-Host Setup Program will launch the BlueZone Web-to-Host Setup dialog.
 CAUTION! The BlueZone Web-to-Host Setup Program will attempt to automatically copy the new BlueZone Web-to-Host files into the default directory called “bluezone”. If this is where your current installation of BlueZone Web-to-Host is located, you must change the location so that you don’t overwrite your current installation.
Change the Destination Drive and Directory location to “bluezone1” as shown:
 |
When you have the Destination Drive and Directory location set, click the Install button.
- The Setup program will copy all the BlueZone Web-to-Host files to your web server.
For help in setting up a “virtual directory” on your web server, click here.
Installation - Mainframe and iSeries Web Servers
If you are installing BlueZone Web-to-Host on an HTTP Web Server, Domino Go, WebSphere or other EBCDIC web server, only the HTML files should be converted from ASCII to EBCDIC. All other files should be transferred as binary. All editing of the associated ASCII text files should be performed on an ASCII computer (not on the web server) with notepad, then copied back to the web server as a binary file.
- Copy the BlueZone Web-to-Host files from the BlueZone CD-ROM to your web server being careful to maintain the directory structure as it appears on the BlueZone CD as shown in the following screen shot.
Also, be sure to copy the files as the correct file type as described above.
Setting “The Path” for Netscape Browsers
In order for BlueZone Web-to-Host to work properly with Netscape browsers, it is necessary to set the “path” which is located in the default.htm page. This “path” statement lets the JavaScript know the location of the Java Plug-in (.jar) and the Java “zippy” (.xpi) files.
- On the web server, edit the default.htm page with Notepad. The “path” statement is located at the top of the page inside an Administrators Note. It looks like this:
thePath = "http://poplar.renex.com/bluezone/"
- Edit thePath = value with a fully qualified URL that matches your web server.
thePath = "http://www.yourhost.com/bluezone1/"
- Save the file and exit notepad.
Testing the Connection
You should now be able to connect to the newly created directory on your web server by accessing the web severs URL followed by /bluezone1 (or whatever name you gave to the newly created folder). This should bring up the default.htm page which will determine your browser type and version, then automatically launch the launch.htm page.
You should be able to connect to the default hosts that are pre-configured in BlueZone Web-to-Host.
Copying the Configuration Files and Modifying the Distribution Files
- If you have created your own BlueZone Configuration Files, copy them from the old installation to the same directory in the new installation now.
- If you did not create any new BlueZone Configuration Files and just reused the ones that came with BlueZone Web-to-Host. Copy those Configuration Files to the same directory in the new installation now.
- Configuration Files end in .zmd, .zmp, .zad, .zap, .zft, .zvt, .ftp
- If you modified any of your Distribution Files, you will have to make those same modifications to the new Distribution Files.
- Distribution Files end in .e3d, .e3p, .e5d, .e5p, .eft, .evt
 NOTE If you are using any optional features such as BlueZone Scripting Host, HLLAPI, special fonts, etc., that are included in any of your Distribution Files, copy them over to the new “bluezone” directory now.
Updating The default.ini file
Registration Key - Update the new default.ini file by copying your BlueZone Registration Key from the old default.ini file.
Desktop Shortcuts - If you are using the Desktop Shortcut feature, copy that information from your old default.ini file to the new one.
Configuration Lock - If you are using the Configuration Lock Feature update the values from your old default.ini file to the new one.
Test Your Installation
You should now be able to access the new BlueZone Web-to-Host directory and launch your pre-configured BlueZone sessions.
Congratulations!
You have successfully upgraded your installation of BlueZone Web-to-Host!
|
