Fix (APAR):  JR29575

Status:  Fix

Release:  6.1.0.1

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  14879

Date: 2008-06-26

Abstract:  SOAP Header containing Business Objects are serialized incorrectly.

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

ERROR DESCRIPTION:                                              
 BOSerialization issue when place a business                    
object                                                          
in the SOAP header with the SOAP attributes of mustUnderstand   
and actor                                                       
set.The following is the example.                               
**********                                                      
<xs:attribute name="mustUnderstand">                            
  <xs:simpleType>                                               
   <xs:restriction base="xs:boolean">                           
    <xs:pattern value="0|1" />                                  
   </xs:restriction>                                            
  </xs:simpleType>                                              
 </xs:attribute>                                                
 <xs:attribute name="actor" type="xs:anyURI" />                 
***********                                                     
The pattern for serialization needs to be 1 for true and 0 for  
false.but                                                       
what we see on the wire along with when we serialize it manually
it's                                                            
mustUnderstand="true|false'                                     

LOCAL FIX:                                                      
Fix will be provided soon                                       

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server and WebSphere
Enterprise Service Bus 6.0.1.x, 6.0.2.x,
6.1.0.x and 6.1.2 users.

PROBLEM DESCRIPTION:
SOAP Header containing Business
Objects are serialized incorrectly.

RECOMMENDATION:
None

When the SOAP Header contains Business Objects and
"mustUnderstand" attribute is set, Business Objects
serialization sets the attribute values incorrectly as
"true" or "false". The values should be 1 for true and
0 for false.

PROBLEM CONCLUSION:                                             
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: