Neoview Character Sets Administrator's Guide (R2.3)

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 on the Neoview Transporter Java Client” (page 43)
• “How Character Encoding Is Implemented on the Neoview Loader” (page 47)
• “How Character Encoding Is Implemented on the Neoview ODBC Driver for Windows”
(page 47)
• “How Character Encoding Is Implemented on the Neoview ODBC Driver for UNIX”
(page 47)
• “How Character Encoding Is Implemented on the Neoview JDBC Driver” (page 48)
Neoview client applications such as Neoview DB Admin or Neoview Command Interface do
not need to be configured.
How Character Encoding Is Implemented on the Neoview Transporter Java
Client
The Neoview Transporter uses the Java Client, a high-speed Java-based data loader and extractor,
to load and extract data from the Neoview platform. The Java 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 Java Client”
(page 43)
• “Encoding Data Sources” (page 44)
• “Encoding Control Files” (page 46)
• “Encoding Java Client Event and Log File Messages” (page 46)
For more information about the features and capabilities of the Neoview Transporter Java Client
for this Neoview release, see “Neoview Transporter Java Client” (page 31).
How Pass-Through Mode and UTF16 Conversion Are Implemented From the Java
Client
Java 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 44) describes how pass-through mode and UTF16 conversion for the Java Client
are implemented and interact. The Java Client does not support ODBC data sources.
How Character Encoding Is Implemented on the Neoview Transporter Java Client 43