Templates for terminal settings

Overview: templates

Terminal settings of the menu system, the toolbar, the keyboard, and the mouse can be very extensive and are therefore summarized in templates. Users can select an appropriate scheme, adjust the scheme to their individual requirements and save the scheme on the server if you have granted them write permission through user administration.

By contrast, the basic settings are valid for all terminals and cannot be modified by your users.

The terminal settings depend largely on the host system and the terminal type, as well as user preferences. The settings are therefore sorted and stored in subdirectories in the configuration directories of the file system.

• By access priority: User - group - custom - basic settings
• By terminal type: 3270, 5250, 9750, xterm/vt, 97801
• By template type: Menu system, toolbar, keyboard settings and mouse settings.

From a technical point of view, templates are standardized macros (JavaScript files) that can be easily created and modified using special editors (designed for this purpose).

Templates of the basic configuration config

Like all configuration directories, the basic configuration config contains a separate TERMINAL subdirectory for every terminal type:

• The directory config/3270 contains special templates
  for the IBM 3270 terminal family (IBM mainframes).
• The directory config/5250 contains special templates
  for the IBM 5250 terminal family (IBM /AS400 Systems).
• The directory config/9750 contains special templates
  for the SNI 9750 terminal family (FSC BS200/OSD).
• The directory config/vt contains special templates
  for the UNIX/Linux terminal families xterm and DEC VTxxx.
• The directory config/97801 contains special templates
  for the Sinix terminal family SNI 97801 (FSC Sinix).

The terminal-specific directories have the same structure and contain an individual subdirectory with a "standard template" default.js for each template type:

• Keyboard settings and mouse settings in the file config/TERMINAL/keyboard/default.js
• The toolbar in file config/TERMINAL/toolbar/default.js
• Menu items in the file config/TERMINAL/menu/default.js
• Depending on the requirements, the auto start directory can contain additional terminal-specific files, for example for PCO handling for 5250 terminals.

Editing templates

You usually edit the templates the same way as your users:

• Start the terminal emulation.
• Using a menu item in the emulation window, start editing the keyboard setting and mouse settings, the toolbar or the menu system.
• In the editor, select the item to be edited in the editor, for example by clicking a menu item or a toolbar item or by pressing the key or mouse button to be set.
• Select the new function from an overview list and assign it.
• Knowledge of LogWeb/Ajax API is only required in special cases.
• If necessary, you can undo all steps of the editing process.
• As a last step, save the source code generated by the editor in your user directory or group directory as a JavaScript file on the server .

If you have set the attribute

_ChangeGroup = true

and want to edit the templates of any user group, you can select your group membership directly when starting the terminal emulation in order to edit the individual templates of the selected group.

Copying template files

If required, you can manually copy a template file from a user directory or group directory to another directory or delete it from a directory.

Note the following when changing the directory structure directly on the server:

• Make sure that you do not change the existing directory strucure.
• Due to the cache, only changes to user data are immediately applied.
• All other changes are only applied when the Web application is restarted.
• Alternatively, you can regenerate the cache during operation.