SOA 11g: B2B Does Not Send ebMS SecurityFailure Error Message Back To The Message Service Handler
Last updated on OCTOBER 18, 2016
Applies to:Oracle SOA Platform – B2B (Business to Business) - Version: 220.127.116.11.0 to 18.104.22.168.0 - Release: 11gR1 to 11gR1
Information in this document applies to any platform.
According to the ebMS 2.0 specification it is strongly RECOMMENDED that "the error is reported to the Message Service Handler (MSH) that sent the message in error", in this case with error code "SecurityFailure"
See chapter 22.214.171.124.2 and 126.96.36.199 of http://www.oasis-open.org/committees/ebxml-msg/documents/ebMS_v2_0.pdf
Is there a reason for B2B not to send this error message?
Is it possible for B2B to send this message?
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