JMS Trigger
Discover more about the JMS Trigger and how to use it on the Digibee Integration Platform.
Last updated
Discover more about the JMS Trigger and how to use it on the Digibee Integration Platform.
Last updated
This trigger requires a dedicated infrastructure. Due to security matters, it's necessary to get in touch with our Support Team through the chat to obtain the liberation.
Let's say you want to use a trigger to make a subscription in a message queue. By using JMS Trigger, you'll be able to trigger a pipeline that enables the consumption of one message at a time.
With the Auto Commit property disabled, it's possible to give the message ack only after the well succeeded pipeline execution. For the IBM MQ broker, it's necessary to keep this field enabled at all times, because it's not supported to control the message ack or reject.
The supported queues are:
Oracle Advanced Queue
Tibco EMS
SQS
IBM MQ
Take a look at the configuration options for the trigger. Parameters supported by Double Braces expressions are marked with (DB)
.
Parameter | Description | Default value | Data type |
---|---|---|---|
Depending on the queue, different parameters can be accessed:
Visibility Timeout in Broker SQS must have a value equal or greater than the timeout of the pipeline. That's necessary, because Broker SQS is a distributed system and doesn't delete the message after its consumption, since there's no guarantee that's actually been consumed.
If the Visibility Timeout isn't configured in the mentioned conditions, a message under processing can be resent. Broker SQS sends the message again if it doesn't receive ACK or REJECT within the time configured in Visibility Timeout. For more information, check the SQS documentation.
There's still no support for the authentication using TLS.
If you want to deploy the trigger, it's necessary to publish the pipeline.
Check how to do it:
Click on Run, located in the superior part of the screen.
Select the environment, which can be test or prod.
Click on Create a new implantation.
Select the pipeline with its version and capacity.
Click on Confirm.
When triggered, the pipeline will receive a payload similar to the following one:
JMS Trigger supports the consumption of messages in a parallel way - the number of consumers configured when deploying the pipeline will be exactly the same for the JMS queue/topic.
Therefore, if 10 consumers are configured in the deploy, 10 consumers will be created for the JMS queue/topic.
That increases the throughput consumption of the messages, besides allowing the user to have control over how many simultaneous consumers can be created.
Formerly, there was only one consumer per trigger.
If you deploy a pipeline with JMS Trigger attached to a topic, it will be necessary to configure just 1 Consumer when making the deploy.
Parameter | Description | Default value | Data type |
---|---|---|---|
Parameter | Description | Default value | Data type |
---|---|---|---|
Parameter | Description | Default value | Data type |
---|---|---|---|
Parameter | Description | Default value | Data type |
---|---|---|---|