TroubleShooting: i18n (Internationalization)/Double Byte Character Set (DBCS)
 Technote (FAQ)
 
Problem
Troubleshooting problems with the WebSphere® Application Server i18n/DBCS component. This should help address common issues with this component before calling IBM® support and save you time.
 
Solution

1. Learning more 2. Troubleshooting 3. Collecting data

Steps to help resolve i18n/DBCS problems
  1. Are DBCS characters being used in an unsupported place?
  2. Is the locale set incorrectly? The LC_ALL and LANG environment variables determine this for UNIX® systems. For Solaris, it must be set different than the OS default value.
    • Yes, set it to an appropriate value for the languages you are working with. The en_US.UTF-8 will work for most languages.

    • No, continue to the next question.

  3. Is the application using the system default locale to output its text?
    • Yes, modify the application to set the locale on the OutputStream.

    • No, continue to the next question

  4. Is the application using the system default locale to input its text?
    • Yes, Setclient.encoding.override=UTF-8. There are instructions here.

    • No, continue to What to do next.

What to do next
If the preceding troubleshooting steps did not help solve your problem, see the MustGather for i18n/DBCS problems to continue investigation.
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Double Byte Character Set (DBCS)
Operating system(s): Windows
Software version: 6.1
Software edition:
Reference #: 1244451
IBM Group: Software Group
Modified date: Sep 28, 2006