Fix (APAR):  PK79287

Status:  Fix

Release:  7.0.0.1

Operating System:  AIX,HP-UX,IBM i,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,OS/400,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  571494

Byte size of APAR:  55065

Date: 2009-05-05

Abstract:  Partial update does not update the application correctly

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

ERROR DESCRIPTION:                                              
Partial application update does not update the application      
correctly.                                                      
                                                                
1. Create a partial zip update to add a file, update a file     
and remove an existing file, for example add a/b/foo.xml,       
update test.xml, delete dummy.txt                               
                                                                
2. run application update partial                               
                                                                
3. The application is updated in the configuration but the      
expanded binaryURL location did not get updated correctly       
                                                                
delta file contents show                                        
<?xml version="1.0" encoding="UTF-8"?><app-delta>               
<change_input changetype="fg-update" contenttype="partialapp"   
operation="update"/>                                            
<files>                                                         
<file operation="update" uri="a/b/foo.xml"/>                    
<file operation="update" uri="test.xml"/>                       
</files>                                                        
</app-delta>                                                    
                                                                
where it should be:                                             
                                                                
<?xml version="1.0" encoding="UTF-8"?><app-delta>               
<change_input changetype="fg-update" contenttype="partialapp"   
operation="update"/>                                            
<files>                                                         
<file operation="add" uri="a/b/foo.xml"/>                       
<file operation="update" uri="test.xml"/>                       
<file operation="delete" uri="dummy.txt"/>                      
</files>                                                        
</app-delta>                                                    
                                                                
Note that foo.xml was not added and test.xml was not deleted,   
which was wrong.                                                

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
 All users of WebSphere Application Server
V7.0

PROBLEM DESCRIPTION:
Partial update does not update the
application correctly

RECOMMENDATION:
None

After partial update, the delta file shows operation="update"
when a new file is added and doesn't show operation="delete"
when a file is deleted. In addition, the application from the
expand binary URL location (that is, installedApps) is not
updated correctly.

PROBLEM CONCLUSION:                                             
In ServiceIndexServerTask, it called CommonUtil.getMergeEar to  
merge the ear file. This should not be called because at this   
point, the appmgmt framework already merged the ear. The extra  
getMergetMergeEar causes multiple updates and results in an     
incorrect application ear file after update. The fix is to      
remove the getMergeEar call in ServiceIndexServerTask.          
                                                                
The fix for this APAR is currently targeted for inclusion in    
fixpack 7.0.0.3.  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 7.0
_X_ Application Server (Express or BASE)
__ Network Deployment (ND)
__ Edge Components
__ Developer

Install Fix to all WebSphere installations unless special instructions are included below.

Special Instructions: None

NOTE:
The user must:
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V7.0.0.0 or newer of the Update Installer. Certain iFixes may require a newer version of the Update Installer and the Update Installer will inform you during the installation process if a newer version is required. 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

1) If your iFix is delivered as a single file with a .pak extension, Copy the .pak file directly to the maintenance directory. If your iFix is delivered as a single file with a .zip extension, unzip the file into 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) For IBM i users, use the update command to install and uninstall the interim fix.  The IBM Information Center can provide additional details, if needed, on the use of this command. 
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=rins_update.
For non-IBM i users, launch the Update Installer and click the Next button on the Welcome page.

4) Enter the directory path of the installation location of the WebSphere product you want to update, and click the Next button.

5) Select the "Install maintenance package" operation and click the Next button.

6) Enter the directory path of your maintenance directory where you have the maintenance packages (.pak files) and click the Next button.

7) The Available Maintenance Package to Install page should list all maintenance packages (.pak files) that it finds in the directory path provided in the previous step.  The Update Installer will select the correct maintenance packages based on your system configuration and will not allow an invalid combination to be installed.  Please keep the Update Installer recommendations and click the Next button and continue with the installation of the maintenance package.  To determine why some maintenance packages have been identified as not applicable, see description in log found in <UPDI_root>/logs/tmp*/updatelogs.txt

8) For all platforms except Windows. In pre-install summary panel, use the "verify permission" feature to verify the user has permissions to apply updates to files associated with the selected maintenance.  Correct any file permissions before clicking next to start the install.

9) 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: