Upgrade Procedure

Title: SEAGULL Web Manager Upgrade Procedure
Version: 3.4
Rev: 02
Author: Bob Campbell

 

Scope

The purpose of this procedure is to upgrade an installed version of SEAGULL Web Manager version 3.X to SEAGULL Web Manager 3.4.  This procedure assumes that you already have a working version of SEAGULL Web Manager 3.X installed on a Microsoft IIS web server, and that you wish to upgrade to SEAGULL Web Manager 3.4.

 

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

In BlueZone Web-to-Host versions 3.1 and 3.2, the default.ini page has changed slightly.  In version 3.1, 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.  In version 3.2, a new Base Registry setting has been added.

New Base Registry Control Option - Very Important!

This feature has been improved with the addition of a new BaseRegistry=2 option. This new setting is explained below.

[BlueZone]
CDVersion=3.4
;0-HKEY_CURRENT_USER (Session Settings), 1-HKEY_LOCAL_MACHINE (All Settings),
;2-FILE MODE (All Sessions - Default)
BaseRegistry=2

There are three choices for Base Registry Setting:

BaseRegistry=0
This setting will place BlueZone “Session” settings into HKEY_CURRENT_USER, and all other BlueZone settings into HKEY_LOCAL_MACHINE.

“Session” settings are those settings that are related to an individual BlueZone Session like the Connection Name, Host Address, Host Port, etc.  BlueZone creates a Registry Entry for each session, S1 through S99.

All other settings are the settings that are common to the whole BlueZone product like License Key, support information, BlueZone version, etc., that may be used by multiple users on the same machine.

BaseRegistry=1
This setting will place ALL BlueZone settings into HKEY_LOCAL_MACHINE.

BaseRegistry=2 (File Mode) default - New!
This setting will place ALL BlueZone settings into HKEY_CURRENT_USER and place BlueZone Web-to-Host into a new mode called “File Mode”.

Starting with BlueZone Web-to-Host version 3.2, BaseRegistry=2 “File Mode” is the default value.  “File Mode” is a new mode that changes the behavior of the BlueZone emulators such that when the End User launches a new session from an existing session (parent session), the new BlueZone session will take it’s settings from the configuration file that launched the “parent” session. When using BaseRegistry=2 “File Mode”, BlueZone Web-to-Host will no longer retrieve session settings from the Windows registry.

BaseRegistry=2 is required when you are deploying BlueZone Web-to-Host to End User’s who are running Windows 2000 or Windows XP with their Windows permission level set to “User”. If BaseRegistry= is set to either 0 or 1, your End Users who have their Windows permission level set to “User” (sometimes referred to as “Restricted User”) will receive messages during the downloading of BlueZone Web-to-Host that “Windows can not write to HKEY_LOCAL_MACHINE”.

CAUTION! Existing BlueZone Web-to-Host Customers - Very Important!

BlueZone Web-to-Host version 3.2 has two new features that may affect the way BlueZone Web-to-Host operates if you were to upgrade to this version using the current default values.

NOTE These new features will only have an impact on BlueZone Web-to-Host installations where you are using Save=Yes (in the Object Tag).

    How to tell if you are using Save=Yes, click here.

If you are NOT using Save=Yes, then you are not affected by this change.  If you ARE using Save=Yes, then read on.

New Features:
  • New Base Registry Control Option:
      BaseRegistry=2 default
  • Working Folder Selection Feature:
      UsePersonalFolderAsWorkingDir=Yes default

The new BaseRegistry=2 option will make BlueZone Web-to-Host work differently than before. If your current installation of BlueZone Web-to-Host, is using BaseRegistry=0, in conjunction with Save=Yes (very likely because both of these settings were are default values before version 3.2), your End Users may have stored their BlueZone emulator configuration settings in the Windows registry, or they may have saved their BlueZone configurations to a file.

The new Working Folder Selection Feature allows the BlueZone Administrator to choose whether or not to use the End User’s “Personal Folder” as the BlueZone Working Directory.  The default setting is “Yes”.

In your current installation of BlueZone Web-to-Host, you did not have a choice as to where the BlueZone Working Directory was created.  All BlueZone Web-to-Host files were stored in a folder that was created in the the End User’s Windows Temp Variable.

Solution

In the default.ini file, change the BaseRegistry=2 setting to 0 and change the UsePersonalFolderAsWorkingDir=Yes setting No, before deploying this version of BlueZone Web-to-Host to your End Users.

By making theses changes, you will essentially make this version of BlueZone Web-to-Host behave the same way as previous versions.

For more in depth information on the new default.ini file and other changes, please consult the BlueZone Web-to-Host Administrator’s QuickStart Guide.  Click on the “What’s New” button to see all the new features of this new release.

 

Upgrade Description

The technique used to upgrade your SEAGULL Web Manager involves installing the new version of SEAGULL Web Manager along side of the old version.  The Web Manager setup program will create a new installation directory, copy the new Web Manager files, copy your existing BlueZone Configuration and Distribution files, upgrade your Distribution Files with the current CAB file version names and automatically create a new ODBC link and Data Source file name.

When the upgrade is complete, you will essentially have two working versions of the SEAGULL Web Manager, the old one and the new one.  Using this method protects your current production installation of SEAGULL Web Manager and allows for testing and configuration of the new version of SEAGULL Web Manager before cutting over to production.

 

Upgrade Procedure

There are five steps to this upgrade:

  • Installing the new SEAGULL Web Manager files on your server
  • Configuring the default.asp document in Internet Service Manager
  • Testing the new SEAGULL Web Manager to verify operability
  • Importing the database from your existing SEAGULL Web Manager
  • Editing the default.ini file

 

Installing the New SEAGULL Web Manager Files

Windows 2000 Server

Windows NT 4.0 Server

  1. Insert the BlueZone CD-ROM into the CD drive of your server. It will automatically launch an introduction screen. Click on SEAGULL Products, then click on SEAGULL Web Manager to start the installation process.

    NOTE If you downloaded the BlueZone CD image from SEAGULL Customer Support, or don’t have “autorun” enabled, browse to the Web Manager directory and double click the setup.exe file instead.
  2. The SEAGULL Web Manager Setup screen will launch.  The setup program will check the location of your existing SEAGULL Web Manager installation, and automatically add the next higher number to the new directory name.

    For example, if your present SEAGULL Web Manager files are installed in a directory called SWM, the setup program will attempt to install the new files in a directory called SWM1.

    Leave all default values as they are and click Install.
     
  3. The SEAGULL Web Manager setup program will create and install the new Web Manager files in a new folder (as described above).

    The setup program will ask you if you want to create the new directory.  Answer yes.

    The setup program will ask you if you want to copy all your existing Configuration Files and Distribution Files from the old location to the new one. Answer yes.

    The setup program will ask you if you want to update the versions of the BlueZone CAB files.  Answer yes.

    The setup program will automatically create a new ODBC data link and will append the next higher number to the data link name as well.

    For example, if your current Data Source Name is swmData, then the new one will be swmData1.  You will not see a prompt for this action.  It will take place automatically.

Configuring the “default.asp” Document in Internet Service Manager

  1. On your web server, using the Internet Information Service Manager, find the new SWM1 folder (or SWM2, etc.) that was just created by the install program, and highlight it.  To learn how to start the Internet Service Manager, click here.

    NOTE You may have to refresh the Internet Service Manager display in order to see it. Click the Action button then Refresh to accomplish this.
  2. Once you have it highlighted, right click and select Properties.
     
  3. Select the Documents tab and add default.asp to the list.
     
  4. Highlight default.asp and move it to the top of the list using the Up Arrow button.
     
  5. Click OK.  No restart of IIS is necessary.
Deny Web Browser Access to the Database

NOTE This step is very important. If you do not perform this step, any end user will be able to download the entire Web Manager database if they happen to know the correct “path”.

  1. Using the IIS Management Console, go to the new SWM folder that was just created, and expand it by clicking on the plus sign.
     
  2. Find the folder called "access" and select it. This is where Web Manager stores its database.
     
  3. Right click and select Properties.  The Properties dialog for this folder will display.
     
  4. De-select the Read checkbox and set the Permissions radio button to None.
     
  5. Click OK to close the dialog.

Now the SWM application will have permission to access the data via ODBC, but web browsers will not be able to download the database file to their machines.

    Proceed to Testing the Connection

Windows 2000 Server

  1. Insert the BlueZone CD-ROM into the CD drive of your server. It will automatically launch an introduction screen. Click on SEAGULL Products, then click on SEAGULL Web Manager to start the installation process.

    NOTE If you downloaded the BlueZone CD image from SEAGULL Customer Support, or don’t have “autorun” enabled, browse to the Web Manager folder and double click the setup.exe file instead.
  2. The SEAGULL Web Manager Set up screen will launch. The setup program will check the location of your existing SEAGULL Web Manager installation, and automatically add the next higher number to the new folder name.

    For example, if your present SEAGULL Web Manager files are installed in a folder called SWM, the setup program will attempt to install the new files in a folder called SWM1.

    Leave all default values as they are and click Install.
     
  3. The SEAGULL Web Manager setup program will create and install the new Web Manager files in a new folder (as described above).

    The setup program will ask you if you want to create the new directory.  Answer yes.

    The setup program will ask you if you want to copy all your existing Configuration Files and Distribution Files from the old location to the new one. Answer yes.

    The setup program will ask you if you want to update the versions of the BlueZone CAB files.  Answer yes.

    The setup program will automatically create a new ODBC data link and will append the next higher number to the data link name as well.

    For example, if your current Data Source Name is swmData, then the new one will be swmData1.  You will not see a prompt for this action.  It will take place automatically.

Creating a Virtual Directory

On Windows 2000 Server, you must create a Virtual Directory so that you can browse to the new SEAGULL Web Manager installation.

     For help with creating a Virtual Directory, click here.

Configuring the “default.asp” Document in Internet Services Manager

  1. On your web server, using the Internet Information Service Manager, find the new SWM1 folder (or SWM2, etc.) that was just created by the setup program, and highlight it.  To learn how to start the Internet Service Manager, click here.

    NOTE You may have to refresh the Internet Service Manager display in order to see it. Click the Action button then Refresh to accomplish this.
  2. Once you have it highlighted, right click and select properties.
     
  3. Select the Documents tab and find default.asp, highlight it, and move it to the top of the list.
     
  4. Click OK.  No restart of IIS is necessary.
Deny Web Browser Access to the Database

NOTE This step is very important. If you do not perform this step, any end user will be able to download the entire Web Manager database if they happen to know the correct “path”.

  1. Using the IIS Management Console, go to the new SWM folder that was just created, and expand it by clicking on the plus sign.
     
  2. Find the folder called "access" and select it. This is where Web Manager stores its database.
     
  3. Right click and select Properties.  The Properties dialog for this folder will display.
     
  4. De-select the Read checkbox and set the Permissions radio button to None.
     
  5. Click OK to close the dialog.

Now the SWM application will have permission to access the data via ODBC, but web browsers will not be able to download the database file to their machines.

 

Testing the Connection

CAUTION! Performing the following “test” is absolutely necessary in order to properly set up the correct file paths in the new SEAGULL Web Manager. Skipping this test will result in the new Web Manager pointing to files in the old Web Manager.

You should now be able to connect to the new SWM directory on your web server by accessing the web severs URL followed by /swm1 (or whatever the newly created folder name is). This should bring up the default Host Access Login page that end users will use to launch their sessions.

    Example: http://www.yourhost.com/swm1

  1. Go to the default Host Access Login Page now.  It should look like this:

  1. Login using the following Login ID without a password:
    Login ID = 5250demo
    Password =

    Click the Login button.
     
  2. You will be presented with the following screen:


  1. Click the Launch All Sessions button.
     
  2. This will launch a standard iSeries Display and Printer session to one of the Seagull iSeries hosts.
     
  3. Once the sessions are launched, close them down and proceed.
     
  4. Go to the Administrator's Login Page by adding /admin to the URL you used above.

    Example: http://www.yourhost.com/swm1/admin

    Go to the Administrator's Login Page now.  It should look like this:

  1. Login with the top level user name of  “owner” with the password “owner” without the quotes.  You should now be at the Admin Home page.

 

 

Importing Data

The next step is to import your existing data. This feature will import all data that is stored in the access database. The data consists of the user database, all their assigned distribution files and sessions, any groups that may be configured and any LU/devices that are assigned.

  1. On the Admin Home page, click on the Import Data link. You will be presented with the Import Data page.
     
  2. Enter your previous DataSource Name in the field provided. You do not have to enter a path here, just the name.

    3. Example: swmData

  3. Make sure that the “Versions 1.1a - 3.0a” radio button is selected.
     
  4. Click the Import button. All data will be imported into the access database located in the new SEAGULL Web Manager folder and a log will be created so that you can check to make sure that all data was imported.

 

Editing 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.

Registration Key - If you are an existing BlueZone Customer and you are not using the new Software Activation Feature, then you will need to copy your BlueZone Registration Key from your old ez.ini file to the new default.ini file as follows:

Edit the new default.ini file with Notepad, find the RegistrationKey= entry and enter your 14 digit BlueZone Registration Key. Be sure to include the double quotes.  Copy it from your old ez.ini file located in the old ez directory.

Configuration Lock - If you are using the Configuration Lock Feature update the values from your old ez.ini file located in the old ez directory.

By default, the new SEAGULL Web Manager’s default.ini file will have both the emulator lock and the BlueZone FTP lock set to a value of zero. This means that all features are unlocked.

NOTE If you are currently using multiple default.ini files in the old system, to support multiple lock configurations or desktop icons for multiple emulators, you will need to create multiple .ini files in the new system to support this. If you simply copy over the old .ini files, they will not have the correct structure.  Instead, use the new default.ini file as a master, and copy it the number of times you need and give it the same name as in the old system.

Congratulations!

You have successfully upgraded your SEAGULL Web Manager to the latest SEAGULL Web Manager.