Decouple child instances from parent instance tree in SOA 11g
Last updated on AUGUST 17, 2017
Applies to:Oracle SOA Suite - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Qn1:There is a composite A which is internally calling composite B in a loop. Composite B is in turn calling composites C, D and E which are again calling composites inside. Can be separated the threads of child process from parent tree so that it can be see individually?
Qn2:Is it needed to put this property ("tracking.ecid") on both Invoke and Receive activity while calling asynchronous child bpel from parent bpel?
Qn3:If it is needed to put the property "tracking.ecid" on both Invoke and Receive activity while calling asynchronous child bpel from parent bpel, then ECID on both Invoke and Receive should match?
Qn4:Will this property ( "tracking.ecid") cause any issues while calling asynchronous child bpel from parent bpel in a loop and in a FlowN/ForEach activity?
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