Tibco Interview Questions and Answers

by Nithyanandham, on Sep 11, 2022 1:43:18 PM

Q1. What is the meaning of Tibco?

Ans: TIBCO (The Information Bus Company) Software Inc. is an American company that provides integration, analytics and event-processing software for companies to use on-premises or as part of cloud computing environments. The software manages information, decisions, processes and applications for over 10,000 customers.

Q2. What are the modes of TIBCO BW Installations ?

Ans:
• GUI mode
• Console mode
• Silent mode

Q3. If you have installed a particular version of TIBCO software e.g. TIBCO BW X.Y.Z, What are X, Y and Z number stands for?

Ans: Integration can be at different application layers:
• X:Patch
• Y:Major
• Z:Minor

Q4. What are the different modes of service invocation?

Ans: 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.

Q5. What are the different modes of service invocation?

Q6. What is vcrepo.dat?

Ans: 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).

Q7. Explain the process configuration parameters – Max Jobs, Flow Limit & Activation Limit ?

Ans: • Max Jobs :
Max Jobs specifies the number of process instances that are kept in memmory. Once this limit is reached newly created process instances (subject to flow limit) are paged out to disk.0 specifies no limit and is the default.
• Flow Limit :
Flow Limit specifies the maximum number of running process instances that are spawned before the process starter is suspended ie it enters a FLOW_CONTROLLED state and does not accept new events. This can be used to control the number of process instances running simultaneously and when the protocol generating the event can store the event till it is received, like email servers, JMS, RV etc. 0 specifies no limit and is the default.
• Activation Limit :
Activation limit flag specifies that once a process instance is loaded it must be placed in memory till it completes execution. By default it is enabled.

Q8. What are the options for configuring storage for process engine’s checkpoint repository ?

Ans: The options for configuring storage for process engine’s checkpoint repository are:
• Local File
• Database. Fault tolerant engines can recover from a checkpoint only when database is used.

Q9. Process engines in a fault tolerant group can be configured as peers or master secondary.How do these differ ?

Ans: The options for configuring storage for process engine’s checkpoint repository are:
• – Peer means all of them have the same weight. In this case when one engine fails another one takes over and continues processing till it fails.
• – In master secondary configuration weights are unequal, the secondary starts processing when master fails. But when master recovers, secondary stops and master continues processing.

Q10. What are the uses of grouping activities ?

Ans: Uses of grouping activities are:
• Create a set of activities having a common error transition.
• Repeat group of activities based on a condition.
1. – Iterate over a list.
2. – Repeat until condition true.
3. – Repeat on Error until condition true.
• Group activities into a transaction.
• To create a critical section area that synchronizes process instances.
• A ‘Pick First Group’ allows you to wait for the occurrence of multiple events and proceed along a path following the first event to occur.

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

Ans: 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 processs definition inside one engine, just specify the scope as ‘Single’.

Q12. How to control the sequence of execution of process instances created by a process starter ?

Ans: Use the sequencing key field in the Misc tab of any process starter. Process instances with the same value for this field are executed in the sequence in which they are started.

Q13. Can there be two error transitions out of an activity ?

Ans: No. There can be only one Error and one Success if no matching condition transition out of each activity.

Q14. What activities are supported in JTA Transaction?

Ans: The Java Transaction API (JTA) UserTransaction type allows:
• JDBC
• JMS
• ActiveEnterprise Adapter (using JMS transports)
• EJB activities
to participate in transactions.

Q15. What activities are supported in XA Transaction ?

Ans: The XA Transaction type allows:
• JDBC activities
• ActiveEnterprise Adapter activities that use the JMS transport
• JMS activities
to participate in transactions.
Note:For JMS activities and ActiveEnterprise Adapter activities, request/reply operations cannot participate in an XA transaction. Also, EJB activities cannot participate in an XA Transaction group.

Q16. What are the options for configuring storage for process engine’s checkpoint repository ?

Q17. Process engines in a fault tolerant group can be configured as peers or master secondary.How do these differ ?
Ans: The options for configuring storage for process engine’s checkpoint repository are:
• – Peer means all of them have the same weight. In this case when one engine fails another one takes over and continues processing till it fails.
• – In master secondary configuration weights are unequal, the secondary starts processing when master fails. But when master recovers, secondary stops and master continues processing.

Q18. How do wait-notify resources work ?

Ans: Basically wait and notify should share a common notification configuration which is just a schema definition for data that will be passed from notifier to waiter. Specific instances of waiter & notifier are corrrelated via a key.
For example: when one process is in wait state for key ‘Order-1’, it waits till another process issues a notification with the same key value.

Q19. What is the default Axis in XPath ?

Ans: Child axis- What this means is that when you select “BOOK” from the current context, it selects a child node with that name, not a sibling with that name. Other axes are parent , self , sibling etc.

Q20. What are the output formats for XSLT?

Ans:
• XML
• HTML
• Text

Q21. What is the Purpose of $_error variable ?

Ans: $_error variable is available in the node following the error transition. It captures the error message, error code etc.

Q22. What are the cases where business process cant proceed correctly subsequent to restart from a checkpoint ?

Ans: Sending HTTP response, confirming an email/jms message etc. This is because the confirmation or sending HTTP response has to done in the same session. When engine crashes these sessions are closed at their socket level. In such cases send response/confirm before checkpoint.

Q23. Which group do you use to wait for multiple events and proceed with the first to occur ?

Ans: A ‘Pick First Group’.