TIBCO | Taking ROOT Code of deployed BW Project

-
In this post I will be covering how to take root code of deployed TIBCO BW Project. Most of the times it happens with developers that code works on his machine but doesn't in deployed version. TIBCO deployed configuration can be downloaded and tested locally. 

This also help developers to restore the code version if same version of code lost from SVN. 




Step 1 :  Login into ADMIN server using WinSCP


Normally the TIBCO admin is installed on Linux machine as it is easier to handle admin tasks on Linux OS.



Step 2 : Go to root code folder and download the desired TIBCO BW Project root code.




Go to below path to find root code. Path may vary depending upon installation of admin. Copy code from datafiles folder to your local folder.

/app<var>/tibco/tra/domain/domain_name<var>/datafiles



Step 3 : Open code in TIBCO Designer and run to debug.

Once code is copied, it is available to open in TIBCO Designer. This helps to find bugs in deployed code. They can be wrong GV configurations, mapping errors etc.

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