BlueZone configuration profiles store information describing every aspect of a BlueZone session including; the host connection settings, keyboard mappings, color settings, font settings, emulator screen position and size, toolbar settings, and more. Having all of these settings in a single file provides a simple way to easily deploy pre-configured BlueZone sessions throughout the enterprise. We refer to the main BlueZone configuration profile as the top-level configuration profile. Each BlueZone emulator has its own top-level configuration profile file extension. For example, the top-level Mainframe Display extension is .ZMD.

Refer Top-level configuration profile for a complete listing of the top-level configuration profile file extensions.

Dialog-level configuration profiles are sub-configuration files. Depending on the BlueZone emulator, there can be as many as nine (9) dialog-level configuration profiles. These dialog-level configuration profiles are grouped by function. The functions for Mainframe Display are session, Telnet, display, keyboard, transfer, toolbar, power pad, and status bar settings. Each emulator has a slightly different list.

BlueZone configuration dialogs that have toolbar buttons located at the bottom of the dialog, support dialog-level configuration profiles:

From left to right the toolbar functions are Default, File Open (Import File), Save, File Save As (Export File), and Help.

Any BlueZone dialog that contains a dialog configuration profile toolbar can have that dialog's settings exported to a file (as a dialog-level configuration profile) with its own file extension. Dialog-level configuration profiles for each emulator and dialog have unique file extensions.

Refer to Dialog-level configuration profile for a complete listing of the dialog configuration profile file extensions.

When BlueZone is first deployed from the web server, the BlueZone administrator does not need to include any dialog-level configuration profiles with the distribution. Only the potential to use dialog-level configuration profiles must be configured by selecting the check box of any dialog configuration profile that the administrator wants to control. In the following example, the BlueZone administrator has opted to select only the TN3270 check box. Select all parts of a BlueZone configuration that you want to control.

On day one, all users make their initial BlueZone download with the same top-level configuration profile. As time goes by, each user makes and save their own customizations to the parts of the BlueZone configuration that they are allowed to change.

Refer to Locking BlueZone emulator features for more information on how to lock BlueZone features that you don't want your users to be able to change.

When the BlueZone administrator decides that a BlueZone configuration modification is required, the administrator uses the Web-to-Host Wizard to create one or more dialog-level configuration profiles that are placed on the web server and pushed out to your user community. As each dialog-level configuration profile is downloaded, it overrides specific values stored in each user's top-level configuration profile. All other values stay as they were thus, leaving any user configuration customizations intact.