Book Image

BPEL Cookbook: Best Practices for SOA-based integration and composite applications development

By : Arun Poduval, Doug Todd, Harish Gaur, Jeremy Bolie, Jerry Thomas, Kevin Geminiuc, Lawrence Pravin, Markus Zirn, Matjaz B. Juric, Michael Cardella, Praveen Ramachandran, Sean Carey, Stany Blanvalet, The Hoa Nguyen, Yves Coene
Book Image

BPEL Cookbook: Best Practices for SOA-based integration and composite applications development

By: Arun Poduval, Doug Todd, Harish Gaur, Jeremy Bolie, Jerry Thomas, Kevin Geminiuc, Lawrence Pravin, Markus Zirn, Matjaz B. Juric, Michael Cardella, Praveen Ramachandran, Sean Carey, Stany Blanvalet, The Hoa Nguyen, Yves Coene

Overview of this book

<p>Service Oriented Architecture is generating a buzz across the whole IT industry. Propelled by standards-based technologies like XML, Web Services, and SOAP, SOA is quickly moving from pilot projects to mainstream applications critical to business operations. One of the key standards accelerating the adoption of SOA is Business Process Execution Language for Web Services (BPEL). <br /><br />BPEL was created to enable effective composition of web services in a service-oriented environment. In the past two years, BPEL has become the most significant standard to elevate the visibility of SOA from IT to business level. BPEL is not only commoditizing the integration market, but it is also offering organizations a whole new level of agility - ability to rapidly change applications in response to the changing business landscape. BPEL enables organizations to automate their business processes by orchestrating services within and across the firewall. It forces organizations to think in terms of services. Existing functionality is exposed as services. New applications are composed using services. Communication with external vendors and partners is through services. Services are reused across different applications. Services are, or should be, everywhere!</p>
Table of Contents (16 chapters)
BPEL Cookbook
Credits
About the Editors
About the Authors
Foreword
Dismantling SOA Hype: A Real-World Perspective

Building the Sample


Let's build the process we just described. First, you create the database tables to support the process, and then you use the BPEL PM Designer to model the process.

Creating the Database Objects

Because the process stores the retry status in the database, you need to design the database component before creating the BPEL process. As discussed earlier, the main database additions that need to be made are:

  • More fields to track the status of records being processed

  • Updatable view

  • Status procedure

The additional fields can be added to the row that contains the data being modified or to a parallel table with a one-to-one relationship to the main table. The main columns that should be added are:

  • Status

  • Process Not Before

  • Retry Count

  • Create DTS

  • Last Modified DTS

The status field should be the same one that is used by BPEL's database polling adapter to identify unprocessed records. It is helpful to create a convention to make it easy to identify records that are still being processed...