Fix (APAR):  PQ76733

Status:  Fix

Release:  5.0.2

Operating System:  All

Supersedes Fixes:  None



CMVC Defect:  171714

Byte size of APAR:  30545

Date: 2003/07/28

Abstract:  Fix to correct the Process Choreographer configuration after installation of WebSphere Enterprise 5.0.2

Description/symptom of problem:  

1) Symptom:
   --------
   When WebSphere Enterprise 5.0.2 is installed on WebSphere Application Server Enterprise 5.0
   without any interim fixes or fix packs applied, the new Process Choreographer Web client will not start
   if Process Choreographer is already configured.

   Problem:
   --------
   The upgrade step for the business process container does not complete
   (see $WAS_HOME/ProcessChoreographer/bpeupgrade.log).
   When the application server is started, the new Process Choreographer Web client will not start
   because the "/bpe" context root is still in use by the previous version of the Web client.

2) Symptom:
   --------
   When WebSphere Enterprise 5.0.2 is installed on WebSphere Application Server Enterprise 5.0 or 5.0.1 with a
   configured Process Choreographer and a database other than Cloudscape, compensation might fail.

   Problem:
   --------
   The database backend ID for the compensation CMP EJBs is reset to "CLOUDSCAPE_V50_1".

3) Symptom:
   --------
   When WebSphere Enterprise 5.0.2 is installed on WebSphere Application Server Enterprise 5.0 or 5.0.1 where
   Process Choreographer has been configured with the administrative console wizard, the
   previous version of the Process Choreographer Web client is not accessible.

   Problem:
   --------
   The previous version of the Process Choreographer Web client at http://<yourHost>/bpe/old/webclient uses
   an incorrect JNDI name to connect to Process Choreographer.


NOTE:  This interim fix is needed only if you configured the business process container before
       you installed WebSphere Application Server Enterprise 5.0.2.


NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
       The Update Installer can be downloaded from the following link:
       http://www-3.ibm.com/software/webservers/appserv/support/index.html




Directions to apply fix:  

1) Create temporary "Fix" directory to store the jar file:
             UNIX: /tmp/WebSphere/Fix
          Windows: c:\temp\WebSphere\Fix

2) Copy jar file to the directory

3) Shut down WebSphere

4) To install the fix, follow the fix installation instructions that are packaged with the update installer.
   In a federated environment, you need to install this fix only on the deployment manager.

5) Restart WebSphere

6) Remove the temp directory (optional).




Directions to remove fix:  

This fix corrects the configuration of an installed enterprise application and cannot be
removed.



Directions to re-apply fix:  




Additional Information:  
-----------------------

This fix cannot correct the database backend ID (see problem #2 above) in every case. It is
not possible to differentiate between:
   - Sybase 12.0 and Sybase 12.5
   - Oracle 8i and Oracle 9i
   - DB2/390 V6 and DB2/390 V7
   - DB2 UDB for iSeries V4 and DB2 UDB for iSeries V5
   - MS SQL Server V7 and MS SQL Server 2000.

Check the $WAS_HOME/ProcessChoreographer/bpeupgrade.log file to see which database backend ID
was actually used.

When the fix is installed, it selects the latest supported version of the database. That is, if
you are using Sybase 12.0, Oracle 8i, DB2/390 V6, DB2 UDB for iSeries V4, or MS SQL Server V7,
then you must manually set the database backend ID after you have installed the fix.

Go to the $WAS_HOME/ProcessChoreographer directory and run the following command:

Windows:
        ..\bin\wsadmin -conntype none -f bpeupgrade.jacl -backendId <backendId>

Unix:
        ../bin/wsadmin.sh -conntype none -f bpeupgrade.jacl -backendId <backendId>


Replace <backendId> with the desired database backend ID from this list:

  DB2UDBAS400_V4_1
  DB2UDBAS400_V5_1
  DB2UDBNT_V72_1
  DB2UDBOS390_V6_1
  DB2UDBOS390_V7_1
  MSSQLSERVER_V70_1 (MS SQL Server V7)
  MSSQLSERVER_V7_1  (MS SQL Server 2000)
  ORACLE_V8_1
  ORACLE_V9_1
  SYBASE_V125_1
  SYBASE_V12_1

*** END OF README ***