DESCRIPTION:
Shares the functionality of defining the sequence and conditions in which one service invokes other services in order to realize some useful function.
Based on W3C
https://www.w3.org/TR/ws-arch/
INTEROPERABILITY SALIENCY:
The Orchestration Service ABB is salient for technical interoperability because it provides the functionality of "automated" business processes coordination. The EIF's Conceptual model for integrated EU public services foresees the concept a Coordination for Integrated Service Delivery. The Model comprises an "integrated service delivery" is based on a "coordination function", which is related to SOA principles such as choreography and orchestration, to manage internal business processes in order to remove complexity for the end-user, as stated in the EIF: "The coordination function ensures that needs are identified and appropriate services are invoked and orchestrated to provide a European public service. This function should select the appropriate sources and services and integrate them. Coordination can be automated or manual."
EXAMPLES:
The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB):
Apache ODE
Apache ODE (Orchestration Director Engine) software executes business processes written following the WS-BPEL standard. It talks to web services, sending and receiving messages, handling data manipulation and error recovery as described by your process definition. It supports both long and short living process executions to orchestrate all the services that are part of your application.
http://ode.apache.org/
|
|
| ID | ABB45 |
| dct:publisher | |
| dct:modified | |
| eira:status | [ Exists | Development planned ] |
| eira:reusability | [ Excellent (90-100%) | Very good (70-89,9%) | Fair (50-74,9%) | Poor (0-49,9%) ] |
| eira:actual_use | [ Currently used | Used planned | No ] |
| difi:namespace | eira |
| difi:name_no | Orchestration Service [ns:eira] |
| difi:description_no | DESCRIPTION:
Shares the functionality of defining the sequence and conditions in which one service invokes other services in order to realize some useful function.
Based on W3C
https://www.w3.org/TR/ws-arch/
INTEROPERABILITY SALIENCY:
The Orchestration Service ABB is salient for technical interoperability because it provides the functionality of "automated" business processes coordination. The EIF's Conceptual model for integrated EU public services foresees the concept a Coordination for Integrated Service Delivery. The Model comprises an "integrated service delivery" is based on a "coordination function", which is related to SOA principles such as choreography and orchestration, to manage internal business processes in order to remove complexity for the end-user, as stated in the EIF: "The coordination function ensures that needs are identified and appropriate services are invoked and orchestrated to provide a European public service. This function should select the appropriate sources and services and integrate them. Coordination can be automated or manual."
EXAMPLES:
The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB):
Apache ODE
Apache ODE (Orchestration Director Engine) software executes business processes written following the WS-BPEL standard. It talks to web services, sending and receiving messages, handling data manipulation and error recovery as described by your process definition. It supports both long and short living process executions to orchestrate all the services that are part of your application.
http://ode.apache.org/
|
| difi:name_en | |
| difi:description_en | |
| difi:language | no |
| label | ${name} [ns:${property:difi:namespace}] |
| dct:type | archi:application-service |