1. What is EAI?

A.EAI is the unrestricted sharing of data and business processes throughout the networked
applications or data sources in an organization
2. What are the different types of integrations?

A. An enterprise system is made up of business processes and data. So when an IT expert

contemplates to use EAI technology, he has to first understand how these business processes are
automated and the importance of all business processes. This understanding will bring out a lot of
useful hints for determining the amount of work needed, how much time it will take, which
business processes and data are to be integrated etc. Apart from this initial and first task of
exploration, the primary knowledge needed is at what level, the integration process has to be
performed in an enterprise application as there are mainly four levels, such as data level,
application interface level, method level, and user interface level in an application.

1. Data-level EAI is the process and the techniques and technology of transferring data between
data stores. This can be described as extracting information from one database, if need,
processing that information, and updating the same in another database. The advantage of data-
level EAI is the cost of using this approach. Because there may not be any changes in the
application code and hence there is no need for testing and deploying the application resulting in
a little expenditure. Also the technologies providing mechanisms to move data between
databases, as well as reformats that information are relatively inexpensive considering the other
EAI levels and their applicable enabling technologies.

2. Application interface level EAI refers to the leveraging of interfaces exposed by custom or
packaged applications. Developers make use of these interfaces to access both business processes
and simple information. Using these interfaces, developers are able to bring many applications
together, allowing them to share business logic and information. The only limitations that
developers face are the specific features and functions of the application interfaces.

This particular type of EAI is most applicable for ERP applications, such as SAP, PeopleSoft and
Bann, which will expose interfaces into their processes and data, do so in very different ways.
The most preferred EAI technology for this type is message brokers as these can extract the
information from one application, put it in a format understandable by the target application and
transmit the information.

3. Method level EAI is the sharing of the business logic that may exist within the enterprise.
Applications can access methods on any other application. The mechanisms to share methods
among applications are many including distributed objects, application servers,and TP Monitors.
An ORB can take the call of one application to methods stored in other applications. An
application server can be a shared physical server for a shared set of application servers. Most of
the integration have been happening at this level as there are a number of robust technologies to
accomplish this type.

4. User interface level EAI is a more primitive approach. Architects and developers are able to
bundle applications by using their user interfaces as a common point of integration. For example,
mainframe applications that do not have database or business process-level access may be
accessed through the user interface of the application. This type is not a preferred one even
though on many occasions, this is the only way of approaching integration task.
3. Explain briefly what do you understand by Rendezvous? A. tibco rendezvous software
makes it easy for distributed applications to share information across a network. It also
enables the development of event driven applications. Rv supports nearly all platforms,
enabling, distributed applications to cooperate. RV works with common networking
protocols and provides reliable messaging . It communicates using broadast , multicat
and unicast interactions . Rv messages are produced and consumed based on logical
subject names.

4. What are the different types of Rendezvous transports? A. network, intra-process, or

Virtual circuit.

5. What are the three parameters passed to RVD? What are the default values for them? A.
Service=, Network=,Daemon=,

6. What are the two protocols used by Rendezvous? Explain each one briefly? A.TRDP TIB
reliable data protocol. A reliable transport protocol for ordered, duplicate free, data
delivery with in a single subnet. PGM pragmatic general multicasting. A reliable
transport protocol for ordered, duplicate free, data delivery over a group of
interconnected subnets.

7. Describe different types of communication enabled by RV?

TIBCO Rv supports the following four types of communication interactions”

• Broadcast-one to many
• Broadcast request/reply –one request to many, then many one to one replies.
• Point to point request/reply-one request, then one reply.
• Point to point-one to one
8. Explain Rendezvous architecture? Compare it with that of message queue? A.Tibco RV
is a bus based architecture with no centralized component or server to broker message
flow. it is a pure peer to peer architecture with publishers and subscribers fully
responsible for message production and consumption.
• Fully distributed, no single point of control
• No single point of failure
• A message travels the network only ones regardless of the number of subscribers.
• Event or demand driven

A message queue is a hub and spoke architecture with a centralized server that
controls message flow.
• Centralized component
• Easy to control message traffic
• Single point of failure
• A message travels the network at least twice.
• Demand driven only.

9. What does the callback handler do?

The callback handler is responsible for taking the received message from the RVD and
presenting to the application for processing callback functions perform the actual
 application specific work of responding to incoming messages. Although different
communication paradigms, in a simplified way an incoming event can be seen as the
request and the call back as the reply.
10. List the Rendezvous components. Describe the responsibilities of each component in
brief?
The daemon and the API are the two primary components of tibco RV.
The Rv daemon implements the TRDP protocol or uses the PGM protocol and, as such is
responsible for
• Delivering messages reliably, including message sequencing ,retransmission and
buffering
• Filtering messages by subject name
The RV API is responsible for providing the message data structure, for determining the
communication mode and for passing messages to and from the rvd.

11. What is RVRD? How is it different from RVD?

RVRD is rendezvous routing daemon. RVD is used to send messages with in a subnet .
But RVRD can send and receive messages beyond the subnet.

12. Explain the RVCM agreement.

A.RVCM involves a handshake agreement among senders and listeners to exchange
messages. In order for senders and listeners to enter into CM agreement they must identify
each other on the network. This is done by giving each of them a unique name. We can either
specify this name ourselves or leave it up to the software to generate a name. The generated
name can be different every time it is generated. So it doesn’t provide persistence.
This handshake can be set up automatically by the parties involved or we can pre-register the
listeners.
It is also possible for a CM sender to deny registration to a CM listener, in which case the
CM listener continues to receive messages with just reliable quality of service.

13. Explain ACID properties.

A. Atomicity: the transaction components act as a single unit. Either all take place or none of
them take place.
Consistency: system data is maintained in a consistent view; intermediate actions are not
posted until the transaction is complete.
Isolation: Intermediate activities are only visible to the transaction master.
Durability: once the transaction has been committed, it cannot be undone.

14. Compare RVRD with RVD.

A.RVD delivers messages to application on computers within a single network. Whereas
rvrd delivers messages beyond LAN boundaries. Rvrd forwards messages between
networks allowing application on one network to listen for and receive messages
from application other networks.
Rvrd subsumes rvd functionality so it is not necessary to run both on the same host

15. What is RVDS? How it addresses the requirements of data security?

TIBCO Rendezvous Data Security is an add-on product that leverages standard rv
functionality to deliver secure data communications in the TIB enabled distributed
environment. Key requirements of secure communications include data privacy, data
authentication, data integrity and access control.
Privacy: RVDS provides data encryption controls that authorize who may read a message
Authentication: RVDS provides digital signatures and certificates to verify the identify of the
message sender.
Integrity: RVDS provides digital signature and message integrity codes to guard against
message tampering.
Access control: RVDS controls the rights of users to send/receive messages with specified
tags that themselves specify the security methods applied.

16. What is the difference between RVCM and RVTX?

In RVCM the messages are delivered “at least once” where as in RVTX environment
messages are delivered and consumed “exactly once”.

17. In RVCM mode, what happens if?

• Certified sender sends message
• Dropped by network outage for 50 seconds
If a certified sender sends a message that gets dropped for 50 seconds , standard rendezvous
reliability resends the message. Because its within the 60 default buffer window. RVCM is
not activated.

18. What component in present in RVCM but not Distributed Queue?

CM Listener ledger file is present with RVCM but not Distributed Queue.

19. How does rvcache differ from DB?

Updates to rvcache are implicit whereas DB updates are explicit. Also rvcache stores only
current value.

20. What is direct communication? What is the advantage of it over RVD usage?
A. Two application programs can conduct eligible point to point communications without
intermediary rendezvous daemon processes. This arrangement can decrease message latency
and context switching for point to point messages. In the path through rvd each the daemon
can a add a small delay. The direct path avoids these sources of potential delay.

21. When will a message be eligible for direct communication?

A. A message is eligible for direct communication if it meets all of these conditions:
• The message has an inbox destination subject.
• Its sending transport object is eligible and enabled.
• Its receiving transport object is eligible and enabled.
• The network path between the sender and the receiver does not cross through
rendezvous routing daemon.

22. Explain Heart beat interval, Activation interval and preparation interval. What is the
relationship among them?
Each RVFT group member must specify a heartbeat interval. This interval is used t determine
the interval at which an active member will publish its heartbeat message.
The activation interval is the interval that an inactive member waits before becoming active
when no heartbeat signal is observed. All member of a FT group must specify the same
activation interval.
The member of a FT group may specify preparation interval. This parameter specifies how
long an inactive member needs to prepare before becoming active.
HB<Prep<Act(if prep!=0)
HB<Act(if pep=0)
23. What is RVRAD? When it is used?
Rendezvous relay agent daemon. Rvrad supports CM in situations where correspondents
connect only intermittently to the network. A common implementation of rvrad is to support
CM delivery among laptop computers that connect to the network intermittently. In such
situations rvrad collects messages on behalf of disconnected clients. When the correspondent
reconnects to the network , rvrad forwards the stored messages