TIBCO | EMS Message Transfer Utility

-
In this post we will be creating TIBCO EMS utility to transfer messages from one EMS instance to other EMS instance(from Domain 1 to Domain 2). Developer needs to keep some utilities handy to resolve production issues. Some times it happens that due to wrong EMS configuration in deployment  steps messages meant for DOMAIN-1 get routed to DOMAIN-2 or other domains  and piled up there. This messages can not be purged as messages are important from enterprise point of view(Order messages, transaction messages). Below steps will create TIBCO BW utility to transfer messages, we can also create same utility with help of Java code. 


Basic idea is simple. We will create two JMS connections and transfer messages using JMS Queue receiver and JMS Queue Sender activity.

Step 1 : Create two JMS connections objects(Domain -1 & Domain -2)






Keep JMS connection details such as username/password/url in Global variables so that they can be changed at deployment time. 

Step 2 : Create Process with JMS Queue receiver, JMS Queue Sender and confirm activity.



Keep the ACK mode of JMS Queue receiver to Client ACK for not auto confirming messages.




Map message body of JMS Queue sender with JMS Queue receiver body.



Messages from Domain 2 are received on JMS Queue receiver and sent to JMS Queue Sender of Domain 1. Keep source/destination queue names in GVs. As you can see above I have kept JMS Max Sessions as 1 to test code, we can keep it to 10. At last we are confirming the messages received on Domain 2 once they are sent to Domain 1. We can keep Write to Log activity to check status or we can check messages on both queues from GEMS(Graphical EMS) Admin tool.

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