TIBCO | JMS Queues

-
TIBCO provides EMS(Enterprise Message Service) for performing message communication with various system and internal processes. As explain in earlier post main purpose of EMS implementation is message transportation with reliable channel. TIBCO provides reliable message service by persisting messages in file store/DB stores etc. There is 100% guarantee of messages being delivered to receiver system.

TIBCO JMS related activities are well explained in TutorialsPedia blog. In this post we will be covering dynamic queues, Request/Response dynamic queues.

What is dynamic Queue?



 TIBCO provides property to create queues on the fly without need of running create queue ems script. This property is useful when there are multiple queues(mostly response queues) needs to be created in Production environment. TIBCO enables dynamic queues creation by default. We can find '>' in queues.conf file which means dynamic queue creation is enabled. We can disable it by removing '>' in queues.conf file. If queue is not present then it will return Not allow to create destination.

create queue >

 Check default EMS conf file below you will find '>'.


Create simple process with JMS queue sender and wait for JMS. In other process create JMS receiver and sender activity to receive message sent from first process and send response back to wait for JMS message activity. Mention queue which is not created in EMS.







You can see the queue gets created automatically once service is started. Note the * symbol it means queue created is dynamic.

 If we removed '>' from queues.conf file and restart the ems server and run again same process then we will get Not allowed to created destination error.


In case of JMS Queue Requestor activity palette there is no need to mention reply queue name. TIBCO BW/EMS creates dynamic reply queue for this.

Note the reply queue name is empty.



You can see in red box that EMS has assigned dynamic queue for sending reply back to JMS Queue requester.

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 ...
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