TIBCO | Point local DEV environment to other environment

-
While developing or debugging TIBCO BW application there comes a situation where a developer needs to point its local dev project to one of the test environments.  TIBCO Designer provides feature to point to other environments without changing current Global Variables containing Dev properties(Such as JMS details). This important to debug the deployed code with current dev code. In coming post I will we giving steps to take deployed code(Root code) and debug it. 

With TIBCO Designer with can provide configuration file(.cfg file) and change the GVs before running code in test mode.

Step 1 : Give proper global variables names to JMS/HTTP connections.





As we can see GVs are named properly with each JMS property as variable. If we hard-code the connection details then we can't change this at deployment time. It is good practice to create GV for each configurable connection details.


Step 2 : Create configuration file(.cfg)

create a configuration file containing each GV. If you check above GVs JNDI URL as below structure.

ProjectName/JMS/Connections/JNDI/JNDI_Context_URL
Now concatenate above string as below.

tibco.clientVar.ProjectName/JMS/Connections/JNDI/JNDI_Context_URL=<<give here test environment jms connection URL>>

The final string will be as below

tibco.clientVar.ProjectName/JMS/Connections/JNDI/JNDI_Context_URL=tcp://localhost:7221,tcp://localhost:7222
tibco.clientVar.ProjectName/JMS/Connections/JNDI/JNDI_UserName=
tibco.clientVar.ProjectName/JMS/Connections/JNDI/JNDI_Password=
tibco.clientVar.ProjectName/JMS/Connections/JMS_Domain1/JMS_UserName=
tibco.clientVar.ProjectName/JMS/Connections/JMS_Domain1/JMS_Password=
tibco.clientVar.ProjectName/JMS/Connections/JMS_Domain1/JMS_QueueFactory_Name=domain1
tibco.clientVar.ProjectName/JMS/Connections/JMS_Domain1/JMS_TopicFactory_Name=
tibco.clientVar.ProjectName/JMS/Connections/JMS_Domain2/JMS_UserName=
tibco.clientVar.ProjectName/JMS/Connections/JMS_Domain2/JMS_Password=
tibco.clientVar.ProjectName/JMS/Connections/JMS_Domain2/JMS_QueueFactory_Name=domain2
tibco.clientVar.ProjectName/JMS/Connections/JMS_Domain2/JMS_TopicFactory_Name=

Save the file as env_name.cfg

Step 3 : Start the Project in test mode and give cfg file as argument. 



Select the process to run then click on Advanced button.



In  Test Engine User args give path of created CFG file as below and click OK.

-p "path_of_cfg_file"

Then run Project as usual. You can check configuration is correct via sending one test message to test env queue and receiving that message in Local TIBCO Designer. 

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