The Oracle SOA Suite provides an Audit Trail monitor screen where the message flow between the different SCA composites can be tracked. Depending on the audit level, it can provide a very detailed chronology of the different states of the message, including the first component that receives the messages, its correspondent transformation along the way, and the routing it’s final destination. Nevertheless, a SOA platform is intended to integrate not only internal composites but also external components. The question is how to maintain the audit trail consistency in such scenarios?
The Oracle A-team posted a very helpful blog demonstrating how to propagate the ECID between JCA adapter calls in order to maintain the audit trail consistency. This blog is going to demonstrate how to achieve this result with JAXWS web services.
As the reader might have already figured it out, the key to this problem relies with the ECID. The execution context id (ECID) is the mechanism the SOA Suite uses to keep track of the messages as it passes between the different components. If an SCA calls another one, it will pass through the ECID, helping the audit trail to correlate the different component instances into one flow. Also, if instead of a SCA composite a JAXWS web service, the ECID will be passed in the SOAP header, more specifically in the ReplyTo element: Read the complete article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.