Profile schemes are used in conjunction with the dialog-level configuration profiles. It is important to understand the difference between the top- and dialog-level configuration profiles and how they work with profile schemes.
The main BlueZone configuration profile if referred to as the top-level configuration profile. Top-level 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 so on. Having all of these settings in a single file provides a simple way to deploy preconfigured BlueZone sessions to your users. 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 extensions for a complete list of the top-level configuration profile file extensions.
BlueZone dialog-level configuration profiles contain a subset of the Top-level configuration file settings based on a specific dialog. If a configuration dialog contains toolbar icons at the bottom of the window, it supports dialog-level configuration settings. For example, the .tn3 profile scheme contains all settings that can be changed in the TN3270 Properties dialog. Each emulator type has a slightly different list.
Users can customize and save their local configuration profiles.
To modify the configuration for all users, the administrator can use the Web-to-Host Wizard to create one or more dialog-level configuration profiles on the web server and push them out to the users. The dialog-level configuration profile overrides specific values stored in each user's local top-level configuration profile. All other values stay the same, leaving any user configuration customizations intact.