A system administrator can define custom key mappings for use in the QAD .NET UI’s terminal mode.

Use an XML file to define the key mappings. Name the file keymapping.xml and place it in the directory defined by the HomeServer configuration value, which is defined at installation time. (The HomeServer configuration value is typically TomcatInstallDir/webapps/qadhome.) The system identifies the keymapping.xml file through the <TerminalKeyMapUrl> element in the client session configuration file. If the element is not in the file by default, you must add it.

For example, in the client session configuration file, you can add a <TerminalKeyMapUrl> element and set it to ${HomeServer}/keymap.xml as follows:

The keymapping.xml file includes a <KeyMapping> element that includes one or more <KeyMap> elements, whose key and value attributes define a key mapping.

In this example, the keymapping.xml file directs the number pad keys "/" and "*" to act as F1 and F4 keys in terminal mode:

For a listing of possible key settings, see Microsoft Developer Network’s  .NET Framework Class Library for Key Enumeration (http://msdn2.microsoft.com/en-us/library/system.windows.forms.keys(vs.71).aspx).

The following table lists the possible value settings: