Combining the Strengths of BPEL and mule ESB

Aimrudee Jongtaveesataporn, Shingo Takada

Research output: Contribution to journalArticle

Abstract

Service Oriented Architecture (SOA) provides an application framework which integrates variety of technology services in a loosely coupled way. Mule Enterprise Service Bus (ESB) is a widely-used ESB product that provides important functions such as message routing, message transformation, protocol-mediation, and event handling. These functions enable Mule ESB to integrate services implemented on various platforms and technologies. However, Mule ESB does not support business logic at all. Another approach to integrate services is to use a business process language such as BPEL (Business Process Execution Language). BPEL is used to define activities along with control flow. It is limited to Web service connections. One major difference is that BPEL is capable of orchestrating a business process with programming constructs, whereas Mule ESB is capable of processing messages in many protocal connections. Both BPEL and Mule ESB have different advantages. Unfortunately, neither one is powerful enough to solve some classes of business problems. In this paper we present the COMBO framework, which merges the strengths of Mule ESB and BPEL. We develop a tool to translate an extended BPEL file to a Mule ESB configuration file. The configuration file is used within a Mule ESB to execute the process that has been described within the BPEL document. We add extension modules to the standard Mule ESB for supporting BPEL functions that Mule ESB does not provide. The extended ESB has capabilities for supporting variable assignment and conditional branches in complex business processes. Our translation can cover frequently used activities in business processes. We also present case studies that use many business activities to show how the COMBO framework supports various activity translation.

Original languageEnglish
Pages (from-to)347-390
Number of pages44
JournalInternational Journal of Software Engineering and Knowledge Engineering
Volume24
Issue number3
DOIs
Publication statusPublished - 2014

Fingerprint

Industry
Service oriented architecture (SOA)
Flow control
Web services
Network protocols

Keywords

  • BPEL
  • Enterprise Service Bus (ESB)
  • Service Oriented Architecture (SOA)

ASJC Scopus subject areas

  • Software
  • Artificial Intelligence
  • Computer Graphics and Computer-Aided Design
  • Computer Networks and Communications

Cite this

Combining the Strengths of BPEL and mule ESB. / Jongtaveesataporn, Aimrudee; Takada, Shingo.

In: International Journal of Software Engineering and Knowledge Engineering, Vol. 24, No. 3, 2014, p. 347-390.

Research output: Contribution to journalArticle

@article{0ea2545f654d4155aa7f95b7fac55899,
title = "Combining the Strengths of BPEL and mule ESB",
abstract = "Service Oriented Architecture (SOA) provides an application framework which integrates variety of technology services in a loosely coupled way. Mule Enterprise Service Bus (ESB) is a widely-used ESB product that provides important functions such as message routing, message transformation, protocol-mediation, and event handling. These functions enable Mule ESB to integrate services implemented on various platforms and technologies. However, Mule ESB does not support business logic at all. Another approach to integrate services is to use a business process language such as BPEL (Business Process Execution Language). BPEL is used to define activities along with control flow. It is limited to Web service connections. One major difference is that BPEL is capable of orchestrating a business process with programming constructs, whereas Mule ESB is capable of processing messages in many protocal connections. Both BPEL and Mule ESB have different advantages. Unfortunately, neither one is powerful enough to solve some classes of business problems. In this paper we present the COMBO framework, which merges the strengths of Mule ESB and BPEL. We develop a tool to translate an extended BPEL file to a Mule ESB configuration file. The configuration file is used within a Mule ESB to execute the process that has been described within the BPEL document. We add extension modules to the standard Mule ESB for supporting BPEL functions that Mule ESB does not provide. The extended ESB has capabilities for supporting variable assignment and conditional branches in complex business processes. Our translation can cover frequently used activities in business processes. We also present case studies that use many business activities to show how the COMBO framework supports various activity translation.",
keywords = "BPEL, Enterprise Service Bus (ESB), Service Oriented Architecture (SOA)",
author = "Aimrudee Jongtaveesataporn and Shingo Takada",
year = "2014",
doi = "10.1142/S0218194014500144",
language = "English",
volume = "24",
pages = "347--390",
journal = "International Journal of Software Engineering and Knowledge Engineering",
issn = "0218-1940",
publisher = "World Scientific Publishing Co. Pte Ltd",
number = "3",

}

TY - JOUR

T1 - Combining the Strengths of BPEL and mule ESB

AU - Jongtaveesataporn, Aimrudee

AU - Takada, Shingo

PY - 2014

Y1 - 2014

N2 - Service Oriented Architecture (SOA) provides an application framework which integrates variety of technology services in a loosely coupled way. Mule Enterprise Service Bus (ESB) is a widely-used ESB product that provides important functions such as message routing, message transformation, protocol-mediation, and event handling. These functions enable Mule ESB to integrate services implemented on various platforms and technologies. However, Mule ESB does not support business logic at all. Another approach to integrate services is to use a business process language such as BPEL (Business Process Execution Language). BPEL is used to define activities along with control flow. It is limited to Web service connections. One major difference is that BPEL is capable of orchestrating a business process with programming constructs, whereas Mule ESB is capable of processing messages in many protocal connections. Both BPEL and Mule ESB have different advantages. Unfortunately, neither one is powerful enough to solve some classes of business problems. In this paper we present the COMBO framework, which merges the strengths of Mule ESB and BPEL. We develop a tool to translate an extended BPEL file to a Mule ESB configuration file. The configuration file is used within a Mule ESB to execute the process that has been described within the BPEL document. We add extension modules to the standard Mule ESB for supporting BPEL functions that Mule ESB does not provide. The extended ESB has capabilities for supporting variable assignment and conditional branches in complex business processes. Our translation can cover frequently used activities in business processes. We also present case studies that use many business activities to show how the COMBO framework supports various activity translation.

AB - Service Oriented Architecture (SOA) provides an application framework which integrates variety of technology services in a loosely coupled way. Mule Enterprise Service Bus (ESB) is a widely-used ESB product that provides important functions such as message routing, message transformation, protocol-mediation, and event handling. These functions enable Mule ESB to integrate services implemented on various platforms and technologies. However, Mule ESB does not support business logic at all. Another approach to integrate services is to use a business process language such as BPEL (Business Process Execution Language). BPEL is used to define activities along with control flow. It is limited to Web service connections. One major difference is that BPEL is capable of orchestrating a business process with programming constructs, whereas Mule ESB is capable of processing messages in many protocal connections. Both BPEL and Mule ESB have different advantages. Unfortunately, neither one is powerful enough to solve some classes of business problems. In this paper we present the COMBO framework, which merges the strengths of Mule ESB and BPEL. We develop a tool to translate an extended BPEL file to a Mule ESB configuration file. The configuration file is used within a Mule ESB to execute the process that has been described within the BPEL document. We add extension modules to the standard Mule ESB for supporting BPEL functions that Mule ESB does not provide. The extended ESB has capabilities for supporting variable assignment and conditional branches in complex business processes. Our translation can cover frequently used activities in business processes. We also present case studies that use many business activities to show how the COMBO framework supports various activity translation.

KW - BPEL

KW - Enterprise Service Bus (ESB)

KW - Service Oriented Architecture (SOA)

UR - http://www.scopus.com/inward/record.url?scp=84905047575&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=84905047575&partnerID=8YFLogxK

U2 - 10.1142/S0218194014500144

DO - 10.1142/S0218194014500144

M3 - Article

AN - SCOPUS:84905047575

VL - 24

SP - 347

EP - 390

JO - International Journal of Software Engineering and Knowledge Engineering

JF - International Journal of Software Engineering and Knowledge Engineering

SN - 0218-1940

IS - 3

ER -