Status:      This is a efix 

For Release: WebSphere 4.0, 4.0.1

For Edition: WebSphere AE, AEs

For ContainerTypes: AEServer, AEsServer

For Operating System: ALL

Supersedes eFixes:  NONE

CMVC defect: PQ52029

Byte size of APAR: 15K

Date: 09/26/01

Abstract: The input values are being returned as garbage by the servlet engine for certain languages.

Fix : A new system property  called client.encoding.override has been introduced which can be used to override any 
client preferences for parsing the input values.This new property should be specified instead of the system property 
default.client.encoding on the JVM settings of the AppServer to be absoulutely sure that the correct encoding is used to 
parse the input values.

Instructions for applying the System Property :

For Advanced Editon Single the following steps need to be performed :

1) Open WebSphere Application Server Administrative Console: (default: http://localhost:9090/admin)
2) Login
3) Open nodes
4) Select Node
5) Open Application Servers
6) Select Application Server
7) Open Process Definition
8) Select JVM Settings
9) In the Advanced Settings: Select System properties hyperlink.
10) In the system properties add the following..
   name=client.encoding.override value=encoding
11) Stop and restart the server.  Note: <WAS_ROOT>/bin/startserverbasic will not make use of the JVM system properties. Run startserver instead

For Advanced Edition the following steps need to be performed :

1) On the WebSphere Administrative Console go to Nodes --> Application Server ---> JVM settings.
2) There will be a section called System Properties. Click on the Add button. A new row will be added to the table.
3) Specify the system property and the corresponding value in the new row. Apply the changes.
4) Restart the AppServer. 


Directions to apply efix:

1) Create temporary "efix" directory to store the zip/tar file:
             AIX: /tmp/WebSphere/efix
   Solaris/Linux: /tmp/WebSphere/efix
         Windows: c:\temp\WebSphere\efix

2) Copy zip/tar file to the directory
   
3) Unzip/untar the file

4) Shutdown WebSphere

5) Run the jar file with the following command answering questions/prompts as they appear:
   java -jar <jarfile name>

6) Restart WebSphere

7) The temp directory may be removed but the zip/tar file should be saved.  Do not remove 
   any files created and stored in the <WASHOME>/WebSphere/AppServer/efix/<APAR#> directories.
   These files are required if an efix is to be removed.



Directions to remove an efix:

NOTE:  EFIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE AN EFIX UNLESS
       ALL EFIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED EFIX.

Example:  If your system has efix1, efix2, and efix3 applied in that order and efix2 is to be
          removed, efix3 must be removed first, efix2 removed, and efix3 re-applied.


1) Change directory to the efix location (<WASHOME>/WebSphere/AppServer/efix/<APAR#>).

2) Shutdown WebSphere

3) Run the backup jar file with the following command:
   java -jar <backup_APAR#>

4) Restart WebSphere



Directions to re-apply an efix:

Follow the instructions for applying an efix.  If the backup files still exist (from the 
previous efix application), you will be prompted to overwrite.  Answer "yes" at the overwrite 
prompts.


Trouble shooting
--------------------------------------------------------------------------------------
o  If an efix complains about the container type and you are sure it should match, contact
   WebSphere L2 Support for assistance with the -SkipContainerCheck option to the efix jar.

o  If the efix complains about the version of XML parser, move the file 
   $WASROOT/jre/lib/ext/xerces.jar to a temporary location (such as c:\temp), load the efix 
   and move the file back to it's original location.



Additional Information:
------------------------------------------------------------------