Guide to BPEL

This web page is made to provide some information about BPEL and how to use it. This is not a complete reference, but should contain enough information to get a beginner started. The information listed on this page, has been gathered during a graduation project at luminis®. In the graduation project we had to search for a way to make a connection between certain software of luminis® and customer systems. These customer systems can be ERP, CRM or similar systems. This page has been updated on 28 june 2005.

Because we had to find a way to connect to these systems in a flexible way, we had to look for a certain open standard that could help in our needs. We found that BPEL could help solve our problem. Then we did some research on this subject and build a proof-of-concept to connect to the software of luminis® though BPEL. We thought it would be a shame not to share our knowledge with the people on the Internet, that's why we made this page.

Index

This guide has been split up into four sections to get a good separation between the different subjects on this web page.

• Usage
  Description how BPEL is used in practical situations, where is it used and were we find it useful.

• Language
  Explanation about how the BPEL language is structured, what is possible with it and how to accomplish it.

• Orchestration / Engines
  Description what is needed to orchestrate a BPEL process and a list of engines which can orchestrate the process.

• Our experience
  Some of our experiences, what did we find useful and what we think you shouldn't do. In this section there is also a list of web pages we find informative.

About the authors

This web page is made by Berry de Vos and Jos Zwiers to share some of our BPEL experiences with people interested in this subject. At the time this is written we are finishing our graduation project at luminis®. In this project we researched some of the possibilities of BPEL and how to use this new technology.

We hope you find the information on this page useful and any suggestions and remarks are welcome. You can contact Berry at bdevos@gmail.com and Jos at jos.zwiers@gmail.com.