If you are using the MessageListener notification on an Integration Server that does not have a Broker configured (and does not have a service associated with the notification), the notification publishes the document in local mode.

When an Integration Server hosts a MessageListener notification that is configured to publish a document, only the Integration Server that hosts the notification should subscribe to the notification's publishable document type. This is because a different Integration Server will not be able to understand the document's serialized message unless that Integration Server also has an Adapter for JMS installed.

When you configure a MessageListener notification, the adapter creates a publishable document type to use with the notification. When you associate a MessageListener notification with a service (rather than publish the document), the service must use the same input signature as the notification's publishable document type would use.