Conference Paper

Tool support for BPEL verification in ActiveBPEL engine

Software Eng. Inst., East China Normal Univ., Shanghai
DOI: 10.1109/ASWEC.2007.50 Conference: Software Engineering Conference, 2007. ASWEC 2007. 18th Australian
Source: IEEE Xplore


The BPEL is designed for integrating and orchestrating Web services and it provides the profound solution to model business process relying on Web service platform. ActiveBPEL is a commercial-grade open source implementation engine for BPEL. In this paper, we describe the work on tool support for the BPEL verification in ActiveBPEL. We implement the algorithm of the mapping from BPEL to timed automata, and integrate it into the ActiveBPEL. By using model checker UPPAAL engine, ActiveBPEL is enhanced and can verify the BPEL properties, such as deadlock and reachability. Moreover, those timed properties of BPEL specification can be checked in our framework as well. Some case studies are presented to show the usage of verification functionality in ActiveBPEL.

Full-text preview

Available from:
  • Source
    • "Since our approach can be applied to retrieve the reliability expression of virtually any workflow, it can be applied to already existing workflow designing tools, instead of needing the design of new ones, as it was for METEOR. This is verified by applying the concept of reliability patterns to a popular commercial workflow designing tool, namely Active BPEL Designer [9], and enabling an early evaluation of reliability formulas for designed workflows. Even more interestingly, the proposed plug-in can be easy adapted to any WS-BPEL [10] compliant designer. "

    Full-text · Article · Jan 2011 · Journal of Software Engineering and Applications
  • Source
    • "Com o intuito de encontrar alguma técnica de inspeção que possa ser aplicada nesse contexto, uma revisão informal e em seguida uma quasi-revisão sistemática da literatura foram executadas. Estas revisões permitiram encontrar algumas propostas para a verificação de Diagramas de Atividades e outras notações aplicáveis a workflow, tais como [14], [15], [16], [17], [18], [19] e [20]. Entretanto, em sua maioria, estas propostas focam na verificação sintática e automatizada dos modelos, sem qualquer menção a procedimentos que possam orientar um inspetor na realização da revisão e na exploração dos aspectos semânticos do modelo. "
    [Show abstract] [Hide abstract]
    ABSTRACT: The requirements specification of contemporary software applications usually is composed by diverse artifacts describing lots of activities, flows, dependencies among the flows, branches and business rules. For instance, web or scientific workflow (e-science) based applications require structural representations for the various activities and functionalities involved in their execution, usually described trough activity diagrams. The quality assurance of such specifications represents a challenge for software engineers. The results of a quasi-systematic review indicated there is a lack of software technologies to support the inspection of this type of requirements specification. Therefore, in this paper, besides the review results, an inspection technique (checklist) to review Activity Diagrams on the requirements specifications is introduced. A proof of concept on applying the checklist for the inspection of a real requirements specification concerned with a scientific workflow based application indicated some advantages on its defect detection capacity when compared with previously executed ad-hoc inspection by software engineers.
    Full-text · Conference Paper · Nov 2010
  • Source
    • "Again, safety analysis (specified using various properties) can be checked in the tool, but also there is an additional part of the tool, called 'Fiona' which checks for proper interaction models within the orchestrations and details operating guidelines for using each of the services appropriately. There has been some reports of direct editor integration with formal verification tools, such as with the ActiveBPEL tool in [8] which uses the UPPAAL model checker to check safety and timed analysis of orchestrations. The tool makes a good attempt to integrate with source editors yet does not provide the flexibility to work with other analysis tools. "
    [Show abstract] [Hide abstract]
    ABSTRACT: Developing service compositions, using multiple standards and implementation techniques, typically involves specifying service characteristics in different languages and tools. Examples are defining service composition behaviour, in the form of the business process execution language for Web services (WS-BPEL) and a global service choreography policy, in the form of the Web service choreography description language (WS-CDL). Whilst there have been a number of model-based analysis tools reported, there is a lack of integration with development environments to support analysis of these different service artifacts. In this paper we present a short history of some of the analysis tools reported, discuss an appropriate criteria of accessible integrated development with analysis features and provide an example approach, called "service engineer" using our tools and integration work. The approach is supported by an integrated service tool-chain development environment known as the SENSORIA development environment. The aim is to provide an accessible, rigorous approach to analysing service compositions but with a simple, clearly defined interface in an integrated development environment.
    Full-text · Conference Paper · Jul 2008
Show more