Skip to main content

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.

Distributed Queues:
RV provides delivery of messages to one of the n members of a server group. When multiple subscribers are there listening on a subject the messages are distributed among them in distributed queues.

Fault Tolerance:
To ensure proper functioning of a program in case of failover situation, programs can be configured in FT (Fault Tolerance) mode in RV. This makes sure that if one program fails then the other starts processing and hence provides rapid recovery from such failures.

Protocols: PGM and TRDP

During installation you can chose between the two protocols.

PGM: Pragmatic General Multicast (PGM) uses reliable delivery. It uses Negative Acknowledgement (NAKs), NAK Confirmation (NCF) and Repair Data (RDATA).

TRDP: Tibco Reliable Datagram Protocol (TRDP) is a 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].

Security:

Rvd and Rvrd communicate with programs over non-secure TCP connections.
RV can be configured with Secure Socket Layer (SSL) to add security feature for applications.

Security is implemented over below three areas of communication:
§  Client to daemon
§  Between routing daemon neighbors
§  Browser to daemon

RV provides two daemons for secure connection:
RVSD: the Rendezvous secure communications daemon, corresponding to rvd
RVSRD: the Rendezvous secure routing daemon, corresponding to rvrd 
Labels:

Comments

Post a Comment

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...
Post a Comment
Read more

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. *********************************************************************************************...
Post a Comment
Read more