|
Modes of Operation |
Chapter 3 |
Starting with version 3.3, BlueZone has two modes of operation, Registry Mode and Profile Mode. Previously, BlueZone only had Registry Mode. These "modes" refer to the way BlueZone saves and recalls configuration settings.
Profile Mode is now the default operation for BlueZone 3.3. BlueZone saves all of its settings in files, called Session Profiles. All parameters for each session are saved in a single file. BlueZone registers the file extensions to Windows during setup so simply clicking on a Session Profile file launches BlueZone and loads the saved settings. Clicking the Session Profile multiple times results in multiple, identical BlueZone sessions. The mode is set using the "Profile Mode =Yes" setting in the Registry. When this setting is absent or set to "No" BlueZone will operate in Registry Mode.
Existing Customers - Very Important!
If you are installing BlueZone version 3.3 or above, using the new Profile Mode, on top of an existing pre-3.3 BlueZone installation, all your existing Session Profiles that are currently stored in the Windows registry, will be converted to Session Profiles (configuration files).
BlueZone will automatically assign Profile Session names to your existing Session Profiles. For example, if you had three Mainframe sessions stored in the windows registry, S1, S2 and S3, they would be converted to Session Profiles with the following names:
Mainframe Display S1.zmd
Mainframe Display S2.zmd
Mainframe Display S3.zmd
All three sessions will appear in the BlueZone Session Manager with the Connection Name as the icon label. All three Session Profiles will automatically be created and placed in your BlueZone "config" folder.
Registry Mode was in previous versions, the default mode of operation, and is now an optional mode. In Registry Mode, BlueZone saves all of its global and user settings in the Windows Registry. Each BlueZone Session (S1, S2, etc.) has a unique set of parameters that are loaded by clicking the BlueZone icon. The sessions launch in order, starting with the first unused session number. This was the default operation for BlueZone prior to version 3.3.
Existing Customers - Very Important!
If you want to continue to use Registry Mode (we highly recommend that you convert to the new Profile Mode), you must make a change to the SETUP.INI file before you install BlueZone.
CAUTION!
You can
not run the BlueZone Setup.exe program from the BlueZone CD-ROM or the
DemoShield (the DemoShield is the Welcome to BlueZone Menu that automatically
launches when you insert the BlueZone CD-ROM into your CD-ROM drive),
if you want BlueZone to install in Registry Mode.
Copy the entire BlueZone Desktop folder from the BlueZone CD-ROM to a convenient location on your workstation's hard drive.
Edit the SETUP.INI file with Notepad, and change the ProfileMode=Yes setting to ProfileMode=No.
Save the file and exit Notepad.
Install BlueZone by double clicking the Setup.exe program located on your hard drive in the same folder where the modified SETUP.INI file is located.
BlueZone will now be installed in Registry Mode.
Global BlueZone settings are saved in the Registry for both Registry Mode and Profile Mode, and User Settings are saved in the Registry in Registry Mode. Where they are saved depends on the value for the Base Registry Setting in the SETUP.INI file for BlueZone Desktop installations, or in the DEFAULT.INI file if you are using BlueZone Web-to-Host's Served Desktop Mode.
Base Registry 0 - Global Settings are saved in the Local Machine Key. User level settings are saved in Current User. This is the default setting for BlueZone Desktop.
Base Registry 1 - Global and User settings are saved in Local Machine. Use this mode if all users of the machine should share both Global and User Settings.
Base Registry 2 - Global and User settings are saved in Current User. This is the default mode for Web to Host, allowing Web to Host to work properly on machines with Restricted User accounts.
Session Manager has been completely redesigned for BlueZone 3.3, in order to support Profile Mode. When using Session Manager, the End User can view all of their saved Profiles and launch one or more sessions by clicking on the Profile entry. Session Manager uses the Configs folder in the user's working directory. Session Manager still works with Registry Mode and displays the session information in the same format it did in previous versions.
Converting from Registry Mode to Profile Mode is a function built into the Session Manager. The first time the Session Manager runs in Profile Mode, it checks the Registry for BlueZone configurations and converts them to Session Profile files. Once converted, the Session Profiles appear in the Session Manager. BlueZone uses the Registry Key name as the Session Profile file name. For example, Mainframe Display S1.ZMD.