Fix (APAR):                IZ82791

Status:                    Fix

Product:                   WBI

Release:                   6.1.2.3

Operating System:          All operating systems

Supersedes Fixes:          

Pre-requisite Fixes:       IZ58181

Exclusive-requisite Fixes: 

CMVC Defect:               IZ82791

Byte size of APAR:         4022571

Date:                      2010-11-12

Abstract:                  New property available that offers possibilty to retrieve messages by copy when using WPS EJB API.

Description/symptom of problem:
When WPS is configured to use work-manager based navigation, the following use of the BPC EJB API may result in messages or variables showing wrong or null data objects: 
a) The local BPC EJB API is used
b) The input message of a human task or business process is submitted using the local BPC EJB API
c) The input message is used in java code after it has been submitted to BPC for further processing

Reason:
The work-manager based navigation comes with an object cache for efficient read access to data objects. In the scenarios described, without the i-fix, a reference to
the data object in the inter transaction cache is passed to the client making the local EJB calls. 
Later use of the data object may occur by the client code and by the BPC container, which leads to wrong or null data.

There are two new custom properties that control the behavior of the cache (if enabled):

- interTransactionCache.passByReference={true|false}
  If the value of this property is set to 'false' then the returned data will be a copy of the cached object.
  The default value for this property is 'true'. This is equivalent the behavior before this fix is applied.
  
- interTransactionCache.integrityCheck={false|true}  
  If the value of this property is set to 'true' (and if interTransactionCache.passByReference is set 
  to 'true' as well) data objects are checked when they are added or read from the inter transaction cache. 
  If the cached object has been modified by another client a message like the following is 
  written to SystemOut.log:
WARNING: CWWBB0699W: The content of the internal database cache for entity 'com.ibm.bpe.database.ScopedVariableInstanceB' with key '
SVIID                         = _SVI:9028012b.81aa9d26.d03267f6.f2f40003}' is not valid anymore.
 
  The default value for this property is 'false' - only if the server is running in 'development mode' the default
  value is set to 'true'. 


Note that the server must be restarted before the custom property become effective.	   


NOTE: Update installer version 6.1.0.17 or later is required to install this interim fix.

NOTE: This interim fix is applicable to both a full WPS installation as well as a WPS client installation.

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: