TIBCO | JMS Queues configuration

-
In previous post we check how dynamic queues are created, in this post we will be checking how to configure JMS response queues.

We can replace JMS Queue requester activity with JMS Queue Sender and wait for JMS design pattern. As TIBCO solution is implemented for large enterprises the LOAD balancing is important part. Normally single instance of TIBCO BW application is deployed in TIBCO Admin. For production environments multiple instances of same application are run on different machines for load balancing.
As same code is running on 2 or more instances we have to ensure few points while developing TIBCO BW Project.
  • TIBCO Queue is point to point which means that it listens for only one receiver for queue at a time. If there are multiple queue receivers are present with same queue name then message is received in round-robin fashion.
  • Similarly TIBCO wait for queue message activity is always listens for one receiver at a time. If there are multiple queue receivers are present with same queue name then there are chances of Activity timeout condition. 
  • If project is using JMS Queue Sender and wait for JMS design pattern then wait for JMS reply queue should be service settable.
  • We have to provide different response queue names at PAR(Process Archive) level of deployed configuration for not using same queue names.
  • We also have to design process in such way that no wrong messages are picked by wait of JMS activity in LB configuration.

Step 1 : Create a simple Project with JMS Queue Sender and wait for JMS design pattern.



Note that we have created correlation id(unique random id) while sending message to JMS Queue sender.(As of now i have hard-coded value, we can use custom random function to generate this id)


Pass the same correlation id in input message.


Make a response Queue name service settable as below.

Step 2 : Map the created correlation id from start to Wait for JMS Queue Message.




This plays important role in correlating input message to correct response message. If this not mapped then there are chances of wrong responses are mapped to input messages.

Step 3 : In receiver side pass the same correlation id to JMS Queue sender.


Step 4 : Configure Load Balancing queues at PAR level



As you can see we service settable queues are configured at Process Archive level. This ensures only one receiver to wait for JMS queue message activity. For multi instance configuration PAR level queues should be named according to PAR Name and instance number.

Once we deployed this simple project we can see that there is only one receiver at a time to wait for JMS and correct input message is picked by wait for JMS.


Comments

Post a Comment

Popular posts from this blog

Spring | Using TIBCO EMS with Spring framework

-
TIBCO EMS can be use with Spring Framework to support message publishing and subscription. Spring provides JMS template to send JMS messages and @JmsListener/ MessageListener to subscribe it. Steps 1 : Create new project in eclipse or IntelliJ Idea Create new project with Spring dependency. We can use maven to add all required libs for this project. Maven takes care of adding referred java libs to build path. TIBCO JMS jars need to be added to build path. Pom.xml will be as follows. As you can see in above pom file we have added TIBCO JMS and Spring JMS dependency. Step 2 : Create JMS bean configuration file(Jms-conf.xml) Next we will create bean configuration file. It will set JNDI and JMS properties. We can use same JMS listener class to subscribe multiple queues and topics. Spring bean configuration take care of JMS transport setup. Env variables values can be provided via properties file. Step 3 : Create JMS Queue/Topic sender and Listner In above cod
Read more

TIBCO | For Loop - Accumulate output

-
Image
In this post we will check how TIBCO for loop works. TIBCO provides Group Activity to iterate over processes or activities. Loops can be different types eg. For Loop, While util loop, if loop, repeat on error etc. TIBCO group can loop over sub-process and accumulate output in end activity to be used by next activities. TIBCO For loop with Accumulate output repeats over process/activity and return output of each iteration in output activity. This is helpful where we want to call sub-process repeatably with different input parameters and store each output in some variable.
Read more

TIBCO | JNDI Server & JMS Instance creation

-
Image
In this post we will be creating TIBCO JNDI server and other instance pointed to JNDI server. First lets see what is mean by JNDI. It is   Java API for a directory service that allows Java software clients to discover and look up data and objects via a name. TIBCO EMS uses JNDI concept to lookup for EMS objects and its relations in messaging service. While developing enterprise level TIBCO solution it is advise or say standard practice to create one JNDI server(also one backup JNDI server) and other instance servers according to the functionality or domains. In this tutorial we will be creating one JNDI server and two domain servers.
Read more