TIBCO‘s information bus (TIB)
一、introduction
===============================
Examples of Valid Subject Names:
===============================
1. NEWS.NATIONAL.ARTS.MOVIES.REVIEWS
2. CHAT.DEVELOPMENT.BIG_PROJECT.DESIGN
3. News.Sports.Baball
4. finance
5. Long.subject_name.is.valid.even.though.quite.uninformative
金融支持===============================
Examples of INVALID Subject Names: 人正常体温是多少
===============================
News..Natural_Disasters.Flood
- Invalid null element in subject string
WRONG.
- Invalid null element at the end of the subject string
.TRIPLE.WRONG..
Invalid subject string with three null elements
===============================
Rerved Names
===============================
葡萄酒种类
_INBOX.
- Inboxes are subject names ud for point-to-point message delivery
- All system generated inbox names begin with this prefix
_LOCAL.
- Subject names with this prefix are ―local‖ to the TIBCO Rendezvous daemon
- The messages do not reach the network
_RV.
- Subject names with this prefix are TIBCO Rendezvous advisory messages
_RVCM.
- Subject names with this prefix indicate internal administrative messages associated with certified message delivery
故宫讲解- Application programs must not nd to subjects with this prefix
_RVFT.
- Subject names with this prefix indicate internal administrative messages associated with TIBCO Rendezvous fault tolerance software
- Application programs must not nd to subjects with this prefix
Publish/subscribe messages are like radio broadcasts; the nder picks a frequency, and any listener who tunes to that frequency receives the broadcast. The broadcast subject name is analogous to a radio frequency. Any application that listens for a subject receives all messages bearing that subject name.
The Rendezvous Daemon (rvd) is a runtime background process that implements TIBCO
Reliable Datagram Protocol (TRDP). The daemon nds, listens for, filters and routes subject-bad messages reliably, detects lost messages and requests re-transmission. Daemons can be started automatically or manually.
The Rendezvous API supplies the message structure and communication type and pass messages to the daemon via a TCP connection. Usually a Rendezvous daemon is run on the same machine as the Rendezvous application but remote daemon connections are possible.
Connection Stack
In the above slide the various layers of the stack pass up traffic, but only if a higher layer has registered interest in some manner.
The Network Interface Card (NIC) will only process network traffic which meets one of three criteria:
- Own hardware address
黄瓜汤怎么做好吃- Broadcast
- Address contained on Multicast table
梦见杀人The NIC Driver will process and forward traffic which is registered at the TCP/IP layer
The TCP/IP layer will only forward traffic which is routed to an open TCP/UDP port, e.g. 7500/UDP default for the TIBCO Rendezvous daemon
游戏名女生简单气质
The TIBCO Rendezvous daemon will only forward traffic on which a connected consumer application has registered subject interest, and only after the complete message has been received
TRDP is implemented by the TIBCO Rendezvous daemon (rvd). TRDP adds a quence number to each outbound message packet. TRDP us a buffer to store outbound messages for a specified interval. If a message packet is lost the consuming rvd requests retransmission. Buffer operations are private to the TRDP implementation; there is no API to access it.
夹耳朵旁是什么字TRDP is optimistic: it assumes messages will arrive at their destination. Only if a message is lost will TRDP nd a negative acknowledgement (NAK) requesting retransmission. Compare this with TCP which is pessimistic: explicit acknowledgment of each received message is required.
The default buffer interval is 60 conds and should not be incread. If stronger delivery assurance is required, Rendezvous certified (RVCM) messaging should be ud
TIBCO Rendezvous Certified Messaging
While standard Rendezvous communication is highly reliable, business requirements often dictate the need for even stronger assurance of message delivery. RVCM fulfills this need, guaranteeing the delivery of each message at its intended destination.
Standard Rendezvous reliable subscribers can receive certified messages published on a subject that they have subscribed to. However, they will not participate in recovery attempts at the API level (as you will find detailed later in this unit).
