WebSphere Application Server Network Deployment, Version 6.0.x   Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
             [TIP: Focusing the table of contents and search results]

Working with locales and character encodings

Internationalization support for this product relies on that provided by the Java™ 2 Platform, Standard Edition (J2SE). Support varies by platform.

Procedure

Results

If your application produces an UnsupportedEncodingException exception, check your operating system documentation to determine if the target operating system supports the required encoding and adjust the runtime environment as needed.

Example [Windows]

For example, on the Windows® platform, the command prompt runs in a Windows code page. Not all Windows code pages are supported by the Java platform, so it is possible to get a Java exception when running a command-line program, such as wsadmin, in an unsupported code page. To avoid exceptions, use the chcp command to explicitly set the code page to an encoding that is supported by the Java platform.
  • Before command-line calls, change the code page.

    For example, Arabic code page 720 is not supported by the Java platform, but the Arabic code page for Windows (Cp1256) systems is. Type chcp 1256

  • When starting a localized application from a command prompt, set the console.encoding property.

    For Arabic, pass the following parameter: -Dconsole.encoding=Cp1256




Related concepts
Globalization
Related tasks
Task overview: Globalizing applications
Related reference
Language versions offered by this product
Globalization: Resources for learning
Task topic    

Terms of Use | Feedback

Last updated: Mar 8, 2007 8:14:28 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tin_regions.html

© Copyright IBM Corporation 2006. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)