Fix (APAR):  PK66432

Status:  Fix

Release:  6.1.0.9,6.1.0.7,6.1.0.5,6.1.0.3,6.1.0.17,6.1.0.15,6.1.0.13,6.1.0.11

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

Supersedes Fixes:  

CMVC Defect:  512058

Byte size of APAR:  20928

Date: 2008-07-18

Abstract:  Unable to get applications deployed on Dmgr

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

ERROR DESCRIPTION:                                              
If an application is deployed on the DMgr, and the Network      
Deployment cell has federated nodes, the                        
ConfigRepoHelper.getEarFileFromBinaries call fails.             

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
 IBM WebSphere Process Server users of
version 6.1.

PROBLEM DESCRIPTION:
Unable to get applications deployed
on Dmgr

RECOMMENDATION:
None

WebSphere Process Server registers application update
listeners for any application updates. At runtime it looks at
the application being updated. If it determines that is a
Service Component Architecture(SCA) module application, it
take certain actions else it ignore the update event.

In a Network Deployment enviornment, when the isclite
application is updated, WebSphere Process Server
receives the update event, and when it tries to process
it, it fails with error
"Cannot instantiate earfile for: isclite.ear"

The Application Server API invoked by WebSphere Process Server
to the EARFile object was designed NOT to return the EARFile
object from binaries location in Network Deployment
enviornments assuming that the binaries location could be
remote to the Dmgr server. But in this case the application was
isclite, which was deployed on the Dmgr and the binaries
location was local to Dmgr, so the API should be able to get
the EARFile object from the binaries location.

PROBLEM CONCLUSION:                                             
In the fix, the API is redesigned to return the EARfile object  
in case of Base enviornments and in Network Deployment          
enviornments, if the application is deployed on the Dmgr server.
                                                                
The fix for this APAR is currently targeted for inclusion in    
fix pack 6.1.0.19.  Please refer to the Recommended Updates     
page for delivery information:                                  
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980   


Directions to apply fix:  
Fix applies to Editions:
Release 6.0
_Y_ Application Server (Express or BASE)
_Y_ Network Deployment (ND)

Install Fix to:
Method:
_Y_ Application Server Nodes
_Y_ Deployment Manager Nodes
_Y_ Both

NOTE:
The user must:
* Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* 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.

The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

For detailed instructions to Extract the Update Installer see the following Technote:
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400

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).

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.
* 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: