Tibco RV sends and listens for confused parameters

Question

Hi, I am new to Tibco RV. After reading the concept of Tibco Rendezvous, I am still confused by the transport parameters: service, network, daemon.

So, conceptually, only one daemon runs on each machine. Therefore, when using tibrvsend:

tibrvsend -service 2323 -network "someIPAddress" -daemon "myDaemon" MESSAGE 

myDaemon this mean that I am sending a message using port 2323 on my local hosting, through the myDaemon daemon (which may be remote), to the comeIPAddress network?

When using tibrvlisten:

 tibrvListen -service 2323 -network "someIPAddress" -daemon "myDaemon" 

Does this mean that I listen using any available port, any available daemon on my local hosting to listen to messages from port 2323 from myDaemon "published on someIPAddress network?

Another question: in the book "Tibco RV Concept" it is mentioned that the same service cannot be tied to two networks. Is this used only for manufacturing machines (since we do not specify a port for the listening machine)? Thus, an error occurs if we do:

 tibrvsend -service 2323 -network "net1" MESSAGE 

and

 tibrvsend -service 2323 -network "net2" MESSAGE 

at the same time (this is normal if we do it consistently, right?)

but for listeners:

 tibrvlisten -service 2323 -network "net1" 

and

 tibrvlisten -service 2323 -network "net2" 

should be fine? (otherwise, this means that manufacturers must know each other's port number in order to avoid conflict)

If I completely mixed up these concepts, could you explain the examples?

Answer 1

So, conceptually, only one daemon runs on each machine

You may have several daemons running on the same machine, but this is not necessary. You can access multiple logical buses on the same daemon by changing the service and network settings.

A daemon is the actual process running on your computer to process Rendezvous messages. Your clients connect to this daemon using the daemon parameter. For instance. the default tcp:7500 will have access to daemons on the local computer on port 7500, while the tcp:server.domain.com:8000 value will access the daemon on the remote computer (server.domain.com) on port 8000.

Example: if you run tibrvlisten -daemon tcp:8000 , you will notice that a new process is running on the computer (rvd.exe on Windows, rvd on Unix) listening on port 8000.

Service and network parameters, in turn, are multicast parameters (see http://en.wikipedia.org/wiki/Multicast ). To simplify, you can consider them as fairly abstract meanings with two important aspects:

• The message producer and consumer must be configured to use the same network / service pair
• You should not reuse the service for multiple networks, as this conflict will cause problems.

Another thing to consider with respect to Rendezvous is that multicast messages are accepted by all machines on the same subnet. If you need to send messages to other subnets, you should consider using Rendezvous Routing Daemons (RVRD).