Reliable Messaging for BPEL Processes

Charfi, Anis; Schmeling, Benjamin; Mezini, Mira

doi:10.1109/icws.2006.111

Cited by 9 publications

(14 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…However, Web Service specifications such as WS-Security and WS-Reliability are based upon SOAP and WSDL, and thus do not cover the security and reliable messaging requirements of BPEL processes. In fact, some middleware concerns are inherently related to BPEL constructs and must therefore be dealt with at the BPEL level [16][17][18]. We have already explained in Section 2 why persistence and auditing in BPEL processes have to be addressed at the BPEL level rather than in underlying middleware.…”

Section: Ao4bpel Middleware Concerns and The Web Service Stackmentioning

confidence: 99%

“…the ordered delivery of messages that belong to messaging activities and go to different partners in a sequence [18]. To illustrate this requirement, consider a sequence activity that contains two one-way (or asynchronous) invoke activities, which call two different partners.…”

Section: Ao4bpel Middleware Concerns and The Web Service Stackmentioning

confidence: 99%

“…These middleware services provide support for non-functional properties of the composition such as security, persistence, and reliable messaging. In two other papers [17,18], we describe a security service and a reliable messaging service that illustrate how aspects can be used to secure and make reliable the interactions between partners in a Web Service composition. A second application is presented in [14], where AO4BPEL aspects are used to implement business rules [82] in the context of Web Service composition.…”

Section: Related Workmentioning

confidence: 99%

“…For each process, we also have to add a new partner link for the counting Web Service (line 3) and a variable (line 5) to be used as input by the new invoke activity. In order to assign the correct value to that variable (the input parameter of the operation increaseCounter), we use an assign activity that is put together with the invoke activity into a sequence activity (lines [11][12][13][14][15][16][17][18][19][20] The discussion so far illustrates how the data collection for billing is a crosscutting concern. The BPEL code addressing that concern is scattered across several processes.…”

Section: Case Studiesmentioning

confidence: 99%

“…Assume that these operations return a string result with the vacation package information, the flight information, or accommodation information. The advice (lines [16][17][18][19][20][21][22][23][24][25][26][27][28][29][30][31][32][33][34][35]) is a sequence activity that executes before the join point activity. At the beginning of the advice, the input parameters of the car rental Web Service are taken from the parent process using the context collection variable ThisProcess(clientrequest) (line 20).…”

Section: Listing 6 the Aspect For Monitoring Execution Timementioning

confidence: 99%

See 4 more Smart Citations

AO4BPEL: An Aspect-oriented Extension to BPEL

2007

Self Cite

View full text Add to dashboard Cite

Process-oriented composition languages such as BPEL allow Web Services to be composed into more sophisticated services using a workflow process. However, such languages exhibit some limitations with respect to modularity and flexibility. They do not provide means for a well-modularized specification of crosscutting concerns such as logging, persistence, auditing, and security. They also do not support the dynamic adaptation of composition at runtime. In this paper, we advocate an aspect-oriented approach to Web Service composition and present the design and implementation of AO4BPEL, an aspect-oriented extension to BPEL. We illustrate through examples how AO4BPEL makes the composition specification more modular and the composition itself more flexible and adaptable.

show abstract

Section: Ao4bpel Middleware Concerns and The Web Service Stackmentioning

confidence: 99%

Section: Ao4bpel Middleware Concerns and The Web Service Stackmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Case Studiesmentioning

confidence: 99%

Section: Listing 6 the Aspect For Monitoring Execution Timementioning

confidence: 99%

See 3 more Smart Citations

AO4BPEL: An Aspect-oriented Extension to BPEL

2007

Self Cite

View full text Add to dashboard Cite

show abstract

Aspect-Oriented Workflow Languages

Charfi

Mezini

2006

On the Move to Meaningful Internet Systems 2006: CoopIS, DOA, GADA, and ODBASE

Self Cite

View full text Add to dashboard Cite

Erklärung: Hiermit erkläre ich, daß ich die vorliegende Arbeit selbstständig und unter ausschließlicher Verwendung der angegebenen Quellen und Hilfsmittel angefertigt habe. Darmstadt, den 12. Dezember 2006To my parents,To my wife, To my brother and my sister AcknowledgmentsFirstly, I would like to thank sincerely my advisor Prof. Dr. Mira Mezini for giving me the chance to work in her team, for her support and guidance during the three years of my PhD work, and for providing valuable feedback on early drafts of this thesis. I am also grateful to Prof. Dr. Gustavo Alonso for being the second advisor of this dissertation.Moreover, I thank the German Science Foundation (DFG) for supporting this work in the framework of the research school on Electronic Commerce at Darmstadt University of Technology. I also thank the Tunisian Ministry of Higher Education for having supported my previous studies in Computer Science at Munich University of Technology.In addition, I am indebted to all my colleagues at the Software Technology Group and at the Aspect-Oriented Programming Group for the excellent and productive working environment. I thank Gudrun Jörs for her continuous support.I am also grateful to Tom Dinkelaker, Slim Kallel, Vaidas Gasiunas, Sven Kloppenburg, and Michael Eichberg for proof-reading parts of this thesis and/or for giving feedback on the dissertation talk. Thanks also to Prof. Dr. Klaus Ostermann, who allowed me to reuse the Latex template of his dissertation.My students Andreas Heizenreder, Benjamin Schmeling, and Leo Shang contributed to the work described in this thesis by implementing some parts of the process container framework and the AO4BPEL engine in the context of their diploma thesis.Last but certainly not least, I thank deeply my family for their infinite support. I am indebted to my dear parents who encouraged me to study abroad and to pursue my doctoral studies. I owe much of this success to my wife for her support during the difficult time of writing this thesis. I thank my sister and my brother for their love. AbstractThis thesis focuses on the modularity of workflow process specifications. In particular, it studies the expression support for crosscutting concerns and workflow changes in current workflow languages and workflow management systems. To illustrate the issues, two workflow languages are considered: a visual graphbased language and the Web Service composition language BPEL.This thesis starts by describing the implementation of several crosscutting concerns such as data collection for billing, activity execution time measurement, and security in typical processes of a travel agency. When examining the resulting workflow specifications, the following observations are made.First, the workflow constructs that implement a crosscutting concern cannot be encapsulated in a separate module with a well-defined interface. They are rather scattered across the specifications of several workflow processes. Second, the workflow specifications that result after adding the implementation of a cro...

show abstract