A. Jongtaveesataporn and S. Takada (Japan)
ESB, BPEL, SOA, Middleware, Service Integration
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.
Important Links:
Go Back
