This Listener will allow you to connect to the Java Messaging Service. It has 5 tabs: Basic, Advanced, Transaction Logging, Credentials and Data Source.
1. Basic: Polling interval determines how often you would like to poll or queue for new messages. Please consult your JMS documentation to determine the naming context factor class and provider URL for the class that you are using.
2. Advanced: At the Advanced tab, you can specify:
Initialize on trigger only: If enabled, Listener doesn’t start up until a trigger initializes it.
Allow command-line invocation: If enabled, Listener can be invoked using the CLI client application.
Restart on listening error: If enabled, the Listener will be restarted after an error occurs.
FIFO Queue Name: The FIFO stuff enables a “First In, First Out” queuing mechanism between Listeners and Transports. If a “FIFO Queue Name” is provided, that name will be used as a key for a queue Transactions & will be pushed into before reaching a transport. They’ll be ordered in this queue according to when the Listener created them.
FIFO Queue Delay: It is the interval between updates/checks against that queue. Providing a queue name guarantees that a given Transport sends transactions in the same order the Listener created them in.
Max Messages per Poll: Specifies the maximum number of messages to pick up from the JMS Provider per polling cycle.
JMS Client Type: Can be Default or an IBM JMS Thin Client.
Reconnect on Error: Determines if connections should be closed and reconnected when errors are encountered.
Synchronous Acknowledge: If enabled, message acknowledgment will not be sent until transport confirms the message has been processed.
3. Transaction Logging – This tab allows us to enable transaction events logging. That data can be logged by a TransactionEventListener.
The Transaction Logging Enable – checkbox allows transaction events originating from this listener to be logged by a TransactionEventListener.
Log Transaction Attribute – if enabled, logs transaction attributes.
Log Transaction Data – if enabled, logs transaction data body.
Log Transaction Data Base64 – if enabled, logs transaction data body as Base64.
4. Credentials: This tab lets you enter the user name and password used to connect to the JMS provider.
5. Data Source: This tab allows you to specify a queue or topic that you would like to connect to. If connecting to a queue, select Point-to-Point. If connecting to a topic, select Publish/subscribe.
For Point-to-Point, you will need to provide the Queue name and the Connection factory name (both present in your JMS configuration).
For Publish/Subscribe, you will need to provide the Topic name and Connection factory name (both present in your JMS configuration).