Towards a Reusable Fault Handling in WS-BPEL

2014 ◽  
Vol 24 (02) ◽  
pp. 243-267
Author(s):  
Andrej Kocbek ◽  
Matjaz B. Juric
Keyword(s):  
Business Process ◽  
Real World ◽  
Service Oriented Architecture ◽  
Proof Of Concept ◽  
Fault Handling ◽  
Process Implementation ◽  
Service Oriented ◽  
Definition Of ◽  
Process Complexity ◽  
Bpel Processes

Service Oriented Architecture (SOA) is an evolution of distributed computing and it is based on the concepts of interoperable services. To enable reliable and robust service oriented information systems, it is important to establish an effective fault handling. WS-BPEL 2.0 specification does not provide sophisticated and reusable support for handling faults and challenges process designers with many obstacles in the process implementation. We introduce a novel policy driven fault handling framework for BPEL by extending the WS-BPEL 2.0 specification. We propose to separate business process and fault handling logic with the aim to decrease code duplication, process complexity and overall process size. The proposed framework consists of a fault policy which includes the definition of BPEL fault handling logic. The fault policy defines fault handlers and fault handling recovery actions that can be used to design handling BPEL process faults. As a proof-of-concept, we have developed a prototype implementation of the proposed policy driven fault handling framework for BPEL and tested it on 117 real world BPEL scenarios. We have confirmed that the proposed solution decreases the code duplication, the process complexity and overall the process size. Even more, we successfully improved the reliability and readability of BPEL processes.

Challenges and Solutions for Complex Business Process Management

2011 ◽  
pp. 1060-1080
Author(s):  
Minhong Wang ◽  
Kuldeep Kumar
Keyword(s):  
Business Process ◽  
Resource Selection ◽  
Business Process Management ◽  
Process Management ◽  
Service Oriented Architecture ◽  
Object Oriented Programming ◽  
Complex Processes ◽  
Computing Technologies ◽  
Service Oriented ◽  
Process Complexity

A business process displays complexity as a result of multiple interactions of its internal components and interaction between the process and its environment. To manage complexity and foster flexibility of business process management (BPM), we present the DCAR architecture for developing complex BPM systems, which includes decomposition of complex processes (D); coordination of interactive activities (C); awareness of dynamic environments (A); and resource selection and coordination (R). On the other hand, computing technologies, such as object-oriented programming, component-based development, agent-oriented computing, and service-oriented architecture have been applied in modeling and developing complex systems. However, there is considerable ambiguity involved in differentiating between these overlapping technologies and their use in developing BPM systems. No explicit linkage has been established between the requirement of complex BPM and the supporting technologies. In this study, we use the DCAR architecture as the foundation to identify the BPM requirements for employing technologies in developing BPM systems. Based on an examination of the both sides (BPM requirements and supporting technologies), we present a clear picture of business process complexity with a systemic approach for developing complex BPM systems by using appropriate computing technologies.

Challenges and Solutions for Complex Business Process Management

2010 ◽  
pp. 1-22 ◽  
Author(s):  
Minhong Wang ◽  
Kuldeep Kumar
Keyword(s):  
Business Process ◽  
Resource Selection ◽  
Business Process Management ◽  
Process Management ◽  
Service Oriented Architecture ◽  
Object Oriented Programming ◽  
Complex Processes ◽  
Computing Technologies ◽  
Service Oriented ◽  
Process Complexity

A business process displays complexity as a result of multiple interactions of its internal components and interaction between the process and its environment. To manage complexity and foster flexibility of business process management (BPM), we present the DCAR architecture for developing complex BPM systems, which includes decomposition of complex processes (D); coordination of interactive activities (C); awareness of dynamic environments (A); and resource selection and coordination (R). On the other hand, computing technologies, such as object-oriented programming, component-based development, agent-oriented computing, and service-oriented architecture have been applied in modeling and developing complex systems. However, there is considerable ambiguity involved in differentiating between these overlapping technologies and their use in developing BPM systems. No explicit linkage has been established between the requirement of complex BPM and the supporting technologies. In this study, we use the DCAR architecture as the foundation to identify the BPM requirements for employing technologies in developing BPM systems. Based on an examination of the both sides (BPM requirements and supporting technologies), we present a clear picture of business process complexity with a systemic approach for developing complex BPM systems by using appropriate computing technologies.

Event-Driven Service-Oriented Architectures for E-Business

2010 ◽  
pp. 952-962
Author(s):  
Olga Levina ◽  
Vladimir Stantchev
Keyword(s):  
Distributed System ◽  
Enterprise Architecture ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Reference Architecture ◽  
Service Oriented Architectures ◽  
Application Systems ◽  
Event Driven ◽  
Service Oriented ◽  
Definition Of

E-Business research and practice can be situated on following multiple levels: applications, technological issues, support and implementation (Ngai and Wat 2002). Here we consider technological components for realizing business processes and discuss their foundation architecture for technological enabling. The article provides an introduction to the terms, techniques and realization issues for eventdriven and service-oriented architectures. We begin with a definition of terms and propose a reference architecture for an event-driven service-oriented architecture (EDSOA). Possible applications in the area of E-Business and solution guidelines are considered in the second part of the article. Service-oriented Architectures (SOA) have gained momentum since their introduction in the last years. Seen as an approach to integrate heterogeneous applications within an enterprise architecture they are also used to design flexible and adaptable business processes. An SOA is designed as a distributed system architecture providing a good integration possibility of already existing application systems. Furthermore, SOA is mostly suitable for complex and large system landscapes.

Convergence of Interoperability of Cloud Computing, Service Oriented Architecture and Enterprise Architecture

2013 ◽  
Vol 4 (1) ◽  
pp. 43-51
Author(s):  
Susan Sutherland
Keyword(s):  
Cloud Computing ◽  
Enterprise Architecture ◽  
Service Oriented Architecture ◽  
Proof Of Concept ◽  
Cloud Computing Service ◽  
Architectural Model ◽  
Service Oriented ◽  
State Of Art ◽  
Dynamic Links

The research identifies the gap that there is a convergence of interoperability of Cloud Computing (CC), Service Oriented Architecture (SOA) and Enterprise Architecture (EA). Furthermore, it outlines the existing non dynamic links between EA and SOA that are currently practiced in the industry and confirmed by scholarly articles; and provides a state of art of the link that could exist in practice between cloud computing and SOA as researched from the published scholarly material. This researched paper also refers to the planned research to test this theory first by developing a logical architectural model of such a feasibility followed by a Proof of Concept

Agile Business Objects Management Application for Electronic Records Archive Transfer Process

2009 ◽  
Author(s):  
Quyen L. Nguyen ◽  
Betty Harvey
Keyword(s):  
Business Process ◽  
Process Management ◽  
Service Oriented Architecture ◽  
Electronic Records ◽  
Industry Standards ◽  
National Archives ◽  
Technology Age ◽  
Service Oriented ◽  
Core Components ◽  
Business Objects

In order to continue to fulfill its mission in the information technology age, the National Archives and Records Administration (NARA) has made the decision to develop the Electronic Records Archives (ERA) system. One of the goals is to provide to the archivists a modernized system with automatic workflow that can streamline the digital archive business process. For an archival system, Ingest is one of the core components. As part of the ingest process, this component would allow the record Producer to negotiate submission agreement before transferring digital materials into the system. Within the framework of a service-oriented architecture with business process management, the ERA system uses XML to represent business objects and metadata. In this paper, we will show how the synergetic combination of XForms and Genericode makes the system agile and responsive to business user requirements. Furthermore, the approach fits well with ERA's design principle to use international and industry standards, and facilitates the integration of XML business objects and the electronic records metadata. We believe that the standard-based approach of XForms+Genericode exposed in this paper can be generalized to develop any e-Forms system with a set of control values and vocabularies.

Community Medical Management System Based on SOA

2014 ◽  
Vol 539 ◽  
pp. 349-354
Author(s):  
Shu Juan Zhang
Keyword(s):  
Business Process ◽  
Service Provider ◽  
Medical Management ◽  
Management System ◽  
Service Oriented Architecture ◽  
Treatment Plan ◽  
Business Management ◽  
Customer Management ◽  
Service Oriented ◽  
Design Idea

When the business process changes, the traditional community medical management system needs to change. But SOA is based on service oriented architecture and separates the service provider and service participants, which makes the system flexible. The paper analyzes and designs the subsystem including customer management, general clinic, business management, case management and treatment plan according to the design idea of service provider and service participants in SOA system. So the community medical management system based on SOA has great reference for community medical management system in other cities.

Behavioral Attestation for Web Services Based Business Processes

2010 ◽  
Vol 7 (3) ◽  
pp. 52-72 ◽  
Author(s):  
Masoom Alam ◽  
Mohammad Nauman ◽  
Xinwen Zhang ◽  
Tamleek Ali ◽  
Patrick C. K. Hung ◽  
...  
Keyword(s):  
Business Process ◽  
Trust Management ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Trusted Computing ◽  
Business Services ◽  
Dynamic Composition ◽  
Open Set ◽  
Service Oriented ◽  
Root Of Trust

Service Oriented Architecture (SOA) is an architectural paradigm that enables dynamic composition of heterogeneous, independent, multi-vendor business services. A prerequisite for such inter-organizational workflows is the establishment of trustworthiness, which is mostly achieved through non-technical measures, such as legislation, and/or social consent that businesses or organizations pledge themselves to adhere. A business process can only be trustworthy if the behavior of all services in it is trustworthy. Trusted Computing Group (TCG) has defined an open set of specifications for the establishment of trustworthiness through a hardware root-of-trust. This paper has three objectives: firstly, the behavior of individual services in a business process is formally specified. Secondly, to overcome the inherent weaknesses of trust management through software alone, a hardware root of-trust devised by the TCG, is used for the measurement of the behavior of individual services in a business process. Finally, a verification mechanism is detailed through which the trustworthiness of a business process can be verified.

Ontologically Enhanced RosettaNet B2B Integration

2011 ◽  
pp. 782-808
Author(s):  
Paavo Kotinurmi ◽  
Armin Haller ◽  
Eyal Oren
Keyword(s):  
Business Process ◽  
Building Block ◽  
Service Oriented Architecture ◽  
Xml Schema ◽  
Web Ontology Language ◽  
Ontology Language ◽  
Service Oriented ◽  
Setup Phase

RosettaNet is an industry-driven e-business process standard that defines common inter-company public processes and their associated business documents. RosettaNet is based on the Service-oriented architecture (SOA) paradigm and all business documents are expressed in DTD or XML Schema. Our “ontologically-enhanced RosettaNet” effort translates RosettaNet business documents into a Web ontology language, allowing business reasoning based on RosettaNet message exchanges. This chapter describes our extension to RosettaNet and shows how it can be used in business integrations for better interoperability. The usage of a Web ontology language in RosettaNet collaborations can help accommodate partner heterogeneity in the setup phase and can ease the back-end integration, enabling for example more competition in the purchasing processes. It provides also a building block to adopt a semantic SOA with richer discovery, selection and composition capabilities.

Sign in / Sign up

Export Citation Format

Share Document