BPEL Tutorial
BPEL Useful Resources
Selected Reading
- Difference between BPEL 1.1 & BPEL 2.0
- Using Oracle BPEL Process Manager Sensors
- Using the Notification Service
- Using Events & Timeouts in BPEL Processes
- Using Correlation Sets & Message Aggregation
- Manipulating XML Data
- Incorporating Java & Java EE Code
- Resubmitting a Faulted Process
- Using Fault Handling
- Using Conditional Branching
- Using Parallel Flow
- Invoking an Asynchronous Web Service
- Invoking a Synchronous Web Service
- Multiple Application Interactions
- Partial Processing
- One Request, a Mandatory Response, & an Optional Response
- One Request, One of Two Possible Responses
- One Request, Multiple Responses
- Asynchronous Interactions with a Notification Timer
- Asynchronous Interactions with a Timeout
- Asynchronous Interactions
- Synchronous Interactions
- One-Way Messages
- Process Monitors
- BPEL - Adapters
- Creating a Partner Link
- Partner Link in BPEL Process
- BPEL - Activities
- BPEL - Introduction
- BPEL - Home
BPEL Useful Resources
Selected Reading
- Who is Who
- Computer Glossary
- HR Interview Questions
- Effective Resume Writing
- Questions and Answers
- UPSC IAS Exams Notes
One-Way Messages
BPEL - One-Way Messages
The Cpent BPEL Process sends a message to Service BPEL Process and the Service BPEL Process is not required to reply as shown in the figure below −
The Cpent BPEL Process needs a vapd partner pnk and an invoke activity.
The Service BPEL Process needs a receive activity.
As with all partner activities, the Web Services Description Language (WSDL) file defines the interaction. The WSDL file is as shown below.
<wsdl:portType name = "BPELProcess">
<wsdl:operation name = "process">
<wsdl:input message = "cpent:BPELProcessRequestMessage" />
<wsdl:output message = "cpent:BPELProcessResponseMessage"/>
</wsdl:operation>
</wsdl:portType>
Advertisements