Fix (APAR):  JR26855

Status:  Fix

Release:  6.0.2.1,6.0.2

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  JR26855

Byte size of APAR:  23828

Date: 2007-06-19

Abstract:  In WPS Event Monitor, the Event Content setting is invalid.

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

ERROR DESCRIPTION:                                              
Release WPS 6.0.2.1                                             
                                                                
If an BPEL process is created with a inline human task and      
EMPTY is specified as content type for an EXIT event in the     
monitoring section and test this application with BPCExplorer   
it can be observed in the Common Base Event Browser that the    
payload type is full and all fields are send there.             
                                                                
Furthermore the expected extension name should be               
                                                                
BPC.BFM.ACTIVITY.STATUS                                         
                                                                
but instead of this the extension name is changed to a different
value, e.g.                                                     
                                                                
BPC.BFM.ACTIVITY.MESSAGE#{http://test/test}Component1./8        

LOCAL FIX:                                                      
n/a                                                             

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.2 users

PROBLEM DESCRIPTION:
In WPS Event Monitor, the Event
Content setting is invalid.

RECOMMENDATION:
None

In WPS Event Monitor, even though EMPTY is specified as Event
Content, BPC.BFM.ACTIVITY.MESSAGE will still emit with payload.

PROBLEM CONCLUSION:                                             
This issue has been fixed by changing the method of creating    
.mon file.                                                      


Directions to apply fix:  
Before applying the iFix ensure that WebSphere Process Server 6.0.1 is installed on the system.
Also 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

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. 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) 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: