Adapter Development Kit 9.12 | webMethods Adapter Development Kit Documentation | webMethods Adapter Development Kit Installation and User’s Documentation | Listener Notifications | Overview | Synchronous and Asynchronous Listener Notifications
 
Synchronous and Asynchronous Listener Notifications
The ADK includes both, synchronous and asynchronous processing model.
An asynchronous listener notification publishes a document to a configured webMethods Broker, using the doNotify method.
*An asynchronous listener notification publishes a document.
*The notification object's runNotification method calls doNotify method.
*The users of the adapter may process the document's data as needed. For example, the users of the adapter can create an Integration Server trigger that receives the document and executes an Integration Server flow service or a Java service.
*Asynchronous listener notifications do not support session handling. When a synchronous listener notification calls an Integration Server service that needs that needs information contained in the session data, it may appear to work because asynchronous listener notifications themselves do not execute a service. Instead, an Integration Server trigger, which supports session handling, is used to receive the document and execute an Integration Server flow service or a Java service.
A synchronous listener notification invokes a specified Integration Server service, and potentially receives a reply from the service and delivers the results back to the adapter resource.
*A synchronous listener notification does not publish a document.
*The notification object's runNotification method calls invokeService.
*The users of the adapter cannot process the document's data as the processing is done in the invokeService method.
*Synchronous listener notifications do not support session handling. When a synchronous listener notification calls an Integration Server service that needs information contained in the session data, that service can fail.