When you create an asynchronous listener notification, the adapter creates a publishable document type. At run time, when the listener detects an event in the back end, it invokes the asynchronous notification. The asynchronous notification then publishes a document, which has the structure defined by the publishable document type, in either of the following ways:

Adapter users can process the document's data any way they want to. For example, they can create an Integration Server trigger that receives the document and executes an Integration Server flow service or a Java service.

At run time, a synchronous listener notification invokes a specified IS service, and potentially receives a reply from the service and delivers the results back to the adapter resource. The listener notification waits until the service has finished processing before it begins to process the next message from the adapter resource. A synchronous listener notification does not publish a document.

Synchronous listener notifications do not support session handling. When a synchronous listener notification calls a service that needs information contained in the session data, that service can fail. However, note that the same service may appear to work for an asynchronous listener notification. This is 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.