1 / 7

Dynamism in BPEL

This document discusses the necessity of dynamism in BPEL (Business Process Execution Language) workflows for improving fault tolerance, resource optimization, and responsiveness to real-time events. It explores various approaches to fostering dynamism, including modifying workflow definitions and instances, utilizing middleware for message redirection, and dynamic binding. Though BPEL itself lacks sufficient dynamism, insights are provided on frameworks like TRAP/BPEL and ScyFlow that enhance dynamic adaptation in composite services. Key considerations, challenges, and advancements in the context of workflow orchestration are also covered.

koren
Télécharger la présentation

Dynamism in BPEL

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Dynamism in BPEL Onyeka Ezenwoye Latin American Grid project. Monday, August 28, 2006

  2. The need for Dynamism • Fault Tolerance • Network failure, resource availability, etc • Optimization • Responsiveness to real-time events, resource scheduling, etc • Variations in user input • Multiple configurations for experiments.

  3. Approaches to dynamism(1) • Fool the System • Actions are performed outside the control of the workflow. • Workflow unaware of changes. • Usually through some middleware • Message redirection, dynamic binding • May use high-level policy • E.g. TRAP/BPEL [1]

  4. Approaches to dynamism(2) • Modify running workflow instance • Task may be cancelled, delegated or redirected. • Other instances of the same workflow are not affected. • Usually requires some dependency list and/or policy specification • E.g. ScyFlow [2], TRIANA [3]

  5. Approaches to dynamism(3) • Modify workflow definition • New behaviour specified in Workflow definitions. • May migrate running instances to new ones. • Migration requires careful management • Difficult to encapsulate every possible orchestration response. • Administrative overhead.

  6. BPEL and dynamism • BPEL is NOT dynamic! • Adequate semantics (pick, skip tasks) • Hierarchical but not modular. • May implement process as several interacting workflows (cumbersome). • Minimal fault handling. • Supports compensation handling. • Dynamism through middleware • application, messaging.

  7. References • Onyeka Ezenwoye and S. Masoud Sadjadi. Trap/bpel: A framework for dynamic adaptation of composite services. Technical Report FIU-SCIS-2006-06-02. • Karen M. McCann et. al.; ScyFlow: An Environment for the Visual Specification and Execution of Scientific Workflows. • Matthew Shields and Ian; Taylor Programming Scientific and Distributed Workflow with Triana Service. • Niels Joncheere et. al; Requirements for an Aspect Oriented Workflow system for Grid Services. • Fabio Casati; A Discussion on Approaches to Handling Exceptions in Workflows. • Rashid Hamadi et. al.; Recovery Nets: Towards Self-Adaptive Workflow Systems.

More Related