Fix (APAR):  PK45671

Status:  Fix

Release:  6.0.2

Operating System:  AIX,HP-UX,Linux,Solaris,Windows,z/OS

Supersedes Fixes:  PK44566; PK45272

CMVC Defect:  PK45671

Byte size of APAR:  87718

Date: 2007-06-04

Abstract:  Changes to generic JVM arguments or the debug arguments field on the dynamic cluster server template are not propagated to dynamic cluster members.

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

ERROR DESCRIPTION:                                              
Making changes to the dynamic cluster template will not         
propagate down to the cluster members if the Generic JVM        
argument is used, but other parameters, like Heapsize and such  
would work.                                                     

LOCAL FIX:                                                      
n.a                                                             

PROBLEM SUMMARY

USERS AFFECTED:
All users of WebSphere Application Server
V6.0.2.x also running WebSphere Extended
Deployment V6.0.2.

PROBLEM DESCRIPTION:
Changes to generic JVM arguments or the
debug arguments field on the dynamic
cluster server template are not
propagated to dynamic cluster members.

RECOMMENDATION:
None

When you make a change to generic JVM arguments or debug
arguments field on the dynamic cluster server template
from administration console or using wsadmin scripts, it does
not get propagated to all the dynamic cluster members.

PROBLEM CONCLUSION:                                             
The code was fixed to propagate the changes                     
in the generic JVM arguments or debug arguments field on the    
dynamic cluster server template to all the dynamic cluster      
members.                                                        
                                                                
The fix was made available for the WebSphere Extended           
Deployment V6.0.2 on WebSphere Network Deployment V6.0.2.x      
release. This fix will also be part of WebSphere Extended       
Deployment 6.0.2 fixpack 1. (6.0.2.1)                           


Directions to apply fix:  
Install Fix to:
_X_ Deployment Manager Nodes

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.0.2.2 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 6.0.2.0-WS-XD-IFPK45671.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 (6.0.2.0-WS-XD-IFPK45671.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 (6.0.2.0-WS-XD-IFPK45671.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: