TY - GEN
T1 - Automatic generation of ESB configuration file from extended BPEL
AU - Jongtaveesataporn, Aimrudee
AU - Takada, Shingo
PY - 2010/12/1
Y1 - 2010/12/1
N2 - Enterprise service bus (ESB) is a middleware to integrate applications in service oriented architecture. Normally software developers use information from the process requirements to manually create the ESB configuration file. This action consumes a lot of effort and may cause some errors in the configuration files. Business Process Execution Language (BPEL) defines a standard that enables a process document to be written that combines Web services. One of the BPEL capabilities that is not available in ESB is the ability to describe a process with logic such as if-else condition. Furthermore, the current WS-BPEL 2.0 standard does not allow for interaction with non-Web service components. Therefore combining the capabilities of ESB and BPEL will help improve the development of service-oriented systems. Our basic approach is to add extra information into BPEL documents for connecting non-Web service components, and use this document to automatically generate an ESB configuration file. This configuration file is used within an ESB to execute the process that was originally described within the BPEL document. We also show a case study.
AB - Enterprise service bus (ESB) is a middleware to integrate applications in service oriented architecture. Normally software developers use information from the process requirements to manually create the ESB configuration file. This action consumes a lot of effort and may cause some errors in the configuration files. Business Process Execution Language (BPEL) defines a standard that enables a process document to be written that combines Web services. One of the BPEL capabilities that is not available in ESB is the ability to describe a process with logic such as if-else condition. Furthermore, the current WS-BPEL 2.0 standard does not allow for interaction with non-Web service components. Therefore combining the capabilities of ESB and BPEL will help improve the development of service-oriented systems. Our basic approach is to add extra information into BPEL documents for connecting non-Web service components, and use this document to automatically generate an ESB configuration file. This configuration file is used within an ESB to execute the process that was originally described within the BPEL document. We also show a case study.
KW - BPEL
KW - ESB
KW - Middleware
KW - SOA
KW - Service integration
UR - http://www.scopus.com/inward/record.url?scp=84862271782&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=84862271782&partnerID=8YFLogxK
U2 - 10.2316/P.2010.725-058
DO - 10.2316/P.2010.725-058
M3 - Conference contribution
AN - SCOPUS:84862271782
SN - 9780889868786
T3 - Proceedings of the IASTED International Conference on Software Engineering and Applications, SEA 2010
SP - 364
EP - 372
BT - Proceedings of the IASTED International Conference on Software Engineering and Applications, SEA 2010
T2 - IASTED International Conference on Software Engineering and Applications, SEA 2010
Y2 - 8 November 2010 through 10 November 2010
ER -