Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 5 Implementation Requirements : Setup and Configuration

Setup and Configuration
The following information describes the requirements for configuring the TIBCO Object Service Broker environment, the keyboard, and the end user display for the use of NLS.
Responsibilities of the Database Administrator
The database administrator is responsible for ensuring that an enterprise is properly enabled for NLS. This involves the following tasks:
Decide which specifications of a TDS code page and a communication code page are appropriate for a peer-connected enterprise. Refer to Restrictions on locale.codepage for the list of valid specifications.
After configuring @NLS1 for each peer, log in to each node as a normal user to validate that NLS initialization completes normally and without errors.
Keyboard Support
NLS supports the full set of Latin-1 keyboard characters as described previously. The ability to exploit the keyboard is dependent upon the host operating system’s ability to recognize these characters. The end user must perform the necessary system configuration or setup to support the national keyboard. Guidelines for each host operating system follow.
Windows
To set up national keyboard support, proceed as follows from the Start Menu:
1.
2.
3.
4.
Choose the national keyboard that most closely matches the one attached to your system (for example, U.S. English, French, or Swedish).
This could require that the original system setup disks or CD-ROM be available to install additional keyboard drivers.
Under Windows, you can reconfigure your keyboard driver dynamically without exiting a session. In this way you can enter multi-national characters from a single keyboard session.
Solaris
Refer to your Solaris documentation regarding exploitation of national keyboards.
z/OS
By default, z/OS display devices attached to conforming display controllers provide identification that defines their supported display code page. NLS uses this code page to configure a suitable mapping between the display code page and the TDS code page. If you are using a 3270 emulator, consult your documentation to determine whether this identification is provided under software control.
If your display device does not provide this support, the TIBCO Object Service Broker initialization assumes that the display code page is the same as the TDS code page. If this is not the case (for example, connecting Swedish EBCDIC devices to a German Data Object Broker), you must provide additional customization. Refer to Changing the EBCDIC Display Code Page.
Display Font Support
To display accented characters, the selected font must be able to display the ASCII code page, or equally, the full national EBCDIC code page:
Windows
Change the text and graphical display client fonts to an ISO8859‑1 font (for example, Courier, Courier New, Fixedsys, Lucida Console, or Modern). The installation default font is Terminal (a DOS font). In addition to choosing an ISO8859‑1 font, consider choosing one that is also fixed‑pitch and TrueType.
Solaris
The default X-Windows display font is typically an ISO8859‑1 font, so no action should be required on your part.
z/OS
Refer to Keyboard Support, specifically the discussion on keyboard support for Windows.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved