Fix (APAR):  PM22371

Status:  Fix

Release:  6.1.1.2

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  6880

Date: 2010-10-07

Abstract:  When deployed from WebSphere CloudBurst Appliance Version 2.0, dynamic cluster server instances are not always started.

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

ERROR DESCRIPTION:                                              
When deployed from WebSphere CloudBurst Appliance Version 2.0,  
dynamic cluster server instances are not always started, even   
though the dynamic cluster is deployed in Automatic mode.       
                                                                
Also, some of the server instances that are not running are     
displayed in the runtime tasks, with the following message:     
DCPC0019I - Application placement controller has not received   
confirmation for the start of server....                        
                                                                
The log files for WebSphere Application Server show that an     
attempt is made to start the server instance before the new     
server definition has been synchronized to all the nodes.       

LOCAL FIX:                                                      
Using the administrative console, manually start any of the     
stopped server instances associated with the dynamic cluster,   
and then stop any unneeded server instances.                    

PROBLEM SUMMARY

USERS AFFECTED:
 All users of WebSphere Application Server
Hypervisor Edition Intelligent Management
Pack Version 6.1.1.2

PROBLEM DESCRIPTION:
When deployed from WebSphere
CloudBurst Appliance Version 2.0,
dynamic cluster server instances are
not always started.

RECOMMENDATION:
None

The configuration changes caused by the Create Dynamic Cluster
script package are not synchronized to the nodes in some
scenarios.

PROBLEM CONCLUSION:                                             
The Create Dynamic Cluster script package has been modified to  
synchronize the configuration changes by way of the deployment  
manager.                                                        
                                                                
This fix will be included in the next available fix pack for    
WebSphere Virtual Enterprise.                                   


Directions to apply fix:  Install Fix to:
__ Application Server Nodes
__ 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 6.1.0.0-WS-WXDOP-IFPM22371.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.1.0.0-WS-WXDOP-IFPM22371.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.1.0.0-WS-WXDOP-IFPM22371.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: