TIBCO | Changing global variable without modifying GV file

-
TIBCO provides global variables to change env and other constant variables. This can be achieve via below ways.

  1. Changing GV value in admin console
  2. Specifying GV value in TRA file of application
Admin user can simply change GV value of application using application management console in TIBCO Administrator.

Same can be achieved via specifying GV value in TRA file of application. This method uses same approach explain in this post. 

Step 1 : Create a simple BW process which writes GV value in log file.



Create a simple process which will receive message on JMS queue receiver and then write GV value to log file.

 Step 2 : Deploy application in domain and send one test message to queue.


Check the log message in application tracing console. The current GV value is written in log message.

 Step 3 : Edit TRA file of application

Open the TRA file of application located under directory path 

/app/tibco/tra/domain/<<domain-name>>/application/<<app-name eg.TibcoTest>>

To change the GV value add below line as shown in image above. Specify full path of GV as below.

 tibco.clientVar.rohan/gv1=stark

 Step 4 : Restart application either via admin console or backend console.




As you can see the GV value defined in admin is still test1 whereas value logged in tracing is stark which is taken from TRA file.

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