IND +91 8688888976
Email : email@example.com
⇒ ConnectivityThe Connectivity function encapsulates the transport and target application interface by connecting each integrated application to the transport function. In the EAI world, the connectivity function is provided by adapters and connectors. ⇒ Transport Transport performs two important functions: ⇨ Moves the data across the network. ⇨ Facilitates some of the key aspects loose coupling, most importantly temporal and technological de-coupling. ⇒ Transformation & Routing In almost all integration activities, transformation from source format to target format is required. The base transformation process involves format modifications (both syntax and semantic mapping). More sophisticated transformation services offer message augmentation (message boosting) or data cleansing (for example removal of duplicates) that may be required to handle the differences between the to-be-integrated applications.
Except for basic point-to-point integration routing of messages is a key component of an integration solution. These message routing activities encompass: Managing the delivery of the messages over communication connections, including protocol conversion, flow control, guaranteed delivery, and connection optimization (for example, connection pooling) Multi-point message decomposition/re-composition, enabling one to many and many to one message routing Content-based routing with associated directory-based or rules-based routing.Transformation and routing function are typically provided by the same component of an integration broker and for that reason we group them together. Task FlowThe Task Flow Management function of the broker coordinates relatively simple, short time activities amongst the integrated systems. Task flow management allows for re-combining applications functionality to yield a more complex functionality.
Rendezvous software suite includes two main components—a Rendezvous programming language interface (API) and the Rendezvous daemon.The Rendezvous daemon runs on each participating computer on your network. All information that travels between program processes passes through the Rendezvous daemon as the information enters and exits host computers. Rendezvous software allows looser coupling between the components of a distributed system. Loose coupling decreases costs for development, operation and maintenance, and increases system longevity. Rendezvous software uses subject-based addressing™ technology to direct messages to their destinations, so program processes can communicate without knowing the details of network addresses or connections.
To better understand the concept of RV, lets go thru some of the Networking Basics –⇒Connection-Oriented and Connectionless Protocols ⇒ Connection-Oriented Protocols: These protocols require that a logical connection be established between two devices before transferring data. This is generally accomplished by following a specific set of rules that specify how a connection should be initiated, negotiated, managed and eventually terminated. Usually one device begins by sending a request to open a connection, and the other responds. They pass control information to determine if and how the connection should be set up. If this is successful, data is sent between the devices. When they are finished, the connection is broken. Example : tcp/ip, ftp, telnet⇒Connectionless Protocols:These protocols do not establish a connection between devices. As soon as a device has data to send to another, it just sends it.Example : udp
⇒RV runs on TRDP – TIBCO Reliable Datagram Protocol. It is implemented by rvd. TRDP is built on top of UDP and adds a sequence number to each outbound packet. TRDP uses buffer to store outbound messages for specific interval (Typically 60 sec.) If message packet is lost, the consuming rvd requests retransmission.⇒In contrast to TCP/IP which is pessimistic, TRDP is optimistic: it assumes messages will arrive at their destination. If the message is lost, then TRDP sends negative acknowledgement (NAK) requesting retransmission.If stronger delivery assurance is required, RV Certified (RVCM) or RV Transactional (RVTX) is used.⇒ RVCM uses ledger files at both Publisher and Subscriber ends. These ledger files stores messages, and these messages sit in ledger file until it gets confirmation from all receivers.
⇒Computer hardware and operating system platforms use different conventions for data representation. Data from one platform can be unintelligible on another platform ⇒Messages are the common currency that Rendezvous programs use to exchange data. Rendezvous messages contain fields of self-describing data. Every message has a subject name, which describes its destination. ⇒ All data that enters or leaves a program through the Rendezvous daemon must be encapsulated in the fields of a message. As an abstraction, a message is a collection of self-describing data fields, Fields ⇒Each field contains one data item of a specific datatype. Programs can identify and access the individual fields of a message either by name or by numeric identifiers. ⇒From the programmer’s point of view, a message is a set of fields. Programs manipulate messages using API calls. Wire Format ⇒At a lower level, beyond these abstract operations, each message exists as a byte sequence in Rendezvous wire format—a uniform representation suitable for network communication among diverse hardware, operating system.
⇒ The software mechanism for sending and delivering messages is called a transport. A transport defines the delivery scope—that is, the set of possible destinations for the messages it sends. Network Transport Parameters ⇒ Several independent distributed applications run on the same network, and you must isolate them from one another (service parameter). ⇒ Programs use the Rendezvous routing daemon, rvrd, to cooperate across a WAN with programs that belong to a particular service group, and the local programs must join the same service group. ⇒ A program runs on a computer with more than one network interface, and you must select a specific network for outbound multicast Rendezvous communications (network parameter). ⇒ A program runs on one computer, but connects with a Rendezvous daemon process running on a different computer, and you must specify the remote daemon to support network communications (daemon parameter).
⇒Create a Process ⇒ Use RV Publisher and RV subscriber activities. ⇒ Use RV subscriber as Startup activity⇒Listen on Subject “Input”⇒Use transition to send this message to RV publisher activity.⇒Publish the same message using RV publisher on subject “Output”.⇒Use tibco send to publish a sample “DCOTG” on subject “Input”.⇒Use tibco listen to listen on “Output” subject.⇒Go to test mode and test this sample application.⇒Observe – Observe the directory structure of your project
IND +91 8688888976
Email : firstname.lastname@example.org