Fix (APAR):  PK70710

Status:  Fix

Release:  6.0.2.2,6.0.2.1

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  PK70710

Byte size of APAR:  116305

Date: 2008-09-11

Abstract:  The On Demand Configuration component does not process the cloneID override value set via the HttpSessionCloneId custom property.

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

ERROR DESCRIPTION:?                                             
The On Demand Configuration ignores HttpSessionCloneID custom   
properties which should override the clone value in the On      
Demand Configuration tree.                                      

LOCAL FIX:?                                                     

PROBLEM SUMMARY:?

USERS AFFECTED:
All users of WebSphere Extended Deployment
trying to override the cloneID value
of a server via the HttpSessionCloneId
custom property

PROBLEM DESCRIPTION:
The On Demand Configuration component
does not process the cloneID override
value set via the HttpSessionCloneId
custom property.

RECOMMENDATION:
None

The On Demand Configuration component should use the value
stored in the HttpSessionCloneId custom property as the
cloneID for a server, when that value is set.  Currently it
does not.

PROBLEM CONCLUSION:?                                            
The On Demand Configuration component will be updated to utilize
 the HttpSessionCloneId custom property value as the cloneId for
 a server, when the value is set.                               
                                                                
Please refer to the Recommended Updates page for delivery       
information:                                                    
http://www.ibm.com/support/docview.wss?rs=3023&uid=swg27005709  


Directions to apply fix:  
Install Fix to:
_X_ Application Server Nodes
_X_ Deployment Manager Nodes
_X_ Both

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

DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
The Fix 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.

Customers must be at V6.1.0.17 or newer of the Update Installer.  This can be checked by reviewing the level of the Update Installer in file <was_root>/updateinstaller/version.txt.

1) Copy PK70710.pak 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 (PK70710.pak 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.

NOTE:  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 (PK70710.pak).

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: