Neoview Character Sets Administrator's Guide (R2.4, R2.5)

C Configuring Neoview Client Applications
The Neoview Transporter, Neoview Loader, Neoview ODBC drivers, and Neoview JDBC driver
each provides certain translation functions on client locale character encoding inserted into the
Neoview database and database encoding retrieved by the client workstations. These translations
ensure that client locale character data can be converted, stored in the Neoview database, retrieved,
and converted to the appropriate client locale character encoding without causing mismatch
errors.
This appendix describes how the translation functions behave and must be configured for these
Neoview client applications:
• “How Character Encoding Is Implemented in the Neoview Transporter Client” (page 49)
• “How Character Encoding Is Implemented in the Neoview Loader” (page 52)
• “How Character Encoding Is Implemented in the Neoview ODBC Driver for Windows”
(page 53)
• “How Character Encoding Is Implemented in the Neoview ODBC Drivers for UNIX”
(page 53)
• “How Character Encoding Is Implemented in the Neoview JDBC Driver” (page 54)
Neoview client applications such as Neoview DB Admin or Neoview Command Interface do
not need to be configured.
How Character Encoding Is Implemented in the Neoview Transporter Client
The Neoview Transporter uses the Transporter client, a high-speed Java-based data loader and
extractor, to load and extract data from the Neoview platform. The Transporter client application
manages load and extract operations from Windows, Linux, and HP-UX for Itanium platforms.
This section describes:
• “How Pass-Through Mode and UTF16 Conversion Are Implemented From the Transporter
Client” (page 49)
• “Encoding Data Sources” (page 50)
• “Encoding Control Files” (page 51)
• “Encoding Transporter Client Event and Log File Messages” (page 52)
For more information about the features and capabilities of the Neoview Transporter client for
this Neoview release, see “Neoview Transporter Client” (page 37).
How Pass-Through Mode and UTF16 Conversion Are Implemented From the
Transporter Client
Transporter client encoding of character data from client locales and the Neoview database
consists of these options:
• Whether or not to enforce pass-through mode for incoming character data
• Whether or not to enforce conversion of incoming character data to UTF16 for internal use
in the native Java String format.
Table C-1 (page 50) describes how pass-through mode and UTF16 conversion for the Transporter
client are implemented and interact. The Transporter client does not support ODBC data sources.
How Character Encoding Is Implemented in the Neoview Transporter Client 49