Fix (APAR):  JR31697

Status:  Fix

Release:  6.1.2

Operating System:  Linux,Windows

Supersedes Fixes:  

CMVC Defect:  JR31697

Byte size of APAR:  15786

Date: 2009-02-16

Abstract:  When setting the target URL for a Web Service call in the Service Message Object (SMO) headers, if the target is an https:// target, the Web Service import fails to route it approp

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

ERROR DESCRIPTION:?                                             
When setting the target URL for a Web Service call in the SMO   
headers, if the target is an https:// target, the Web Service   
import fails to route it appropriately.                         
                                                                
The same thing works fine with an http:// target.               
                                                                
When the SMO header is https:// the Web service import just     
defaults to the address listed in the import.                   

LOCAL FIX:?                                                     
none                                                            

PROBLEM SUMMARY:?

USERS AFFECTED:
WebSphere Process Server 6.1.0.x, WebSphere
Process Server 6.1.2.x, and WebSphere
Process Server 6.2.0.0 users.

PROBLEM DESCRIPTION:
When setting the target URL for a Web
Service call in the Service Message
Object (SMO) headers, if the target
is an https:// target, the Web
Service import fails to route it
appropriately.

The same thing works fine with an
http:// target.

When the SMO header is https:// the
Web service import just defaults to
the address listed in the
import.

RECOMMENDATION:
None

If an import is using a webservices binding and mediation is
used to route request to URLs starting with https://  ,
then it fails and uses default URL instead of using newly
set https:// URL. Mediation can only route request to
URLs starting with http:// .

PROBLEM CONCLUSION:?                                            
The issue will be resolved in a future fixpack.                 


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: