Fix (APAR):  PK67582

Status:  Fix

Release:  6.1.0.13

Operating System:  AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux zSeries,OS/400,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  PK67582

Byte size of APAR:  4917

Date: 2008-06-19

Abstract:  Migration of a federated node fails during syncNode operation. The installation of the CEI 6.1 application and the uninstall of the CEI 6.0 application are not updating the sererin

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

ERROR DESCRIPTION:                                              
This is opened against Common Event Infrastructure(CEI)         
component in WebSphere Application Sever.                       
                                                                
-CEI Code review indicated a potential problem due nodeSync     
operation starting before CEI applications were uninstalled .   
                                                                
- The plugin startup for Application Server V6.1 migration and  
CEI plugin code are using the same startup weight of 1000.      
                                                                
This will cause the ordering algorithm to be affected by the    
output from OSGI, which will default to the sort order of the   
jar files in the plugins directory (or its reverse).  This would
explain why Windows and Linux might see different behaviors     
because the default sort algorithms for Windows is alphabetical,
and for Linix/Unix it is by timestamps.                         

LOCAL FIX:                                                      
NA                                                              

PROBLEM SUMMARY

USERS AFFECTED:
 Users on Linux machines who are migrating
from WebSphere Process Server or WebSphere
Application Server with Common Event
Infrastructure (CEI) installed, from
Version 6.0 to version 6.1.

PROBLEM DESCRIPTION:
Migration of a federated node fails
during syncNode operation. The
installation of the CEI 6.1
application and the uninstall of the
CEI 6.0 application are not updating
the sererindex.xml file by the time
the syncNode is called and this is
causing syncNode to fail.

RECOMMENDATION:
None

The serverindex.xml file is not updated
with the new CEI 6.1 application. The old
6.0 CEI applications are still listed in
the xml file even if they were uninstalled
and removed from the system. During the
syncNode operation an exception is thrown
because the applications are listed but
the ears are not found on the system.

PROBLEM CONCLUSION:                                             
This is a timing issue. CEI migration code has been delayed     
so that syncNode and the install and uninstall CEI operations   
are not in conflict.                                            
                                                                
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:  
NOTE: Choose the:
1) Release the fix applies to
2) The Editions that apply
3) Delete the Editions & Methods that do not apply and this Note

Fix applies to Editions:
Release 6.0
__ Application Server (Express or BASE)
__ Network Deployment (ND)
__ WebSphere Business Integration Server Foundation (WBISF)
__ Edge Components
__ Developer
__ Extended Deployment (XD)

Install Fix to:
Method:
__ Application Server Nodes
__ Deployment Manager Nodes
__ 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: