RVRD Information: RVD (Rendezvous daemon) vs RVRD (Rendezvous Routing Daemon) RVRD (Rendezvous Routing Daemon) are simply

process owned by middleware or netwo rk teams which listens multicast traffic locally and transmit it to another RVRD counter part (another host) using TCP. This remote host than re multicast this traffic to there own network. So essentially it used to bridge two different reg ional network e.g. London and Newyork etc. RVRD is multicast in one end and unicast on other end so it receives messages fr om multiple RVD (Rendezvous Daemon) and send via TCP to another RVRD which distr ibutes messages on different RVD (Rendezvous Daemon) on there own network e.g. s ay on NY network. Control of RVRD (Rendezvous Routing Daemon) resides on middleware/network team a nd they decide which topics/subject is allowed for RVRD (Rendezvous Routing Daem on) traffic. So if you send message on a topic which is not configured on RVRD and subscriber for that service is on some another physical network it will not receive those messages until that topic is enabled on RVRD (Rendezvous Routing D aemon) front. On the other hand RVD (Rendezvous Daemon) is a background process runs on every host which wants to send or receive message from tibco multicast network. Your p rocess depends upon this for reliable and efficient network communication. all m essages goes via rvd before it enters or leaves host on a multicast network and RVD (Rendezvous Daemon) is responsible for creating packets or assembling packet s to and from the network. On points -- RVD transmit outbound message from your program to network. -- RVD delivers inbound message from network to your process. -- RVD takes care of Operating system specifics and encapsulates those leaving y our process independent of such low level details. -- RVD daemon can be start automatically if its not running already ,may exit af ter some specified period of inactivity. 1. Start RVRD on both the boxes, i.e. box A and box B, which are in two differen t subnets. 2. Open the http interface of both the RVRDs in two different browser instances. 3. Click on the router link, add a unique router name for both the instances. 4.Then click on the local network link on the same page (which will be initially shown as 0), add the local network name, service, network specification and cos t and click on add. 5. Then go to the routers link, click on the neighbours link (initially shown as zero), in the remote end point, put the hostname/ip address of the other RVRD b ox as well as the router name for the other RVRD and add the neighbor interface. In the port, use a TCP port that has been opened by your firewall. In this page , you can select on the type of your neighbors as well, i.e. accept any, passive etc. Default is ACTIVE-ACTIVE, i.e. any of these two RVRDs can initiate a conne ction to the other RVRD. 6. Follow step 4 and 5 for the other RVRD too. 7. Wait for some time and then click on the "Connected Neighbors" link to see if the connection is established between these two RVRDs.

click on the local network name from the routers page and specify the export/import list of the subjects. Now for data communication. which match thes e export/import subject. 9. This will enable your R VRD to send and receive the messages to/from the other network. Try a tibrvlisten/tibrvsend test on one of the exported/imported subject on b oth sides to check that the communication is happening. .8.

Sign up to vote on this title
UsefulNot useful