Fix (APAR):                IY94772

Status:                    Fix

Product:                   WBI

Release:                   6.0.2.0

Operating System:          All operating systems

Supersedes Fixes:          

Pre-requisite Fixes:       

Exclusive-requisite Fixes: 

CMVC Defect:               IY94772

Byte size of APAR:         37170

Date:                      2007-02-16

Abstract:                  DataSource 'jdbc/BPEDB' moved to wrong cluster during WPS 6.0.2 upgrade install.

Description/symptom of problem:

If you upgrade a WPS 6.0.1 Network Deployment environment with the following properties to 6.0.2:

  a) There is at least one cluster where Business Process Choreographer is not configured

  b) AND there is at least one DataSource with JNDI name "jdbc/BPEDB" anywhere in the cell, either
     created manually or as part of a Process Choreographer configuration on a single server

then (one of) the DataSource(s) with JNDI name "jdbc/BPEDB" can be moved to the cluster that does
not have Process Choreographer configured. This results in errors in the Process Choreographer
configuration whose DataSource was moved.

Because the 6.0.2 update installer cannot be replaced, the broken Process Choreographer configuration
must be fixed by following these steps:

  1) Apply this interim fix on the deployment manager installation.

  2) Start the deployment manager.

  3) Go to the deployment manager's WebSphere directory, e.g. "c:\WebSphere\ProcServer".

  3) On Windows platforms, run this command:
       "bin\wsadmin.bat -f ProcessChoreographer\config\bpeupgrade.jacl -profileName <nameOfDmgrProfile>"
     On Unix platforms, run this command:
       "bin/wsadmin.sh -f ProcessChoreographer/config/bpeupgrade.jacl -profileName <nameOfDmgrProfile>"
     Where <nameOfDmgrProfile> denotes the name of the deployment manager's profile, e.g. "Dmgr01".

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: