Fix (APAR): IY95645 Status: Fix Product: WBI Release: 6.0.2.1 Operating System: All operating systems Supersedes Fixes: IY94772 Pre-requisite Fixes: Exclusive-requisite Fixes: CMVC Defect: IY95645 Byte size of APAR: 64330 Date: 2007-03-15 Abstract: Wrong exception destinations set for Business Process Choreographer JMS queues. Description/symptom of problem: 1) Symptom: -------- Under rare conditions it can happen that JMS messages on the BPC..Bus SIBus are found in the system exception destination. 2) Problem: -------- There is no tool available to replay messages from the system exception destination on the BPC SIBus. Since these messages usually are used for navigation of long running business processes, this can cause business processes to hang. 3) Solution: --------- This interim fix solves the described problem. If you install the interim fix and execute bpeupgrade.jacl from the /ProcessChoreographer/config directory, then the definitions of the SIBDestinations used by Business Process Choreographer are modified in such a way that messages from these destinations are no longer moved to the system exception destination in the case of failed delivery. If delivery fails repeatedly, then such messages are moved to the BPEHldQueue from which they can be replayed. For each stand-alone profile where you configured Business Process Choreographer do the following: 1. Go to the /ProcessChoreographer/config directory. 2. Make sure that the application server where Business Process Choreographer is configured is stopped. 3. Do one of the following: - On Windows, run the following command: ..\..\bin\wsadmin -conntype NONE -profileName -f bpeupgrade.jacl where is the name of the profile for which the Business Process Choreographer configuration is to be upgraded. - On UNIX and Linux, run the following command: ../../bin/wsadmin.sh -conntype NONE -profileName -f bpeupgrade.jacl where is the name of the profile for which the Business Process Choreographer configuration is to be upgraded. For each node in a network deployment (ND) environment where you configured Business Process Choreographer on a server that is not a cluster member do the following: 1. Make sure that the deployment manager is running. 2. Make that sure all of the application servers where Business Process Choreographer is to be upgraded are stopped. 3. On the managed node, go to the /ProcessChoreographer/config directory. 4. Do one of the following: - On Windows, run the following command: ..\..\bin\wsadmin -profileName -f bpeupgrade.jacl where is the name of the profile for which the Business Process Choreographer configuration is to be upgraded. - On UNIX and Linux, run the following command: ../../bin/wsadmin.sh -profileName -f bpeupgrade.jacl where is the name of the profile for which the Business Process Choreographer configuration is to be upgraded. For each cluster in a network deployment (ND) environment where you configured Business Process Choreographer do the following: 1. Make sure that the deployment manager is running. 2. Make that sure all of the application servers where Business Process Choreographer is to be upgraded are stopped. 3. On the deployment manager, go to the /ProcessChoreographer/config directory. 4. Do one of the following: - On Windows, run the following command: ..\..\bin\wsadmin -cluster -f bpeupgrade.jacl where is the name of the cluster for which the Business Process Choreographer configuration is to be upgraded. - On UNIX and Linux, run the following command: ../../bin/wsadmin.sh -cluster -f bpeupgrade.jacl where is the name of the cluster for which the Business Process Choreographer configuration is to be upgraded. Directions to apply fix: 1) Copy pak file to the directory maintenance in the UpdateInstaller directory 2) 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. 3) Follow the Fix installation instructions that are packaged with the Fix Installer on how to install the Fix. 4) Restart WebSphere Directions to remove fix: NOTE: 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, then fix2 may be removed 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) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere 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) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Additional Information: