Last updated on MARCH 21, 2017
Applies to:Oracle Service Architecture Leveraging Tuxedo (SALT) - Version 12.2.2 and later
Information in this document applies to any platform.
INFO: Oracle SALT, Version 22.214.171.124.0, 64-bit, Patch Level 002
INFO: Oracle Tuxedo, Version 126.96.36.199.0, 64-bit, Patch Level 013
When attempting to request Tuxedo services as webservices through SALT errors occur parsing the SOAP header.
There is no need to parse the SOAP Header and have tried not to by explicitly setting the mapsoadheader property to false did not help.
(mapsoapheader and headerMapping properties are both false by default) The client application is not sending any data in the header.
Three Tuxedo services are exposed as WS using SALT. A Weblogic Server requests the SOAP services and, in the request of the services, the following error is displayed in the ULOG file of SALT domain:
Tracing turned on: GWWS_TRACE_LEVEL=200 and TMTRACE=ws:ulog:
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