MessageListener Notification Run-Time Processing

The following diagram and steps illustrate what happens at run time when MessageListener notifications are invoked. Integration Server continues to invoke the notification periodically, as defined when you configured the schedule parameters for the MessageListener notification.

Step	Description
1	JMS messages are placed on a JMS destination (queue or topic).
2	The notification gets a connection from the notification's connection pool.
3	The notification uses the JMS APIs to monitor the JMS destination.
4	The notification retrieves the JMS messages from the queue or topic.
5	The notification does one of the following actions, depending on how you configured the notification: The notification creates a publishable document, which contains the JMS message, and then publishes the document. When you use this option, you can create an integration scenario that uses an Integration Server trigger to invoke a flow or Java service using the data contained in the publishable document. The notification invokes a service in Integration Server. To use this option, you specify the name of the service to be invoked when you configure the notification. For more details about Integration Server publishable documents, see the Publish-Subscribe Developer’s Guide for your release.