Fix (APAR):  JR27292

Status:  Fix

Release:  6.0.1.6

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  5015

Date: 2007-09-11

Abstract:  The BO XML serialization result is changed, after upgrading to WebSphere Process Server 6.0.1.6.

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

ERROR DESCRIPTION:                                              
After a customer upgraded their                                 
production env from WPS 6.0.1.3 to WPS 6.0.1.6, they encountered
a serious problem of message format change.                     
With the same BO schema ( named MUA_ResponseType ), the output  
XML message was changed. The code running on process server     
V6.0.1.6 has optional fields added to the xml message,ie        
codeshareInfo xsi:nil="true", however, the same code running on 
V6.0.1.3 doesn't do this. This change influenced customer's     
service.                                                        
                                                                
Customer logged the BO instance by                              
BOXMLSerializerImpl.writeDataObject(DataObject dataObject,      
                                      String rootElementURI,    
                                      String rootElementName,   
                                      OutputStream outputStream)
                                                                
In 6013, if the element's minOccurs attribute equals 0, and the 
element value is null/unset, this element will not appear in    
output stream. But in 6016, the element will occur with         
attribute "xsi:nil=ture".                                       
                                                                
<xs:element name="FFPorResSessionID" type="xs:string"           
minOccurs="0">                                                  

LOCAL FIX:                                                      
No local fix                                                    

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server and WebSphere
Enterprise Service Bus 6.0.1.6 users

PROBLEM DESCRIPTION:
The BO XML serialization result is
changed, after upgrading to WebSphere
Process Server 6.0.1.6.

RECOMMENDATION:
None

After upgrading to WebSphere Process Server 6.0.1.6, the BO
XML serialization result is changed. If the element value is
set to null or unset, the xsi:nil="true" attribute is shown
for this element in serialization result.

PROBLEM CONCLUSION:                                             
This problem has been fixed by removing a previous regression   
fix.                                                            


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: