In a TIBCO BW project, there is a high chance that we need to configure a queue receiver and queue sender activities. This activity can receive/send data from/to mainframe endpoint or any other JMS based endpoint. In this post, I am going to explain how to configure the JMS queue receiver or sender pallets and the different options are available to make our coding life easier.
How to configure the TIBCO BW JMS Connection pallet?
For both queue receiver and sender, the first thing is to establish a connection to the endpoint. In this example, it’s TIBCO EMS and we can use JMS Connection pallet to establish the connection. There are different ways to set up a connection to EMS and I will explain in another post. For this example, I am using TCP connection and all we need to know is the listening URL, username and password. Once this done click on Apply button to save the changes. There is a test connectivity button as well, you can use that to check the connectivity of the EMS which you configured.
We can create as many JMS connections if the BW has a dependency on multiple EMS servers.
How to configure the TIBCO BW JMS Queue Receiver pallet?
As you might aware JMS Queue Receiver is a starter process and its initiate a process based on the receipt of a message for the specified JMS queue. The configuration tab has the following fields.
| Feild | Description |
|---|---|
| JMS Connection | Here we need to specify the JMS connection which we created at the beginning. we can use the Browse icon to set up this. |
| Destination QUEUE | Name of the queue of the incoming message. If you have a valid JMS connection, you can use the Browse button next to this field to display the destination queues. |
| Message Type | The type of message, this can be an XML Text, Object, Text etc. |
| Acknowledge Mode | The acknowledge mode for the incoming message. Read more at Acknowledgement modes in JMS Queue receiver. |
There is one more Configuration field is available for JMS Queue receiver which is Max Session. This is configurable for the Acknowledge modes Client, Transactional and Local Transactional. Max Session allows us to create multiple sessions to the queue and will be able to read the message for each session. This is to increase the performance of a BW process.
How to configure the TIBCO BW JMS Queue Sender pallet?
This pallet shares some configuration as in JMS Queue receivers like JMS Connection, Destination queue and Message type. And one additional thing which we need to configure here is the input tab. The main field is Body and here we can map the data which we need to send to the destination queue.
| Feild | Datatype | Description |
|---|---|---|
| Destination Queue | String | The queue to which to send the request. This input item overrides the Destination Queue field on the Configuration tab. |
| Body | Depends on message | The body of the message |
How to send data to different queues based on the data received?
This can be achieved using the Destination Queue field inside the input tab. We can write as many conditions to send data to different queues. For example, if the received data has a string CREDIT its need to go to QUEUE.CREDIT and if it has DEBIT its should go to QUEUE.DEBIT.
Hope now you have a better idea on how to set up the JMS queue pallets in Tibco Business Works. Please let me know your feedback and suggestions in the comment box below.