B2B 11g - Conversation ID Between Inbound/Outbound Messages Cannot be Set by Backend
Last updated on JANUARY 15, 2014
Applies to:Oracle B2B (Business to Business) - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Inbound and Outbound messages need to be under the same conversation. Binary Messages also need to be related. This must be achieved by:
a. Setting correlation between B2B messages when possible
b. Setting the value of b2b.replyTo=<InboundMessageId> and MessageType=1 on the outbound message
Conversation ID between messages needs to be supported between inbound and outbound messages. This will allow to correlate inbound and outbound messages using the Conversation Id.
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