Message listener
Last updated
Last updated
A Message Listener is activated automatically for each action configured in an input contract with an OnMessage trigger. The Message listener is created when the contract is saved.
Message listeners are listed in Monitoring → Message Listener.
The Message listener uses the JMS Client Connection configured in the input contract to:
connect to and listen on a specific queue
receive incoming JMS messages as they arrive
Upon receiving messages, the Message listener applies the selected Message Processing Rule to aggregate messages into files.
In the Message listener page, results can be filtered by:
Status of the message listener: started, stopped or failed.
M2F Action: the name of the contract action and the name of the contract are shown.
Protocol: the JMS protocol is available.
STENG Cluster and Peer: cluster and peer where the Message listener is active.
The Message listener’s activation is also visible in the Central Log.
When the Message Listener is activated, the JMS provider will show the active consumer on the configured input contract queue.
The Message listener can be activated for each STENG if the Parallelism parameter in the corresponding input contract action is configured by setting the toggle to ON. If the toggle is set to OFF, a single listener is activated for all STENGs.
You can find detailed information in the section.
