TIBCO | Types of variables

-
In this post we will discuss about different types of TIBCO variables. TIBCO application can uses any of this variables to manipulate data and logic.

TIBCO variable types are as follow

  1. Global variables
  2. Process variables
  3. Shared variables




Global variables

Global variable are used mainly for setting env variables such as JMS/HTTP/RV connection details. This are useful as those can be change at deployment time.

Process variables

Process variables are used for getting process level information. This information can be accessed while mapping some parameters in any of the BW activities such as Mapper activity. The $_processContext variable is available to process level info such as process id, ProjectName, EngineName, TrackingInfo etc.

Shared variables

There are two types of shared variables
  1. Shared variables
  2. Job shared variables
Shared variables allows TIBCO BW process to share data across process instances. Multiple process instances can read and write data to this shared variable. As all process instances are using this variable it is necessary to put this variable in critical section while writing data to this variable. 

Job Shared variable allows TIBCO BW process to share data in that job only. If any of the other process is using this variable then they might get different output value. This is useful for passing data in sub processes. 

Below is example of how Shared variables are implemented in TIBCO BW.














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