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

Interaction design patterns


The request will have one or more input parameters, and the response may have one or more output parameters. Deciding the interaction between the client and the service provider is one of the most important decisions during the design of BPEL services. Each service has its own WSDL definition and endpoint. The Partner Link is used for interaction between services.

Primarily, BPEL services are all about the request and response. The following design patterns are used for implementing BPEL services:

  • Synchronous request and response

  • Asynchronous request and response

  • One request and multiple responses

  • One request, a mandatory response, and an optional response

  • One-way message

Some of the other possible interaction design patterns that are not commonly used are listed here:

  • Multiple requests, multiple responses

  • Multiple requests, first response (ignore remaining responses)

  • One request and one or two responses

  • Asynchronous interaction with a timeout using the onMessage activity...