1. What is TIBCO BE and why it is used?
Ans: TIBCO BE is a well known software system for
processing complex business events to draw useful meanings from them to better
predict the business changes and to take proper actions accordingly.
2. What is the role
of channels and destinations in TIBCO BE?
Ans: Channels are resources which are used to
enable connectivity and communication between TIBCO BE and other sources like
JMS sources, RV sources or HTTP sources.
Destinations are defined within a channel and
they specify the source and sink for the message. For example, when you
create a destination for a JMS Channel; it contains details about the
destiantion queue name, delivery mode etc.
3. How events are
generated in TIBCO BE?
Ans: Event instances get created based on the
messages coming as input from the channels.
4. What are rules
and how TIBCO BE rules work?
Ans: In TIBCO BE, Rules specify the actions that
need to be taken based on certain conditions. Rules are triggered based on
events when conditions are met.
5. What is
difference between Rule Functions and Virtual Rule Functions?
Ans: Rule Functions are the functions
written in Rule Language with complete body while Virtual Rule Functions are like
interfaces without body.
Body implementation of Virtual Rule Functions is
made through decision tables instead.
6. What is the
relationship between decision tables and Virtual Rule Functions?
Ans:
Decision tables are the body implementation of Virtual Rule Functions. A
Virtual Rule Function can have one or more decision tables for its body
implementation.
7. What is RMS and
why it is used?
Ans: Rule Management Server (RMS) is a component
of BusinessEvents, which manages decision projects and provides a mechanism for
approval. It also provides user authentication, decision project authorization,
and other project management features. Decision Manager communicates with Rules
Management Server to check out decision projects, update local copies of decision
tables, and commit changes. RMS users can then approve or reject those changes.
8. How can we
prioritize and De-prioritize rules for an event?
Ans: For a cetain event, we can have multiple
rules available. The Priority value of any rule decides the sequence
in which rules are triggered. A value closer to 1 means higher priority.
9. Describe the
purpose and usage of TIBCO BE Concepts?
Ans: Concepts are created to hold the properties
of any entity. Normally, information from the Events is used to create
instances of the Concepts in the Rules and Rules Functions.
10. What is event
PreProcessor and why it is used?
Ans: Event PreProcessor is basically a Rule
Function. This rule function is used to process the incoming messages before
they are converted into Events.
11. Why
Scorecards are used in TIBCO BE?
Ans: Scorecard is a type of concept in BE.
Scorecard acts same as a static variable in any progamming language with
project wide scope and having only single instance. Scorecards are used in
order to track or store such information which has to be used throughout the
inference agent.
12. Describe the flow
of messages in TIBCO BE?
Ans: Messages are received through Channels with
specified destinations.
Event PreProcessor is executed first (if it
exists in the project).
Incoming message is converted to an event.
Rules are triggered based on event.
13. What is CDD
and what’s its significance?
Ans: CDD (Cluster Deployment Description) is an
XML file which contains all required information about deployment of a TIBCO BE
project.
14. How we can
integrate TIBCO BW with TIBCO BE?
Ans: Based on the type of channel configured in
TIBCO BE, you can send messages from TIBCO BW and receive the responses. For
example, If TIBCO BE has JMS Channel configured, you can send JMS messages to
the specified destination from TIBCO BW using Send JMS
Message activity and then you can receive a response as well
using Receive JMS Message activity.
Similarly, you can communicate for HTTP, SOAP, RV
or any other types of channels as well from TIBCO BW.