When you create an asynchronous notification, WebSphere MQ Adapter creates a publishable document type. The publishable document type defines the structure of the document that includes the msgBody and msgHeader properties. At run time, after the listener retrieves a message from the queue, the listener invokes the asynchronous notification. The asynchronous notification publishes the document that has the structure defined by the publishable document type created with the asynchronous notification.

An asynchronous listener notification can publish a document in either of the following ways:

To process the message from the queue, you should create an Integration Server trigger that subscribes to the document type that WebSphere MQ Adapter created with the asynchronous notification. For more information about using triggers with services, see the Publish-Subscribe Developer’s Guide for your release.

Beginning with Integration Server 8.0, you can choose the destination to which asynchronous notifications should publish messages. Specifically, you can choose whether the asynchronous notification templates use JMS APIs to publish messages to Integration Server or Broker APIs to publish notification messages to Broker.

For steps for selecting a publish destination for asynchronous notification messages, see Listener Notifications.