This document discusses supporting multiple code sets for HTTP requests and responses in WebSphere Application Server. It describes WebSphere's mechanism for determining the code page of an HTTP request based on: 1) the content-type header, 2) a customizable encoding.properties file mapped to languages, or 3) a default.client.encoding system property. This allows requests and responses to be encoded in different code pages while still supporting Unicode in the application server.

1. 1/82

2. 2/82
Unicode and WebSphereUnicode and WebSphere

3. 3/82
IBM WebSphere PlatformsIBM WebSphere Platforms

4. 4/82
WebSphere Application Server V4.0WebSphere Application Server V4.0
• Java 2 Enterprise Edition V1.2
o Servlet V2.2
o Java Server Pages V1.1
o Enterprise Java Beans V1.1
o JDBC V2.0
o …
• Web Services
o SOAP, UDDI, WSDL
• XML
o XML4J (Xerces V1.2)

5. 5/82
Model of Global WebSphere ApplicationsModel of Global WebSphere Applications
English
French
French in Canada
Web App.
Server A
English
French
Japanese
French in Canada
Korean
Server B Web App.
Server C
- Database
- Messaging
- EJB
- Web Services
Server D
JDBC
IIOP
XML
Korean
Japanese
XML
HTTP
HTTP/
SMTP
HTTP
HTTP/
SMTP

6. 6/82
ConsiderationsConsiderations
• Unicode will be the best solution.
• However, customers still would like to use
traditional code sets because not all web
clients are ready for Unicode.
• Especially for requests and responses
composed of text/html data.
• Also for handling data from data stores.

7. 7/82
GoalGoal
• Easy deployable environment for Unicode-based
J2EE Web application.
• Multiple code set support for HTTP communication
by single Web application server.

8. 8/82
HTTP response and requestHTTP response and request
RESPONSE
REQUEST
GET
POST
REQUEST
RESPONSE
Web Browsers WebSphere
REQUEST
WebServices
UNICODEMULTPLE CODE SETS
REQUEST

9. 9/82
HTTP RequestHTTP Request
• FORM application is processed by the
ServletRequest interface of Servlet.
• ServletRequest.getParameter() family of methods
return parameters’ data from FORM.

10. 10/82
ProblemProblem
• ServletRequest.getParameter() family of
method must return string in Unicode after
transcoding the parameter values from the
code set of the FORM to Unicode.
• There is no reliable way to decide the code
set of the FORM…
However

11. 11/82
Solution used WebSphereSolution used WebSphere
• WebSphere provides a flexible code set
determination mechanism.
• Two customizable properties
o encoding.properties file
o default.client.encoding system property

12. 12/82
encoding.propertiesencoding.properties
#LOCALE=IANA_CHARSET
en=ISO-8859-1
…
th=windows-874
vi=windows-1258
ja=Shift_JIS
ko=EUC_KR
zh=GB2312
zh_TW=Big5
hy=UTF-8

13. 13/82
Code Set Determination for the RequestCode Set Determination for the Request
Step 1
o If content-type of the FORM contains a charset value, use it and
break.
Step 2
o If encoding.properties file contains a pair of language and
charset, use the charset associated with accept-language and
break.
Step 3
o If default.client.encoding contains a charset value, use it and
break.
Step 4
o Use ISO-8859-1.

14. 14/82
Step 1Step 1
• Step 1 will usually fail because charset value is not
usually added to content-type of the FORM.
o Charset supporting:
• Some WAP devices (because of WML specification)
o No charset support:
• Most Browsers for PCs.

15. 15/82
Step 2Step 2
• Step 2 is used for accept-language based multi-
language Web applications.
• Administrator is allowed to customize the code set
in the encoding.properties file.
• Accept-charset cannot be used -- it is not intended
to provide the request encoding.

16. 16/82
Step 3Step 3
• When neither Step 1 nor Step 2 are effective,
Step 3 is used.
Step 4
Step 4 defaults to ISO-8859-1.

17. 17/82
ThankThank You !!!You !!!
For More Information click below link:
Follow Us on:
http://vibranttechnologies.co.in/websphere-classes-in-
mumbai.html