Tutorials Point | Tech Blog

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.

In this post we will check how to handle JSON datatype using TIBCO Designer. TIBCO Designer does not comes with built in JSON Palette in version 5.7.X. We need to install REST Plugin in order to use REST/JSON Palettes.  JSON  is lightweight datatype used in many systems mainly in web applications. JSON is lightweight as it does not require any XSD. We still can  use XML XSD in TIBCO to convert XML to JSON and vise versa. Activities : Render JSON - Converts XML data string to JSON String Parse JSON   - Converts JSON String to XML data string 

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. 

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. 

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.

In previous post we check how dynamic queues are created, in this post we will be checking how to configure JMS response queues. We can replace JMS Queue requester activity with JMS Queue Sender and wait for JMS design pattern. As TIBCO solution is implemented for large enterprises the LOAD balancing is important part. Normally single instance of TIBCO BW application is deployed in TIBCO Admin. For production environments multiple instances of same application are run on different machines for load balancing.

TIBCO provides EMS(Enterprise Message Service) for performing message communication with various system and internal processes. As explain in earlier post main purpose of EMS implementation is message transportation with reliable channel. TIBCO provides reliable message service by persisting messages in file store/DB stores etc. There is 100% guarantee of messages being delivered to receiver system. TIBCO JMS related activities are well explained in TutorialsPedia blog. In this post we will be covering dynamic queues, Request/Response dynamic queues.

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.

TIBCO BusinessEvents provides DecisionManger to generate certain results based on input conditions. This is useful when TIBCO BusinessWorks needs to call other processes based on input params. TIBCO BusinessWorks sends request to DecisionEngine in return BusinessEvents - DecisionManger will provide some results. In this post we will implement DecisionManager using XSLT & DB. One more advantage of this is that it uses DB to store input rules, so rules can be added at run time and cache can be refresh either via publishing simple message on topic or restarting the process instance.

As explained in earlier post TIBCO Designer is used to develop Enterprise middleware applications. It is necessary to follow certain structure to develop BW Project to ensure low complexity and easier component understanding. Standard structure also allows to follow certain software design patterns in enterprise applications.

TIBCO is most widely used middleware product in market. TIBCO is providing integration solutions from last 2 decades(1997 - Current). TIBCO provides solutions for Integration, Orchestration, Business Process Management and Analytics. TIBCO Products TIBCO AMX BusinessWorks (Aka TIBCO BW)

The last post was about what is EAI. In this post i am going to explain and use of different EAI products. In any software industry the EAI is must there to connect different components. There are SAP CRM systems, Billing systems, Salesforce systems, Oracle systems needs to be interconnected. There are different EAI products available in market. Based on the requirement the EAI product is chosen.

From Wikipedia's definition the Enterprise application integration (EAI ) is the use of software and computer systems' architectural principles to integrate a set of enterprise computer applications. But what it exactly mean? Before going to definition of EAI, think of legacy banking computer systems connected to each other in Ad hoc manner. Inventory component is storing large database of users. Accounting component manages complex calculations of end users. Front end components are consumed by bank officials and bank users. Each of this component is connected and requesting each other for information. Those components are used to connected point to point or one to many manner.