How To Configure GWWS To Prevent TPURCODE From Passed Back In SOAP Header
Last updated on FEBRUARY 22, 2017
Applies to:Oracle Service Architecture Leveraging Tuxedo (SALT) - Version 12.1.3 and later
Information in this document applies to any platform.
User upgraded from SALT 11g to SALT 12c. After the upgrade, the SALT component is now passing back TPURCODE in the SOAP header. This caused all user's web service client to fail as they transform the SOAP response to web service specific XML using XSLT, and it does not know how to map TPURCODE.
Is there anyway to prevent SOAP header from passing back "TPURCODE" ?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms