Fix (APAR):  JR30107

Status:  Fix

Release:  6.1.0.2,6.0.2.5,6.0.2.4,6.0.2.3

Operating System:  AIX,HP-UX,i5/OS,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  66183

Date: 2009-03-03

Abstract:  SOAP Header data not propagated to client side.

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

ERROR DESCRIPTION:                                              
When a SOAP message is sent via a Mediation Module and if the   
Header for that message is updated in a target module , the     
updated header is not reflected in the mediation module during  
response flow.                                                  
                                                                
Ex: If you have a mediation module Y updates a SOAP header A    
to B ,and this module is called via a another mediation         
module X , then during a transaction the modified header is     
not available in Mediation module X during the response flow.   
It will still have the old Header Value.                        

LOCAL FIX:                                                      
None                                                            

PROBLEM SUMMARY

USERS AFFECTED:
Websphere Process Server 6.2.0.x and
6.1.0.x users.
users.

PROBLEM DESCRIPTION:
SOAP Header data not propagated to
client side.

RECOMMENDATION:
None

SOAP header value modified in the down stream modules is not
propagated to the client in a mediation flow.

PROBLEM CONCLUSION:                                             
Header data has to be propagated to the client in a mediation   
flow.                                                           
                                                                
Applying this interim fix will resolve the issue.               


Directions to apply fix:  
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 Process Server.

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

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere Process Server.

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: