TIBCO Enterprise Application Integration

Enterprise Application Integration (EAI) provides a common framework for integrating incompatible and distributed systems - making it faster and easier to tie together applications and Web Services so you can integrate them into business processes that span your organization. TIBCO's EAI solution lets your applications, databases and mainframes communicate and interact with each other by automatically routing and transforming information so it gets where it needs to be, when it needs to be there, and in the proper format.

Web Services Based Integration:

Integration of different systems by utilizing Service Orientation of Web Services has become quite common when It comes to enterprise applications. TIBCO BW provides quite handy and powerful resources for developing SOAP web services. Web Service Based Integration has many pros. Exposing web service operations allows a greater re-usability of the services and same web service allows endpoints for any number of upstream/downstream systems. Web service based integration also gives a greater power to the developer to ensure data correctness and a more stronger information security by utilizing security measures like digital certificates and password based authentication.

HTTP Based Enterprise Application Integration:

In many cases, communication between upstream or downstream system and TIBCO layer is through HTTP channel where payload is transferred through HTTP GET and POST options. HTTP based integration reduces the overheads and makes the integration simpler. There are some data validation and security problems also associated with this approach. All the data sent through HTTP channel must be properly validated, parsed and translated before using it for any further processing. 

RV (Rendezvous) Based Enterprise Application Integration:

Rendezvous is another commonly used protocol for message communication in TIBCO. RV is rapidly being replaced by EMS/JMS based communication in current age implementations; Its still widely available in many old implementations. RV based communication has many pros also associated with it. Unlike JMS; RV based communication doesn’t have any single point of failure (as no centralized server is used) and we can achieve guaranteed delivery of messages by utilizing Certified RV capabilities.

JMS Based Enterprise Application Integration:

JMS based communication is rapidly taking control replacing RV based communication mechanism in the projects being developed using TIBCO BW. The reason behind popularity of JMS/EMS is its efficiency as well as performance tuning features.

TIBCO Enterprise Message Service

TIBCO Enterprise Message Service (EMS) is TIBCO’s implementation of Java Message Service (JMS) with some enterprise-class enhancements. Java Message Service (JMS) is an API which provides facility/standards for creating, sending and receiving messages between two or more client applications. TIBCO has developed its own messaging platform called TIBCO EMS by adapting the standards/features of the JMS.

JMS supports (hence TIBCO EMS) two variants of messaging models:

1.  Point-to-Point:

               

In this messaging mode there is one producer and one consumer per message and this model uses the object call ‘queue’ to store the messages generated by producer until it was received by the consumer. Message producer sends the message to the ‘queue’ and the message consumer receives the message from the same ‘queue’.

2. Publish/Subscribe:

         

In this mode the message producer publishes a message onto to an object call ‘topic’ from here multiple message receivers is going to receive the same message. In this case message produceris known as publisher and message consumer is known as subscriber.