Book Image

Oracle SOA BPEL Process Manager 11gR1 - A Hands-on Tutorial

Book Image

Oracle SOA BPEL Process Manager 11gR1 - A Hands-on Tutorial

Overview of this book

BPEL, Business Process Execution Language is the definitive standard in writing and defining actions within business processes. Oracle BPEL Process Manager R1 is Oracle's latest offering, providing you with a complete end-to-end platform for the creation, implementation, and management of your BPEL business processes that are so important to your service-oriented architecture."Oracle SOA BPEL Process Manager 11gR1 – A Hands-on Tutorial" is your guide to BPEL design and development, SOA Suite platform troubleshooting, and engineering in a detailed step-by-step guide working real-world examples and case studies. Using industry-leading practices you will start by creating your first BPEL process and move onto configuring your processes, then invoking, orchestrating, and testing them. You will then learn how to use architect and design services using BPEL, performance tuning, integration, and security, as well as high availability, troubleshooting, and modeling for the future. "Oracle SOA BPEL Process Manager 11gR1 – A Hands-on Tutorial" is your complete hands-on guide to Oracle SOA BPEL Process Manager 11g.
Table of Contents (20 chapters)
Oracle SOA BPEL Process Manager 11gR1 – A Hands-on Tutorial
Credits
About the Authors
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
Index

The Dehydration Store


The BPEL Process Manager is a web application created by Oracle. Oracle BPEL Process Manager is deployed on top of J2EE containers such as WebLogic, WebSphere, and JBoss. Oracle BPEL Process Manager uses a database to store metadata, runtime instance information, and the state of each conversation. The database is also used as a Dehydration Store to store the state of the BPEL process services. The process of updating the state of the BPEL process services in the database is called Dehydration. The asynchronous and synchronous processes mainly use the Dehydration Store to save the state of the process while waiting for asynchronous callbacks. The asynchronous messages also persist in the Dehydration Store.

Over a period of time the Dehydration Store database fills with data unless you purge the data at regular intervals. It is an industry-leading practice to develop data purging frequency based on the data retention policies for audit and troubleshooting needs. It is...