Fix (APAR):  PM45008

Status:  Fix

Release:  6.1.1.4,6.1.1.3,6.1.1.2

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  89499

Date: 2011-10-18

Abstract:  Application editions that are installed on dynamic clusters that were converted from static clusters can not be validated.

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

ERROR DESCRIPTION:                                              
Adding support for Application Edition with static clusters that
have been upgraded to Dynamic Clusters.                         

LOCAL FIX:                                                      
N/A                                                             

PROBLEM SUMMARY

USERS AFFECTED:
 All WebSphere Virtual Enterprise
Application Edition users

PROBLEM DESCRIPTION:
Application editions that are
installed on dynamic clusters that
were converted from static clusters
can not be validated.

RECOMMENDATION:
None

Validation mode clones a target server or cluster to test an
application edition.  However, dynamic clusters that were
converted from static clusters could not be cloned.  An
excpetion similar to the following occurs:
java.lang.Exception: The application edition is associated
with unmanaged deployment target(s).  This is an invalid and
unsupported configuration.
at
com.ibm.ws.xd.appeditionmgr.helpers.CloneHelper.clone(CloneHelpe
r.java:185)
at
com.ibm.ws.xd.appeditionmgr.mbean.ApplicationEditionManager.vali
dateEdition(ApplicationEditionManager.java:586)

PROBLEM CONCLUSION:                                             
Changes were made to enable converted dynamic clusters to be    
cloned, which allows validation mode to function for            
applications installed on dynamic clusters that are converted   
from static clusters.                                           
                                                                
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
_x_ Deployment Manager Nodes
__ 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 PKxxxxx.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 (PKxxxxx.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 (PKxxxxx.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: