Tibco Interview Questions

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

Not all 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

2. What are the possible Error output's of Read File activity?

Integration can be at different application layers: FileNotFoundException :Thrown when yhe file does not exist. UnsupportedEncodingException:Thrown when the text file’s encoding is not valid and the content of the file is read into process data. FileIOException :Thrown when an I/O exception occurred when trying to read the file.

3. What are the encodings supported by designer ?

Encodings supported by designer are ISO8859-1(Latin-1) UTF-8

4. What is a TIBCO Domain?

Domain is a collection of hardware and software components that are used for business process integration. The domain defines the TIBCO BusinessWorks environment. Each domain must contain one and only one administration server. Each domain must have a unique domain name. Each domain may contain one or more machines but no single machine can belong to multiple domains. Each machine may have more than one type of software component.

5. What is TIBCO Administrator ?

TIBCO Administrator supports security administration as well as monitoring and management of processes and machines. TIBCO Administrator consists of the TIBCO Administration Server and the web browser based TIBCO Administrator GUI.

6. What is a deployment?

A deployment is a completed configured instance of an integration or project. TIBCO Designer is used to configure projects and deployments in current version. In the future, TIBCO Administrator will be used to manage deployment of projects.

7. What is the purpose of a Lock shared configuration resource?

A Lock is specified for a 'Critical Section' group when the scope is 'Multiple'. It can be used to ensure synchronization across process instances belonging to multiple processs definitions or for process instances across engines(Check multi engine flag for lock in this case and the BW engine needs to be configured with database persistence while deployment). If synchronization is for process instances belonging to the same processes definition inside one engine, just specify the scope as 'Single'.

8. What is the relationship between TIBCO Administrator and TIBCO domains?

A TIBCO Domain is a collection of hardware and software components that are used for business process integration. Domains are created using domain utility provided by TRA. Applications are deployed in a domain using TIBCO administrator. One domain can be administered by only one TIBCO administrator.

9. What are the types of adapter services ?

Types of adapter services are : Subscriber Service Publisher Service Request-Response Service Request-Response Invocation Service

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

IBCO 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-Persistent while TIBCO EMS adds another type of delivery mode which is RELIABLE delivery mode. Also, for restriction of messages acknowledgement, JMS provides NO_ACKNOWLEDGE mode while TIBCO EMS extends the functionality of JMS by providing EXPLICIT_CLIENT_ACKNOWLEDGE mode and EXPLICIT_CLIENT_DUPS_OK_ACKNOWLEDGE mode.

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

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.

12. 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.