Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Oracle SOA BPEL Process Manager 11gR1 - A Hands-on Tutorial

You're reading from   Oracle SOA BPEL Process Manager 11gR1 - A Hands-on Tutorial Your step-by-step, hands-on guide to Oracle SOA BPEL PM 11gR1

Arrow left icon
Product type Paperback
Published in Jun 2013
Publisher Packt
ISBN-13 9781849688987
Length 330 pages
Edition 1st Edition
Languages
Arrow right icon
Toc

Table of Contents (20) Chapters Close

Oracle SOA BPEL Process Manager 11gR1 – A Hands-on Tutorial
Credits
About the Authors
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
1. Creating Basic BPEL Processes 2. Configuring BPEL Processes FREE CHAPTER 3. Invoking a BPEL Process 4. Orchestrating BPEL Services 5. Test and Troubleshoot SOA Composites 6. Architect and Design Services Using BPEL 7. Performance Tuning – Systems Running BPEL Processes 8. Integrating the BPEL Process Manager with Service Bus, Registry, and SOA Deployment 9. Securing a BPEL Process 10. Architecting High Availability for Business Services 11. The Future of Process Modeling 12. Troubleshooting Techniques 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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image