eFix (APAR): PQ55222
Status:      testFix

For Release: WebSphere 4.0.1

For Operating System: all

CMVC defect: PQ55222

Included defects: 

Byte size of APAR: 862,214  bytes

Date: 11/27/01

Abstract: HTTPTRANSPORT DOES NOT HANDLE CUSTOM STATUS CODES


Description/symptom of problem: 
Custom HTTP status codes are not handled by the HTTPTransport


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/PQ55222 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/PQ55222).

2) Shutdown WebSphere

3) Run the backup jar file with the following command:
   java -jar PQ55222_Test_AEsServer_AEServer.jar

4) Restart WebSphere

5) To enable view the additional information provided below.


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.