Tutorials Point | Tech Blog

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.