Which documents are sent to a listener

Any documents having a verb that matches the settings of the active listener are delivered to that listener.

A listener receives documents from different sources, such as:

  • Documents published by an active application connection point.
  • Documents picked up using one of the technology connectors, such as database connector or web file connector.
  • Documents created in a data flow, such as a document that is created (or extended) by a mapping step or a document that is enriched in a workflow step.
  • Documents created by one of the ION engines, such as SyncPulseAlert or SyncPulseTask documents as created by the Activities engine.

Be aware that a document that is not sent to any other destination can still be sent to a listener. For example, you have these models defined and activated:

  • A connection point A that can send SyncSalesOrder and SyncPurchaseOrder.
  • A connection point B that can receive SyncSalesOrder and send SyncProductionOrder .
  • A document flow from A to B for SyncSalesOrder documents.
  • A listener for Sync documents.

In this case, not only the SyncSalesOrder is sent to the listener. If A publishes a SyncPurchaseOrder or B publishes a SyncProductionOrder then those documents are also sent to the listener. Even though there is no data flow defined for these documents.

If connection point B is a database connection point that has a stored procedure defined, ION starts invoking that stored procedure regularly when the listener is activated. When deactivating the listener, the stored procedure is not invoked anymore, if no other party must receive the document.

If you have a connection point that must send documents to a listener, but that connection point is not used in any data flow yet, you can create a specific document flow. This document flow must contain a single activity using the connection point. As explained earlier, the listener is not explicitly modeled in the data flows. After activating the listener and the document flow, any documents from the active connection point having a verb that is relevant are delivered to the listener.

Note: 
  • For Sync and Process messages, the ToLogicalId in the message header must be lid://default, as explained in Infor ION Development Guide . If the ToLogicalId is filled, then the message is only delivered to the connection point that is referred to by the ToLogicalId. In that case the message is not sent to the listener. Consequently, Process messages that are sent from an activation policy are also not sent to the listener.
  • If an application publishes a document in its outbox table and there is no component for which this document is relevant. The document is marked as having no route (status '9'). When publishing such a document after activating a listener that has the verb of that document selected, the document will not get status '9' but status '1' (processed).
  • In the normal message pattern, an application that receives a Process message publishes an Acknowledge reply. A listener will not publish an Acknowledge when handling a Process message, because it does not publish any messages. Consequently, ensure that relevant Process messages are not only sent to the listener, but also through a document flow to a connection point that can handle the message and send an Acknowledge reply.