Mostrando entradas con la etiqueta servicio compuesto. Mostrar todas las entradas
Mostrando entradas con la etiqueta servicio compuesto. Mostrar todas las entradas

domingo, 10 de mayo de 2009

Coreografía de Servicios

"...does not rely on a central coordinator. Rather, each Web service involved in the choreography knows exactly when to execute its operations and with whom to interact. Choreography is a collaborative effort focusing on the exchange of messages in public business processes. All participants in the choreography need to be aware of the business process, operations to execute, messages to exchange, and the timing of message exchanges". Ver la siguiente figura (fuente: Oracle).


"A technique used to characterize and to compose service-oriented business collaborations based on ordered message exchanges between peer entities in order to achieve a common business goal...Choreography differs from orchestration primarily in that each party in a business collaboration describes its part in the service interaction in terms of public message exchanges that occur between the multiple parties as standard atomic or composite services, rather than as specific service-oriented business processes that a single conductor/coordinator (e.g., orchestration engine) executes"

"...This typically involves use of a standards-based choreography scripting language. An example of such a language is the Web Services Choreography Description Language [WS-CDL]..."

(fuente: OASIS
http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/soa-ra-pr-01.pdf)

Orquestación de Servicios

La Orquestación de Servicios constituye "A technique used to compose hierarchical and self-contained service-oriented business processes that are executed and coordinated by a single agent acting in a "conductor" role...An orchestration is typically implemented using a scripting approach to compose service-oriented business processes."
(fuente:
http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/soa-ra-pr-01.pdf)


"...is usually used in private business processes, a central process (which can be another Web service) takes control of the involved Web services and coordinates the execution of different operations on the Web services involved in the operation. The involved Web services do not "know" (and do not need to know) that they are involved in a composition process and that they are taking part in a higher-level business process. Only the central coordinator of the orchestration is aware of this goal, so the orchestration is centralized with explicit definitions of operations and the order of invocation of Web services". Ver la siguiente figura (fuente Oracle).