AW: [service-orientated-architecture] Re: Orchestration, Choreography , and Composition

Mon, 31 Jul 2006 01:11:34 -0700

Sometimes customers are asking for some "auto-magic" between two business processes that takes care of the mismatch between them.  In certain situations you can generate what is called in the literature a "process mediator", i.e. a third business process (another orchestration, e.g. as an executable BPEL process) that performs the buffering of messages.
 
Obviously, such a process mediator does not always exist. Even if it exists it can not always be automatically generated.  A specification of the appropriate "wires" between the processes may then solve the mismatch: This is one nice example of specifying a choreography.

----- Ursprüngliche Mail ----
Von: Ashley at Metamaxim <[EMAIL PROTECTED]>
An: [email protected]
Gesendet: Mittwoch, den 26. Juli 2006, 10:35:11 Uhr
Betreff: Re: [service-orientated-architecture] Re: Orchestration, Choreography , and Composition

Patrick wrote:
 
>> Whether this approach is suitable or appropriate in the business
>> processes context I do not know.

> Yes, that is more my question. I would not expect this to be part of a
> business-level "choreography" .
 
On reflection I think that, fun though it is, the kind of buffering solution I suggested would be unwise in the context of business processes. For instance, if you have messages whose semantics are dependent on their context in the exchange, you could have nasty results.
 
I think that the formulation of a choreography for the collaboration should ensure that the abstract processes of the participants are compatible. If the sequence of message exchanges then violate the choreography, this should be handled manually as an exception situation.
 
Rgds
Ashley

__._,_.___


SPONSORED LINKS
Computer software Computer security software Computer software program
Computer fax software Computer virus software

YAHOO! GROUPS LINKS



__,_._,___

Reply via email to