Fix (APAR):  PM38178

Status:  Fix

Release:  6.1.1.3,6.1.1.2

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

Supersedes Fixes:  PM27746

CMVC Defect:  PM38178 

Byte size of APAR:  288570

Date: 2011-07-12

Abstract:  A new application edition fails to rollout due to the names of web modules not matching or due to the number of web modules not matching.

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

ERROR DESCRIPTION:                                              
When attempting to roll out a new application edition, the      
operation fails with the message:                               
                                                                
WPVR0013E: Rollout failed because no target or previous edition 
information found for edition x.x of application [app_name].    

LOCAL FIX:                                                      
n/a                                                             

PROBLEM SUMMARY

USERS AFFECTED:
All WebSphere Virtual Enterprise Version
6.1.1.2 and 6.1.1.3 users of application
edition

PROBLEM DESCRIPTION:
A new application edition fails to
rollout due to the names of web
modules not matching or due to the
number of web modules not matching.

RECOMMENDATION:
None

Application editioning functionality was errantly looking for
modules in the new edition that match the name and have the
same number of modules as the old edition.  If the new edition
did the meet the criteria, then the following error will occur
as a symptom of the problem:

A new application edition fails to rollout due to the names of
web modules not matching or due to the number of web modules
not matching.

PROBLEM CONCLUSION:                                             
Application editioning was modified to no longer look for a     
matching number of modules or modules with the same name.       
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 PM38178.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 (PM38178.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: