Fix (APAR):  PK97393

Status:  Fix

Release:  6.1.1,6.1.0.5,6.1.0.4,6.1.0.3,6.1.0.2,6.1.0.1,6.1

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  9922

Date: 2009-10-08

Abstract:  In all versions prior to 6.1.0.5, the default edition metadata is not generated when a profile is augmented for the product.

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

ERROR DESCRIPTION:                                              
Under some conditions the default edition metadata is not       
generated when XD profile augmentation is done on version of XD 
prior to 6105.                                                  

LOCAL FIX:                                                      
none                                                            

PROBLEM SUMMARY

USERS AFFECTED:
 All users of WebSphere Extended Deployment
Version 6.1.0.x

PROBLEM DESCRIPTION:
In all versions prior to 6.1.0.5, the
default edition metadata is not
generated when a profile is augmented
for the product.

RECOMMENDATION:
None

When Websphere Application Server profiles are augmented for
any version of WebSphere Extended Deployment prior to Version
6.1.0.5, the edition metadata might not generate due to
incorrect profile checks.

PROBLEM CONCLUSION:                                             
This fix provides a stand-alone utility that generates the      
default edition metadata for WebSphere Application Server-based 
applications. Complete the following steps to use the utility:  
                                                                
1. Install the fix.                                             
2. Run the <WAS-HOME>/bin/appeditionoperations.py script as     
shown in the following example:                                 
                                                                
<WAS-HOME>/bin# ./wsadmin.sh -lang jython -f                    
appeditionoperations.py createEditionMetadata <profile_name>    
<profile_path>                                                  
                                                                
As a result, the default edition metadata for the profile       
whose name and path are passed as arguments is generated.       
                                                                
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:
NOTE: Developers -  Place and X next to the proper installation method and remove this note
__ 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 6.1.1.0-WS-WXDOP-IFPK97393.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.1.0-WS-WXDOP-IFPK97393.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.1.0-WS-WXDOP-IFPK97393.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: