Skip to main content

Tibco Rendezvous (RV): Intro


When I started working on Tibco RV, I used to get stuck on many things. Small, big but the main problem was that I couldn’t find much online as a resolution. Information was limited and distributed. So here’s my try to bring all that I know to one place about RV and provide solutions to as many issues as possible.

Intro:

For large enterprises, the most fundamental need is the data transfer from one system to another. The messaging model used must be efficient, reliable and scalable. Tibco RV is used by applications running on distributed platforms to exchange data for Enterprise Application Integration (EAI). Tibco Rendezvous has more than 2000 customer installations and is the leading messaging system for real-time and broad data distribution. Tibco RV is used in Replay Service, Reuters Wireless Delivery System, Reuters Market Data System and Internet Finance Platform.
Tibco RV is used by distributed applications for communicating data. It provides both point-to-point and multicast messaging service.

It has a publisher/sender that sends the message and subscriber/listener that receives the message. It provides Rendezvous Daemon (RVD) for communication over same network and Rendezvous Routing Daemon (RVRD) for routing to other networks.
There are two main components of Tibco RV: RV API Library and RV Daemon

RV API: Rendezvous programming language interface. Tibco RV has different APIs for different programming languages like in C, C++, Java etc.

RV Daemon: It is a background process that runs on each server and RV communication is done through daemon. It receives the message and delivers it to the right place.

Why use RV?

What makes it preferable is its high speed messaging and multicast ability along with certified messaging without bearing the complications of knowing network details as it supports subject based addressing.

So if data needs to be sent to multiple customers and with high speed then RV is a good option. For example: In order to send one UDP packet to 1000 consumers, through RV it is sent on the wire only one time. And with TCP protocol it will send IP packets out 1000 times. This is what multicast does.

It supports TRDP protocol that runs on top of User Datagram Protocol (UDP). It includes message numbering and Negative Acknowledgement [only the message that is not received sends negative acknowledgement]. So the message traffic is reduced as there is no acknowledgement for the messages being successfully delivered.

Where to use RV?

RV supports multicast so if there’s a need to send messages to 1000 customers then instead of using TCP which will create 1000 different TCP connections, use RV as it will publish one message on the subject and it is received by all the 1000 customers. This makes RV very fast and cheap too. Hence it is widely used in banks/stock markets.

RV Vs EMS:

RV is used mostly for small packets where speed is more important instead of reliability. Whereas EMS is used where reliability is more important, data is critical and cannot compromise on losing any message.
To overcome this Tibco RV provides certified messaging which can be used for sensitive data if using RV.
Moreover, as Tibco EMS server is single point of failure if it goes down all traffic is blocked but in Tibco RV there is no single point of failure and if one node goes down others can still communicate with each other.
The requirement determines which tool to use. To put it simply we can say that Tibco RV is like a Radio and EMS is like a telephone. If you want to send a message/information to a whole city then you’d prefer to broadcast it. And if you need to send a message to an individual you’d use a telephone.

Conclusion:

Tibco RV provides high speed data transfer like for publishing market data. It can be implemented over a range of hardware platforms and programming languages and can be optimized for peer-to-peer or multicast messaging. A centralized daemon makes it cost effective too. With high performance, flexible and scalable data distribution Tibco RV is extensively used in enterprise application integration (EAI). All these features make Tibco RV the most preferable messaging model.

=====================================================================

Other Topics :


Comments

Popular posts from this blog

Tibco Rendezvous (RV): Transport and More

Transport: It is the mechanism for sending and delivering messages. There are three main parameters in Tibco RV for transport: network, daemon and service. Service is specific to programs. Multiple programs may be running on a network. Each program has a different service. There can be many services running under a daemon for different programs. Network parameter specifies the interface for multicast communication from a program. A specific network should be selected for  outbound multicast Rendezvous communications. Daemon specifies the port where RV daemon runs. RV communicates through this daemon and hence remote daemon must be specified to support network communications. Tibrvsend and Tibrvlisten: Every Tibco RV installation provides these two utilities for sending and receiving messages on any multicast network. Sample for testing these utilities: tibrvlisten.exe -service 7576 -network 10.21.6.38 -daemon tcp:7500 "TEST" tibrvsend.exe -s...

Tibco Rendezvous (RV): Features and More

Features of Tibco RV: Decoupling and Data Independence : In RV the applications are loosely coupled and RV has self-describing data that makes it easy for the applications to share data. Location Transparency : RV is based upon subject based addressing. The data/messages are sent and received over subject; hence the programs can communicate without knowing the network details. Architectural Emphasis on Information Sources and Destinations : RV provides efficient solutions for developing distributed system by emphasis on identifying sources and destinations of information. Reliable Delivery: RV provides reliable delivery of messages and without the need of network details. The information like network details and packet transfer are hidden. Certified Message Delivery: Some applications require more assurance for message delivery. For this RV provides Certified Message (CM) delivery which sends the confirmation for the messages received. Distribu...

How to add JCO Trace?

Requirement: To debug an issue and to check the data flowing through Tibco R3 adapter enable SAP JCo trace. Once the trace is enable it creates JCo tracing files in the specified location. These files have details of the JCo library, versions and JCo paths. It will show a complete trace log of the fields/segments in the adapter and it's tables and the input/output data that is flowing through the adapter. ************************************************************************************************************************************************ Steps: Add below properties in the adr3.tra file to enable SAP JCo trace: ===== java.property.jco.trace_level=8 java.property.jco.trace_path=<The path of the directory where the JCo trace file will be generated> ===== Restart the SAP adapter instance. Once you test, the JCo files will be created in the specified location. *********************************************************************************************...