Saturday, 17 November 2012

SOA Invoke

1. 
The client posts the message to the delivery service.
2.
The delivery service saves the invocation message to the invoke_message table.
The initial state of the message is 0 (undelivered).
3.
The delivery service schedules a dispatcher message to process the invocation
message asynchronously. The JTA transaction commits, persisting the invocation
message to the database. Recovery and High Availability Oracle BPEL Process Manager

4. The dispatcher message is delivered to the dispatcher through the
afterCompletion()
call. Therefore, the message is not delivered if the JTA  transaction fails.

5.
The dispatcher sends the JMS message to the queue. The message is picked up by

MDB.
6.
MDB fetches the invocation message from the dispatcher.

7.
MDB passes the invocation message to Oracle BPEL Server, which updates the
invocation message state to  1 (delivered), creates the instance, and executes theactivities in the flow until a breakpoint activity is reached.

No comments:

Post a Comment