Fix (APAR):  PK18921

Status:  Fix

Release:  5.1.1.8

Operating System:  AIX,HP-UX,Linux,Linux Red Hat - pSeries,Linux zSeries,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  PK18921

Byte size of APAR:  6330

Date: 2006-03-10

Abstract:  Need to add a method to FragmentInfo that will disable automatically appending the method type to the cache-id for GET and POST requests.

Description/symptom of problem:  
PK18921 resolves the following problem:

ERROR DESCRIPTION:                                              
 Portal server needs to be able to                              
set IGNORE-GET-POST.                                            

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
Servlet caching users that have fragments
that implement CacheableServlet and want
to GET and POST requests to that fragment
to generate the same cache-id.

PROBLEM DESCRIPTION:
Need to add a method to FragmentInfo
that will disable automatically
appending the method type to the
cache-id for GET and POST requests.

RECOMMENDATION:
None

Portal in some scenarios does not differentiate between GET
and POST requests.  Since Dynacache automatically appends the
method type to the cache-id duplicate cached content is stored
with two different cache-ids.  Portal needs to be able to
disable this for fragments implementing CacheableServlet.

PROBLEM CONCLUSION:                                             
Added a method to com.ibm.websphere.servlet.cache.FragmentInfo  
that will allow Portal to call setIgnoreGetPost(true) in a      
fragment implementing CacheableServlet.                         
                                                                
The fix for this APAR is currently targeted for inclusion       
in cumulative fixes 5.02.17 and 5.1.1.10 and fixpack 6.0.2.9.   
Please refer to the recommended updates page for delivery       
information:                                                    
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980   

Directions to apply fix:  NOTE: Choose the:
1) Release the fix applies to
2) The Editions that apply
3) Delete the Editions & Methods that do not apply and this Note

Fix applies to Editions:
Release:
5.0  5.1
___  ___ Application Server (Express or BASE)
___      Enterprise Edition (DD)
___  ___ Network Deployment (ND)
___  ___ Edge Components
___  ___ Developers Edition
___  ___ Tools
     ___ WebSphere Business Integration Server Foundation (WBISF)

Install Fix to:
Method:
__ Application Server Nodes
__ Deployment Manager Nodes
__ Both

NOTE:
The user must:
* Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* Be logged in with the same authority level when unpacking a fix, fix pack or refresh pack.

The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

The Update Installer for V5.0 does not have a maintenance directory.
It uses fixpacks and fixes as the location of the unpacked files.

1) Copy PKxxxxx.jar file directly to the maintenance directory

2) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to.

3) Launch Update Installer

4) Enter the installation location of the WebSphere product you want to update.

5) Select the "Install maintenance package" operation.

6) Enter the file name of the maintenance package to install (PKxxxxx.jar file which was copied in the maintenance directory).
The V5.0 and V5.1 fix packs and fixes are unpacked as .jar files and should be unpacked into fixpacks or fixes directory.

7) Install the maintenance package.

8) Restart WebSphere

Directions to remove fix:  NOTE:
* The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED
* DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED
* YOU MAY REAPPLY ANY REMOVED FIX

Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.

1) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against.

2) Start Update Installer

3) Enter the installation location of the WebSphere product you want to remove the fix.

4) Select  "Uninstall maintenance package" operation.

5) Enter the file name of the maintenance package to uninstall (PKxxxxx.jar).

6) UnInstall maintenance package.

7) Restart WebSphere

Directions to re-apply fix:  1) Shutdown WebSphere.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere.

Additional Information: