Database Reference
In-Depth Information
Understanding IDs and ECIDs
To effectively perform transaction monitoring, it helps to understand the differen-
ce between the various IDs. Every composite instance has a unique composite
instance ID, sometimes simply referred to as an instance ID. The instance ID is
a sequential numeric identifier and is the primary means of navigating instances
through the console.
The
Execution Context ID (ECID)
, on the other hand, is a global unique identi-
fier of a particular transaction. As a message is passed from composite to com-
posite, the ECID is passed with each message. This allows for the correlation
of a message across different components even if the message leaves Oracle
SOA Suite 11g and comes back!
An ECID is generated when the request is first processed by Oracle Fusion Mid-
dleware. If it exists, no new ECID is generated. The following is an example of
an ECID:
cb680017c6a0acfe:-606797c4:134357968da:-8000-0000000000001736
In the sample integration design shown in the following screenshot, we have a
BPEL process that produces a message in some external JMS queue. After-
wards, this message is consumed asynchronously by another BPEL process
that passes it on to a Mediator service, which in turn invokes a final BPEL pro-
cess. In this example, each of these components are in their own composite
(that is, the integration consists of a total of four composites).
Each composite instance has its own instance ID (see instance IDs 20008,
20009, 20010, and 20011 in the flow shown in the following screenshot). Upon
the instantiation of the first composite, an ECID is generated. As shown in
