Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
WS-BPEL 2.0 for SOA Composite Applications with Oracle SOA Suite 11g

You're reading from   WS-BPEL 2.0 for SOA Composite Applications with Oracle SOA Suite 11g Define, model, implement, and monitor real-world BPEL business processes with SOA powered BPM.

Arrow left icon
Product type Paperback
Published in Sep 2010
Publisher Packt
ISBN-13 9781847197948
Length 616 pages
Edition 1st Edition
Languages
Arrow right icon
Toc

Table of Contents (17) Chapters Close

WS-BPEL 2.0 for SOA Composite Applications with Oracle SOA Suite 11g
Credits
1. Foreword
About the Authors
About the Reviewers
2. Preface
1. Introduction to BPEL and SOA FREE CHAPTER 2. Service Composition with BPEL 3. Advanced BPEL 4. Using BPEL with Oracle SOA Suite 11g 5. BPEL Extensions, Dynamic Parallel Flow, Dynamic Partner Links, Notification Service, Java Embedding, and Fault Management Framework 6. Entity Variables, Master and Detail Processes, Security, and Business Events in BPEL 7. Human Interactions in BPEL 8. Monitoring BPEL Processes with BAM 9. BPEL with Oracle Service Bus and Service Registry 10. BPMN to BPEL Round-tripping with BPA Suite and SOA Suite 11. Integrating BPEL with BPMN using BPM Suite

Business process lifecycle


A business process specified in BPEL has a well-defined structure. It usually waits for the client to invoke the process. This is done using the<receive> activity, as we have seen in the previous chapter. A business process can also use the<pick> activity to wait for the initial incoming message. Then the business process typically invokes several operations on partner web services and waits for partners to invoke callback operations. The business process also performs some logic, such as comparison and calculation of certain values. The business process terminates after all activities have been performed.

We can see that each BPEL process has a well-defined lifecycle. To communicate with partners, BPEL uses web services. Web services provide a stateless model for operation invocation. This means that a web service does not provide a common approach to store client-dependent information between operation invocations. For example, consider a shopping...

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