Databases Reference
In-Depth Information
WS-Addressing
To solve these issues, the SOA Suite makes use of WS-Addressing, which provides a
standardized way of including all the address-specific information as SOAP headers
within a SOAP message.
With this approach, the transport protocol is just responsible for delivering the
message to the appropriate binding component, which will then deliver the message
to the Service Infrastructure. This will then route the message to the appropriate
endpoint/service engine.
To demonstrate how WS-Addressing achieves this, let us look at the WS-Addressing
headers the Service Infrastructure inserts into our request and response messages in
the previous example.
Request message with WS-Addressing
The initial request sent by composite A, with WS-Addressing headers inserted, looks
something like the following:
<env:Envelopexmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:ins="http://xmlns.oracle.com/sca/tracking/1.0">
<env:Header>
<wsa:To>http://hostname:8001/soa-infra/services/default/AysncB/
client_ep</wsa:To>
<wsa:Action>http://xmlns.oracle.com/AsyncA/AsyncB/BPELProcessB/
BPELProcessB/process</wsa:Action>
<wsa:MessageID>urn:62772860C2DE8F6A0634D09B</wsa:MessageID>
<wsa:RelatesTo>urn:62772860C2DE8F6A0634D09B</wsa:RelatesTo>
<wsa:ReplyTo>
<wsa:Address>
http://hostname:8001/soa-infra/services/default/AsyncA!1.0*
2fc449a6-fa51-440a-afae-b143d9c26d88/BPELProcessB%23BPEL
ProcessA/BPELProcessB
</wsa:Address>
<wsa:ReferenceParameters>
<ins:tracking.ecid>…</ins:tracking.ecid>
<ins:tracking.conversationId>…</ins:tracking.conversationId>
<ins:tracking.parentComponentInstanceId>…
</ins:tracking.parentComponentInstanceId>
</wsa:ReferenceParameters>
</wsa:ReplyTo>
</env:Header>
<env:Body>
…
</env:Body>
</env:Envelope>
