This is in continuation of my tibco tutorial series where I will discuss tibco rv on application developer point of view as middle ware or messaging solution.
As discussed in earlier tibco tutorials, tibco is used for communicating between two systems e.g. client and server or server to server , here we will see some of the basic terms used in tibco rv world.b
Main purpose of these tibco tutorials is to give overview of fundamentals of tibco rv with day to day examples and discuss its usage. I have been using tibco for more than 3 years and have used in my various project where I use tibco reliable messagging , tibco certified messagging for both client to server and server to server communication.
"tibrvsend" and "tibrvlisten" these are two utility comes with every tibco installation. One can used to send message on any multicast network while other can be used to receive message on any multicast network.
Here is an example of sending and receiving message in tibco multicast network.
tibrvsend -network "190.231.54.20" -service "5420" -daemon "tcp:7500" "TESTING”
tibrvlisten -network "190.231.54.20" -service "5420" -daemon "tcp:7500"
So here we see three new things network, service and daemon
Network
------------
This is the multicast network on which message will travel here it is "190.231.54.20"
It could be any IP address which is setup on your network router. If your computer has multiple NIC (network interface card) then eth0 or eth1 could be prefixed in network e.g.'
"eth0; 190.231.54.20"
normally different NIC card is used for different network speed e.g. eth0 could be a Gigabyte network or eth1 could be for Megabyte network.
Service
----------
This is the UDP port on which tibco rv sends message, its advised to keep last two digit of network as service e.g. here 54.20 is used as service "5420".
important point to note is "one service can be bound to only one network in one machine" e.g. here service "5420" is bound to network "190.231.54.20" if you try to bound it to another network "192.231.54.20" , tibco will throw error "Transport initialization failed".
This problem generally occurs when you are subscribing many networks in one machine.
Daemon
------------
This is the tcp port on which application communicates to rvd (rendezvous daemon), by convention its tcp:7500 but it could be anything as long as it’s not conflicting with others.
there is one more concept called "remote daemon" where tibco used daemon of different machine to communicate with multicast network it looks like "host:7500" where host is remote host , its not advised to used remote daemon , I will discuss this on a separate post.
rvd
------
I have referred it many times but not yet explained, it’s a program we called rendezvous daemon which is required for tibco messaging, if it’s not running on your machine you can not send/receive message in a multicast network. if its not running then application generally starts it but its a good practice to start rvd in permanent account. It is this process will handle everything from sending message to receiving message in tibco multicast network.
remote daemon
------------------
Some time instead of using local daemon ( rvd installed on local computer) we use RVD (Randezeous daemon) installed on some other remote host . this is called using remote daemon. so that remote daemon connects to our process via TCP and connect to tibco multicast network via UDP. see here how to use remote daemon.
C:\>tibrvlisten -service "5420" -network ";190.231.54.20" -daemon "tcp:remotehost:7500" TEST.REPLY
here we are connecting RVD (Randezeous daemon) running on host "remotehost"
this technique is useful if you don't have RVD (Randezeous daemon) installed in your host or your process is running on some virtual host which is not ideal for tibco installation.
reliable communication
----------------------------
reliable communication is what Tibco RV by defaults provide where RVD makes every effort to deliver the message to Receiver but delivery is not guaranteed, this is useful in case of high speed messaging where data becomes stale after few seconds and missing data can be tolerable . for guaranteed deliver Tibco provides Certified Messagging.
Hope this would be helpful.
If you have not read my other blogs on my "tibco tutorial" series here are the links :
tibco tutorial part 1
tibco tutorial part 2
tibco tutorial part 3
tibco tutorial part 4
Please let me know if you like this kind of tibco tutorial , if you have any doubt , questions related to tibco rv please post those as comment and i will try my best to answer those .
If you would like to discuss any tibco topic , Please suggest I would be happy to write tibco tutorial on those.
to learn more about tibco rv or tibco ems see my tibco tutorial series
As discussed in earlier tibco tutorials, tibco is used for communicating between two systems e.g. client and server or server to server , here we will see some of the basic terms used in tibco rv world.b
Main purpose of these tibco tutorials is to give overview of fundamentals of tibco rv with day to day examples and discuss its usage. I have been using tibco for more than 3 years and have used in my various project where I use tibco reliable messagging , tibco certified messagging for both client to server and server to server communication.
"tibrvsend" and "tibrvlisten" these are two utility comes with every tibco installation. One can used to send message on any multicast network while other can be used to receive message on any multicast network.
Here is an example of sending and receiving message in tibco multicast network.
tibrvsend -network "190.231.54.20" -service "5420" -daemon "tcp:7500" "TESTING”
tibrvlisten -network "190.231.54.20" -service "5420" -daemon "tcp:7500"
So here we see three new things network, service and daemon
Network
------------
This is the multicast network on which message will travel here it is "190.231.54.20"
It could be any IP address which is setup on your network router. If your computer has multiple NIC (network interface card) then eth0 or eth1 could be prefixed in network e.g.'
"eth0; 190.231.54.20"
normally different NIC card is used for different network speed e.g. eth0 could be a Gigabyte network or eth1 could be for Megabyte network.
Service
----------
This is the UDP port on which tibco rv sends message, its advised to keep last two digit of network as service e.g. here 54.20 is used as service "5420".
important point to note is "one service can be bound to only one network in one machine" e.g. here service "5420" is bound to network "190.231.54.20" if you try to bound it to another network "192.231.54.20" , tibco will throw error "Transport initialization failed".
This problem generally occurs when you are subscribing many networks in one machine.
Daemon
------------
This is the tcp port on which application communicates to rvd (rendezvous daemon), by convention its tcp:7500 but it could be anything as long as it’s not conflicting with others.
there is one more concept called "remote daemon" where tibco used daemon of different machine to communicate with multicast network it looks like "host:7500" where host is remote host , its not advised to used remote daemon , I will discuss this on a separate post.
rvd
------
I have referred it many times but not yet explained, it’s a program we called rendezvous daemon which is required for tibco messaging, if it’s not running on your machine you can not send/receive message in a multicast network. if its not running then application generally starts it but its a good practice to start rvd in permanent account. It is this process will handle everything from sending message to receiving message in tibco multicast network.
remote daemon
------------------
Some time instead of using local daemon ( rvd installed on local computer) we use RVD (Randezeous daemon) installed on some other remote host . this is called using remote daemon. so that remote daemon connects to our process via TCP and connect to tibco multicast network via UDP. see here how to use remote daemon.
C:\>tibrvlisten -service "5420" -network ";190.231.54.20" -daemon "tcp:remotehost:7500" TEST.REPLY
here we are connecting RVD (Randezeous daemon) running on host "remotehost"
this technique is useful if you don't have RVD (Randezeous daemon) installed in your host or your process is running on some virtual host which is not ideal for tibco installation.
reliable communication
----------------------------
reliable communication is what Tibco RV by defaults provide where RVD makes every effort to deliver the message to Receiver but delivery is not guaranteed, this is useful in case of high speed messaging where data becomes stale after few seconds and missing data can be tolerable . for guaranteed deliver Tibco provides Certified Messagging.
Hope this would be helpful.
If you have not read my other blogs on my "tibco tutorial" series here are the links :
tibco tutorial part 1
tibco tutorial part 2
tibco tutorial part 3
tibco tutorial part 4
Please let me know if you like this kind of tibco tutorial , if you have any doubt , questions related to tibco rv please post those as comment and i will try my best to answer those .
If you would like to discuss any tibco topic , Please suggest I would be happy to write tibco tutorial on those.
to learn more about tibco rv or tibco ems see my tibco tutorial series
