To use multiple language encoding support in the administrative console, configure an application server with UTF-8 encoding enabled.
ResultNote that the autoRequestEncoding option does not work with UTF-8
encoding enabled. The default behavior for WebSphere Application Server is,
first, to check if charset is set on content type header. If it is, then the product uses content type header for character encoding; if it is not,
then the product uses character encoding set on server using the system property default.client.encoding. If charset is not present and the system property is not set, then the product uses ISO-8859-1. Enabling autoRequestEncoding on a Web module changes the default behavior: if charset it not present on an incoming request header, the product checks the Accept-Language header of the incoming request and does encoding using the first language found in that header. If there is no charset on content type header and no Accept language header, then the product uses character encoding set on server using the system property default.client.encoding. As with the default behavior,
if charset is not present and the system property is not set, then the product uses ISO-8859-1.
Related tasks
Creating application servers