Delay B2B Message Processing Until All SOA Composites are Deployed
Last updated on JANUARY 04, 2017
Applies to:Oracle SOA Suite - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
You have a SOA - B2B integration, that consists of the B2B Engine running on the same manged server as SOA with the SOA deployed composites to sending/receiving messages from B2B.
When the B2B managed server is started, the B2B Listening Channels starts polling for messages BEFORE all SOA composites being deployed. B2B Engine processes these messages, and when trying to send to the SOA composite supposed to receive B2B messages, it won't find it (as it's not deployed) so the message will go to the default IP_IN_QUEUE.
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