|
Problem |
MustGather for problems with the WebSphere® Application
Server i18n/DBCS component. Gathering this information before calling IBM®
support will help familiarize you with the troubleshooting process and
save you time. |
|
Solution |
In general, i18n/Internationalization/DBCS calls are
slightly different from other related calls. Troubleshooting these
problems can be focused into two broad areas, Character Output and
Character Input:
- Character Output problems are associated with JavaServer
Pages™ (JSP™) that cannot display characters that are either hard coded
into the body of a JSP or HTML page, or are pulled from some datasource.
An example: The Euro symbol doesn't show up in a JSP on Solaris™, or
Korean characters show as question marks. These problems are handled
initially by creating a simple testcase.
- Character Input issues are almost always more complex and
challenging to solve than Output problems. This type of problem can
involve POST values/Request headers, JDBC™ drivers as well as Database
settings and configuration. Test cases are of little to no use since the
problem is a complex interaction within the specific environment. For this
class of problems, a servlet engine trace and reproduction of the problem
is often the best (and only) place to start problem determination.
One type of problem can often be mistaken as a character output problem:
When a JSP cannot display characters taken from a database. A testcase
will often be inconclusive. This can indicate that the problem is with the
data stored in the database. This can be confirmed by checking the data
directly.
If you have already contacted support, continue on to the
component-specific MustGather information. Otherwise, click: MustGather:
Read first for all WebSphere Application Server products.
i18n/DBCS specific MustGather information
- Create a simplified testcase of your problem. Confirm that the test
does indeed fail on your system.
- Collect the following:
- For all releases of WebSphere:
- Stdout, Stderr, tracefile, as well as any logs that
capture servlet or JSP output.
- For UNIX® systems, value of LOCALE settings.
- For WebSphere V5.0, V5.1 and V6.0:
- The application ibm-web-ext.xmi file.
- For character input issues:
- A detailed description of your database configuration,
included JDBC driver level.
- A ServletEngine/WebContainer trace
Finally, a trace might be necessary at a later time. If it is convenient
to capture a ServletEngine/WebContainer trace when recreating the problem,
it could reduce time to resolution. You can find information in the below
"Related information" section for ServletEngine and WebContainer trace on
V4,
V5
and V6.
Follow instructions to Submitting
Diagnostic Information to IBM Technical Support for Problem
Determination.
For a listing of all technotes, downloads, and educational materials
specific to the i18n/Internationalization/DBCS component, search the WebSphere
Application Server support site. |
|
|