Designer 10.15 | webMethods BPM Process Development Help | Building and Uploading Processes | Working with Protocols
 
Working with Protocols
 
Configuring a Subscription-Triggered Process
Configuring a Simple Service Triggered Process
Configuring a JMS-Triggered Process
Configuring an EDA-Triggered Process (Deprecated)
Process steps use messaging protocols to send and receive information. Messaging protocols are applied when a subscription trigger starts or joins a process, and when information is sent and received within the process, such as when catching and throwing BPMN events.
Note:
Parent and child process models must use the same protocol.
Designer supports the following four protocols listed in the table below, although some protocols are not available for specific activity or event types:
Protocol
Description
Used by
Subscription
For Publishable Documents
Used by send and receive task activities, message events, signal events, and the start none event. See Configuring a Subscription-Triggered Process and About Subscription Triggered Process Generation.
Simple Service
For Synchronous Receive and Send
Used by send and receive task activities for two-way synchronous information exchange. See Configuring a Simple Service Triggered Process and About Simple Service Triggered Process Generation.
JMS
For JMS Triggered Processes
Used by send and receive task activities, message events, signal events, and the start none event. See Configuring a JMS-Triggered Process and About JMS-Triggered Process Generation.
EDA (deprecated)
For EDA Event Triggered Processes
Message end events only send information, so they use only the send version of the selected protocol. Message start events only receive information, so they only use the receive version of the selected protocol.
Software AG Designer supports the use of the EDA (deprecated) protocol with BPMN message events as a BPMN extension.
Related Topics