Colombo: Lightweight middleware for service-oriented computing

Curbera, Francisco; Duftler, Matthew J.; Khalaf, Rania; Nagy, William A.; Mukhi, Nirmal; Weerawarana, Sanjiva

doi:10.1147/sj.444.0799

Cited by 48 publications

(37 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…BPEL engines such as Colombo [58] and Oracle BPEL Process Manager [143] use policies to define the non-functional properties of Web Service interactions.…”

Section: Using Policiesmentioning

confidence: 99%

“…Colombo Colombo [58] is a light-weight platform for developing, deploying, and executing service-oriented applications. It was developed at IBM Research.…”

Section: Using Policiesmentioning

confidence: 99%

“…Colombo [58] is a light-weight platform for service-oriented applications, which supports transactional, reliable, and secure Web Service interactions. The messaging-level requirements are expressed indirectly by attaching policies to local copies of the WSDL files of partner Web Services.…”

Section: Work On Non-functional Concerns In Bpelmentioning

confidence: 99%

“…The survey reveals that only a few recent BPEL engines [52,58,169] provide support for the expression and enforcement of messaging-level requirements. Process-level requirements such as interacting with a partner using a secure conversation and multi-party ordered message delivery are not supported in all currently available commercial and Open Source BPEL engines.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Aspect-Oriented Workflow Languages

Charfi

Mezini

2006

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

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

“…BPEL engines such as Colombo [58] and Oracle BPEL Process Manager [143] use policies to define the non-functional properties of Web Service interactions.…”

Section: Using Policiesmentioning

confidence: 99%

“…Colombo Colombo [58] is a light-weight platform for developing, deploying, and executing service-oriented applications. It was developed at IBM Research.…”

Section: Using Policiesmentioning

confidence: 99%

Section: Work On Non-functional Concerns In Bpelmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Aspect-Oriented Workflow Languages

Charfi

Mezini

2006

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

View full text Add to dashboard Cite

show abstract

“…These include support for parallelism, the conversational nature of BPEL [17], correlation and the handling of faults and conditional links/joins. The use of a firstclass, separate BPEL runtime such as [7] may therefore be advantageous. The BPEL runtime however would need to be integrated with a policy and coordination middleware, as described in Section 5.…”

Section: Future Workmentioning

confidence: 99%

Composition of Coordinated Web Services

Tai¹,

Khalaf²,

Mikalsen³

2004

Middleware 2004

View full text Add to dashboard Cite

Abstract. The Web services architecture defines separate specifications for the composition and the coordination of Web services. BPEL is a language for creating service compositions in the form of business processes, whereas the WSCoordination framework defines coordination protocols for distributed activities. In this paper, we investigate the combination of these two aspects to compose coordinated Web services. We argue for a policy-based approach to address this problem and introduce a new model and middleware that enables the flexible integration of diverse coordination types into (existing) process-based Web services compositions.

show abstract

A Lightweight Agent Fabric for Service Autonomy

Li²,

Sun

Service-Oriented Computing: Agents, Semantics, and Engineering

View full text Add to dashboard Cite

Colombo: Lightweight middleware for service-oriented computing

Cited by 48 publications

References 8 publications

Aspect-Oriented Workflow Languages

Aspect-Oriented Workflow Languages

Composition of Coordinated Web Services

A Lightweight Agent Fabric for Service Autonomy

Contact Info

Product

Resources

About