Fix (APAR):  PK56448

Status:  Fix

Release:  6.0.2.1,6.0.2

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

Supersedes Fixes:  

CMVC Defect:  PK56448

Byte size of APAR:  18635

Date: 2007-12-03

Abstract:  Currently, there exists no facility for users to retrieve application edition information from command line.  This iFix resolves the issue by introducing two new commands for this 

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

ERROR DESCRIPTION:                                              
WebSphere Extended Deployment Application Edition               
allows for multiple versions of an application to               
be deployed to a cluster.                                       
                                                                
This APAR allows users to obtain the version of                 
the applications deployed using the WASADMIN                    
scripting tool.                                                 

LOCAL FIX:                                                      
N/A                                                             

PROBLEM SUMMARY

USERS AFFECTED:
Users of WebSphere Extended Deployment
V6.0.2 and V6.1 who want to retrieve
application edition information from
command line, that is via scripting using
the wsadmin tool.

PROBLEM DESCRIPTION:
Currently, there exists no facility
for users to retrieve application
edition information from command
line.  This iFix resolves the issue
by introducing two new commands for
this particular purpose.

RECOMMENDATION:
None

This iFix introduces two new commands so users can retrieve
application edition information via command line.

(1) listEditions:  This command takes in a parameter, appName,
which is the name of the application in question, and it
returns of string array of all the installed editions of the
application.

(2) isEditionExists:  This command takes in two parameters,
appName and edition.  It will test and see if the specified
edition exists for the particular application.  Simple boolean
true or false is returned.


Sample Usage:

wsadmin>AdminTask.listEditions('-appName HelloWorld')

wsadmin>AdminTask.isEditionExists('-appName HelloWorld
-edition 2.0')

PROBLEM CONCLUSION:                                             
With this iFix, users will be able to retrieve application      
edition information from command line using the two new         
commands introduced.                                            
                                                                
The commands will be included in XD 6.0.2.2 and XD 6.1.0.1.     


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.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-IFPK56448.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-IFPK56448.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-IFPK56448.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:  The fix will also ship in XD 6.0.2.2 and XD 6.1.0.1.