General Administration

I18N - Background Installation Information

 

Background Installation Information

 
  • Oracle Database
    For all environments NLS_LANG has to be set to AMERICAN_AMERICA.AL32UTF8.

    In new environments NLS_LANG is set to AMERICAN_AMERICA.AL32UTF8.
    In this environment a character conversion is performed by the Oracle library (preferred method).
  • Java Client
    The Java Client (and all other Java ECI clients) scans the configuration parameter EDB-CHR-ENC-JVM for a standard environment (currently set to UTF-8).
    Each user in an I18N environment needs to configure a proper font that is able to display non-Latin characters.
  • Web Client
    Same as Java Client. Additionally, the encoding defined in the webplm properties file need to be adapted to use UTF-8 instead of ISO-8859-x in an I18N environment.
  • EDM Server
    Three new configuration entries exist to control how characters are mapped from the client to the database charset:
    • If EDB-EPQ-USE-CHAR-CONVERSION is active the EPQ performs the client side character set conversion.
    • If EDB-EPQ-USE-SUBST-CHARACTER is set invalid characters will be replaced with a substitution character. Otherwise, an error message is issued and the conversion is canceled.
    • If EDB-EPQ-SUBST-CHARACTER is set its content is used as substitution character. Otherwise, the ICU's default substitution character (usually 0x1a) is used.
    In the standard dump the character conversion is deactivated. This configuration is needed when upgraded dumps are used because they can contain illegal characters (e.g. €).