Fix (APAR):  JR32795

Status:  Fix

Release:  6.2.0.1,6.2.0

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  9940

Date: 2009-04-28

Abstract:  After migrating WebSphere Enterpise Service Bus to v6.2 or v6.2.0.1, in network deployment topology, failed events cannot be viewed in the failed event manager.

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

ERROR DESCRIPTION:                                              
After migrating ESB from version 6.1x to 6.2, failed event and  
recovery does not function correctly.                           

LOCAL FIX:                                                      
None                                                            

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Enterprise Service Bus users
migrating to v6.2 or v6.2.0.1

PROBLEM DESCRIPTION:
After migrating WebSphere Enterpise
Service Bus to v6.2 or v6.2.0.1, in
network deployment topology, failed
events cannot be viewed in the failed
event manager.

RECOMMENDATION:
None

After migrating WebSphere Enterprise Service Bus to v6.2 or
v6.2.0.1, in network deployment topology, the exception
destination for the queues, in case of remote messaging
engine, is not setup correctly. It should be setup to the
failed event destination instead it is the default exception
destination.

PROBLEM CONCLUSION:                                             
The application of this iFix will resolve the problem and will  
setup the exception destination of the queues in case of        
remote messaging engine to the failed event destination. Note   
that the application of this iFix is required prior to          
migration.                                                      


Directions to apply fix:  
Download and follow Update Installer installation instructions.  The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

1) Copy the pak file to the directory maintenance in the UpdateInstaller directory

2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

3) Run the UpdateInstaller and follow the prompts.

4) Restart WebSphere Process Server.

Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH 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, then fix2 may be removed

1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere Process Server.

Directions to re-apply fix:  
1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

3) Restart WebSphere Process Server.

Additional Information: