Fix (APAR):  JR31384

Status:  Fix

Release:  6.1.2.1,6.1.2

Operating System:  Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  15751

Date: 2009-02-06

Abstract:  When using a dynamic endpoint on a WebService Import, the outgoing SOAP message contains an EndpointReference header element.

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

ERROR DESCRIPTION:?                                             
When a dynamic endpoint is used with the WebService             
Export, the outgoing SOAP message contains an Endpoint          
Reference header.                                               
                                                                
Dynamic endpoint is set through the mediation component by      
setting a value in the SMOHeader/Target/Address field.          
                                                                
                                                                
Later, when this is processed by WebService Import compoonent   
the SOAP message contains an endpoint reference header:         
                                                                
                                                                
   <soapenv:Header>                                             
  <ad:EndpointReference                                         
xmlns:ad="http://schemas.xmlsoap.org/ws/2004/08/addressing">    
    <ad:Address>http://localhost:12345/someService</ad:Address> 
  </ad:EndpointReference>                                       
</soapenv:Header>                                               
                                                                
This is a partial WS-Addressing header used internally by WPS   
and is ignored by many webservice engines, including the        
standard WAS JAX-RPC engine.                                    
                                                                
However, this causes an error with providers such as the WAS    
WebService Feature Pack JAX-WS engine which looks for full      
WS-Addressing headers.                                          
                                                                
The following error is received: org.apache.axis2.AxisFault:    
A required message information header, To, MessageID, or Action,
is not present.                                                 

LOCAL FIX:?                                                     
1) Avoid using dynamic endpoint                                 
                                                                
2) Change webservice provider engines or adjust the webservice  
provider engine so that it ignores the endpoint header or       
remove the header with a webservice handler.                    
                                                                
3) Attempt to modify the .wsdl so that full WS-Addresing headers
are sent.  For WebSphere this is described in this link:        
                                                                
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index     
.jsp?topic=/                                                    
com.ibm.websphere.base.doc/info/aes/ae/twbs_wsa_dep.html        

PROBLEM SUMMARY:?

USERS AFFECTED:
WebSphere Process Server 6.1.2 customers.

PROBLEM DESCRIPTION:
When using a dynamic endpoint on a
WebService Import, the outgoing SOAP
message contains an EndpointReference
header element.

RECOMMENDATION:
None

The EndpointReference header is used internally by WebSphere
Process Server within the Service Component Architecture
message, but since it is a partial WS-Addressing header, it
causes errors with WebService providers. The EndpointReference
header should be removed from the WebService Import in all
cases before the message is serialized into SOAP request.

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: