Interview Questions
« Previous | 0 | 1 | 2 | 3 | 4 | Next »

1.What is the difference between JMS and TIBCO EMS?

TIBCO EMS is a customization of JMS specifications by TIBCO. The difference between JMS and TIBCO EMS is that JMS provides two types of delivery modes which are Persistent and Non-Persistentwhile TIBCO EMS adds another type of delivery mode which is RELIABLE delivery mode.
Also, for restriction of messages acknowledgement, JMS provides NO_ACKNOWLEDGE mode whileTIBCO EMS extends the functionality of JMS by providing EXPLICIT_CLIENT_ACKNOWLEDGE mode and EXPLICIT_CLIENT_DUPS_OK_ACKNOWLEDGE mode.

2.What is the difference between TIBCO EMS PERSISTENT, NON-PERSISTENT and RELIABLE delivery modes?

In PERSISTENT delivery mode, messages sent by the producer to the EMS Server are persisted/stored in a disk and a confirmation is sent to the producer for every message.
In case of Non-Persistent delivery mode, messages sent by the producer are not stored/persisted on EMS Server. Acknowledgement is sent back only if authorization is enabled.
In case of RELIABLE delivery mode, messages are not persisted and also, no acknowledgement is sent back to the producer.

3.What is the difference between Static and Dynamic destination queues?

Static EMS queues are created using EMS Administrator or by configuring directly in the configuration file (queues.conf) and are permanent and can be used at enterprise level. Static queues have a permanent TTL (Time To Live) and they exist till the time they are deleted manually.
On the other hand, dynamic queues are short lived queues which are created when needed and get expired once they are not in use. Dynamic queues remain alive until at least one client is associated with them.

4.Which command is used to delete all the messages from a queue or topic?

Purge command is used to delete all the pending messages from a queue. For example, if you want to purge a queue named ‘queue.ajmal’; you can run following command in TIBCO EMS Administrator:

5.What is the difference between Queues and Topics?

The difference between TIBCO EMS Queues and Topics is that Queues are based on point to point communication model with only one consumer for each queue while EMS Topics are based on Publish/Subscribe model where messages are multicast to more than one consumers from a topic

6.What are TIBCO EMS bridges and why bridges are used?

Bridges are used to connect multiple destinations (queues or topics) so that same message can be sent to multiple destinations. When a bridge exists between two queues, the message is delivered to both queues.

7.Which configuration file is used for creating and configuring bridges in EMS?

bridges between destinations are configured in a configuration file named as bridges.conf

8.Which configuration file has EMS Server configurations stored?

All EMS Server properties are configured in the file tibemsd.conf

9.What is the difference between JMS Queue Receiver and JMS Queue Requestor Activity?

JMS Queue Receiver is a process starter activity that starts a process whenever a new message is available in a queue while JMS Queue Requestor is a non-starter (normal) activity which is used to request for a message to a queue and gets back a response.

10.Can we use Multicast on queues?

No, multicast can be used only for topics. Queues are point to point and can’t be used for multicast.

11.What is Tibco ?

Tibco makes integration server software for enterprises. An integration server allows a company to mix packaged applications, custom software, and legacy software for use across internal and external networks. Tibco's patented approach is called Information Bus (TIB)and Tibco says that it has been used in financial services, telecommunications, electronic commerce, transportation, manufacturing, and energy.
Active Enterprise is Tibco's integration server package that supports both message-bus and hub-and-spoke integration server models. The message-bus model connects the different applications to a common backbone using application adapters. The hub-and-spoke model connects all applications to a central server. Tibco's latest addition to Active Enterprise is Business Works, which uses Web Services technology.

12.What is the role of TRA?

TRA stands for TIBCO Runtime Agent. The TRA has two main functions:

  • Supplies an agent that is running in the background on each machine. The agent is responsible for starting and stopping processes that run on a machine according to the deployment information. The agent monitors the machine. That information is then visible via TIBCO Administrator.
  • Supplies the run-time environment, that is, all shared libraries including third-party libraries.

13.What are the revision control system options available in TIBCO designer?

  • File sharing
  • VSS
  • Perforce
  • XML Canon
  • ClearCase
  • iPlanet
  • PVCS

14.What are the different modes of service invocation?

Services can be invoked in several ways.

  • A one-way operation is executed once and does not wait for a response.
  • A request-response operation is executed once and waits for one response. In a request-response service, communication flows in both directions. The complete interaction consists of two point-to-point messages—a request and a response. The interaction is only considered complete after the response has arrived.
  • Publication (notification) means an operation sends information on an as-needed basis, potentially multiple times.
  • Subscription means incoming information is processed on an as-needed basis, potentially multiple times.

15.What is vcrepo.dat?

TIBCO Designer creates a file named vcrepo.dat in the project root directory when you first save the project. This file is used to store properties such as display name, TIBCO Rendezvous encoding, and description. This file can be used for identification in place of the project root directory and can be used as the repository locator string (repoUrl).

16.What are the TIBCO BW activities that can participate in transactions?

TIBCO BusinessWorks activities can participate in a transaction. Only the following types of activities have transactional capabilities:

  • JDBC activities
  • JMS activities
  • ActiveEnterprise Adapter activities that use JMS transports
  • EJB activities
  • TIBCO iProcess BusinessWorks Connector activities

17.What are the different types of Transactions TIBCO provides?

TIBCO BusinessWorks offers a variety of types of transactions that can be used in different situations. You can use the type of transaction that suits the needs of your integration project. When you create a transaction group, you must specify the type of transaction. TIBCO BusinessWorks supports the following types of transactions:

  • JDBC
  • Java Transaction API (JTA) UserTransaction
  • XA Transaction

18.What activities are supported in JTA Transaction?

The Java Transaction API (JTA) UserTransaction type allows

  • JDBC
  • JMS
  • ActiveEnterprise Adapter (using JMS transports)
  • EJB activities
  • 19.What is the purpose of the inspector activity ?

    The Inspector activity is used to write the output of any or all activities and process variables to a file and/or stdout. This is particularly useful when debugging process definitions and you wish to see the entire schema instead of mapping specific elements to the Write File activity.

    20.What are the maximum/minimum of threads available for incoming HTTP ?

    The maximum/minimum of threads available for incoming HTTP : 75/10

    « Previous | 0 | 1 | 2 | 3 | 4 | Next »

    copyright © 2014 - all rights riserved by