The Profile Schemes Feature is used to automatically import Dialog Configuration Profiles. When this feature is used, the values stored in the Dialog Configuration Profile will override certain values stored in the main BlueZone configuration file that was used to start the session.
I say certain values because, by definition, Dialog Configuration Profiles are subsets of the main BlueZone Configuration file. There are up to eight types of Dialog Configuration Profiles that can be used in any combination along with the main BlueZone configuration file.
NOTE This
feature will be used primarily by BlueZone Administrators that use a "push
technology", like Microsoft's SMS, to install and update BlueZone
files on their End User's machines.
If your BlueZone Administrator does not use the Profile Schemes Feature, this feature can be also be useful to End Users.
For example, if you are the type of user that requires many BlueZone configuration files and you make many modifications to those configuration files, you can use the Profile Schemes feature to share Dialog Configuration profiles that are common to all BlueZone configurations.
For example, let's say you regularly use ten different BlueZone configuration files, and the BlueZone keyboard map configuration is the same for all ten configuration files. If this is the case, instead of having to make your specific keyboard map changes to all ten configuration files, you can make the keyboard map changes once and export the keyboard map to a Dialog Configuration Profile. Then you would open the Profile Schemes Tab, place a check in the Keyboard checkbox and browse to the keyboard map file you just created.
Result
You now have a Keyboard map profile that can be shared among all ten BlueZone configuration files. You also have the added benefit of only having to make any future keyboard map changes once. You do not have to update all ten configurations.
First, to understand how the Profile Schemes Feature works, you must have a good understanding of Dialog Configuration Profiles.
SEE Dialog Configuration Profiles located in Configuration Files located in this chapter, for more information.
To configure the Profile Schemes dialog, select File::Properties from the BlueZone MenuBar. Select the Profile Schemes tab. The Profile Schemes dialog will be displayed as shown here:
NOTE
This is
an example of the BlueZone Mainframe Display Profile
Schemes dialog. Other
BlueZone emulation client Profile Schemes
dialogs will look slightly different. However,
the functionality and concepts are the same.
First determine which aspects of the BlueZone configuration you wish to override using the Profile Schemes Feature.
Enable the desired features by placing a check in the corresponding checkbox.
There are two ways to use this dialog:
A) You can leave the file names blank, in which case BlueZone will create a Profile Configuration file (based on your current configuration settings) with the same name as the master BlueZone configuration file, but with the corresponding file extension.
B) You can create you own Dialog Configuration Profiles by going to each Dialog, making your desired customizations, then exporting the changes to a Dialog Configuration Profile using your own naming convention.
Depending on which method you want to use, either leave the file name blank, or use the Browse button to locate the appropriate Dialog Configuration Profile.
Click the OK button to save your choices.
From now on, when this BlueZone Mainframe Display Session launches, BlueZone will apply all the configuration settings stored in the main BlueZone configuration file (.zmd) first, then it will apply the Dialog Configuration Profiles that are enabled (checked) in the Profile Schemes dialog, and override the configuration settings with the values stored in the enabled Dialog Configuration Profiles.
SEE The
BlueZone Dialog Configuration Profile Table
located in the Appendix, for a
complete listing of the Dialog Configuration
Profile file extensions.