Fix (APAR):  PM30808

Status:  Fix

Release:  7.0.0.15,7.0.0.13

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

Supersedes Fixes:  

CMVC Defect:  PM30808

Byte size of APAR:  10538

Date: 2011-05-16

Abstract:  Any file that is in the node synchronization exclusion list is being deleted from the node repository during synchronization after upgrading to 7.0.0.13. This includes the namestor

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

ERROR DESCRIPTION:?                                             
Client has a successful install of fixpack 7.0.0.13 and finds   
that the namestore.xml file has been deleted from the node.     
namestore.xml in the node is used to store persistent bindings. 
The nodeagents systemout.log shows the following entry -        
-                                                               
[12/14/10 18:01:53:609 CET] 00002246 FileRepositor A ADMR0017I: 
User XXXCustomRegistry/wasys deleted document                   
cells/xebk701/nodes/xdaps301_1/namestore.xml                    

LOCAL FIX:?                                                     
By design, the namestore.xml doesn't get synced from dmgr to    
node                                                            
because the master copy is kept at the node level. Therefore    
doing                                                           
subsequent syncNode would not make a difference in this case. If
the                                                             
namestore.xml that is at the dmgr level contains the bindings   
they need,                                                      
they can copy it from dmgr and use it to recover those.         

PROBLEM SUMMARY:?

USERS AFFECTED:
 All V7 WebSphere Network Deployment
customers who use node level persistent
namestore bindings or synchronization
service exclusions.

PROBLEM DESCRIPTION:
Any file that is in the node
synchronization exclusion list is
being deleted from the node repository
during synchronization after
upgrading to 7.0.0.13. This includes
the namestore.xml file which is
automatically in the exclusion list.

RECOMMENDATION:
None

A nodeagent trace will show the file is being deleted, example
log below:
[1/13/11 13:04:20:445 CET] 00000020
NodeSync < invokeGetFolderSyncUpdate
Exit
...
cells/myCell/nodes/myNode/namestore.xml
deleted
cells/myCell/nodes/myNode/xxxxx.xml
deleted
cells/myCell/nodes/myNode/plugin-cfg.xm
l deleted
...
This is only an issue if the file shown above is in the
exclusion list.
Example what to look for in nodeagent.xml for exclusion list
is below:
<fileSynchronizationService
xmi:id="ConfigSynchronizationService_11
62465673595" enable="true"
synchInterval="1"
autoSynchEnabled="true"
synchOnServerStartup="false">
<exclusions>cells/askbpoif01pCell01/nod
es/askbpoif01pNode1/servers/IFsrv01/plu
gin-cfg.xml</exclusions>
</fileSynchronizationService>

PROBLEM CONCLUSION:?                                            
Code was updated to correct this problem.                       
                                                                
The fix for this APAR is currently targeted for inclusion in    
fixpack 7.0.0.17. Please refer to the recommended updates page  
for delivery information:                                       
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980   
.                                                               
*** Note: see APAR PM34232 for the V6.1 equivalent of this fix  


Directions to apply fix:  Fix applies to Editions:
Release 7.0
_X_ Application Server (Express or BASE)
_X_ 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 Application Server.
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 Application Server.

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 Application Server.
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 Application Server.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere Application Server.



Additional Information: