Skip to main content

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 -service 7576 -network 10.21.6.38 -daemon tcp:7500 "TEST" "Sending message"

Point-to-Point and Multicast Messageing:

Tibco RV supports point-to-point messages in which only one receiver can receive the messages and it can listen several times to the same subject/inbox name. One process can receive multiple copies of the message by listening several times to the same subject/inbox name, but two processes cannot share a subject/inbox name.
In multicast multiple receivers/subscribers can listen to the same subject and receive the same messages. Multicast messages are just like radio broadcasts; the sender picks a frequency, and any listener who tunes to that frequency receives the broadcast message. The public subject name is analogous to a radio frequency; any program that listens for a subject receives all messages sent on that subject name.

Interactions in RV:

There are three types of interactions in RV:

Publish/Subscribe: Sends information to multiple programs.
Request/Reply: Sends request to individual program and receives response from it.
Multicast request/reply: Sends request to multiple programs and receives response from all.

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

Other Topics :


Tibco Rendezvous (RV): Intro
Tibco Rendezvous (RV): Features and More
Tibco Rendezvous (RV): Virtual Circuit, Fault Tolerance and Current ValueCache
Tibco Rendezvous (RV): Monitoring and Troubleshooting
Labels:

Comments

Post a Comment

Popular posts from this blog

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...
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