TIBCO iProcess Interview Question and Answers

Que: What is Business Process Management (BPM)?

Ans: Business Process Management is simply the management of your business processes. It is a simple yet a powerful concept that helps you increase the efficiency of your business processes. It is a combination of processes and technology. It improves the execution and monitoring of processes.

Que: What is CDQP?

Ans: Case Data Queue Parameters allow values from work item case data to be used to sort,defined(globally), and can then be mapped to specific queues for use in Work Queue Manager.

Que: How to do exception handling in Iprocess for EAI steps?

Ans: We can achieve exception handling Using the SW_QRETRYCOUNT , Please see the below explanation

Using the SW_QRETRYCOUNT system field to provide exception Handling for Transaction

with Failing EAI Steps .

The SW_QRETRYCOUNT System field returns the number of times that a message in a message queue has failed.

The field value is 0 the first time a message is processed and is incremented each time the message fails.

For Example , If a BG process is processing a message and SW_QRETRYCOUNT=2, this

means that the BG is attempting to process the message for the third time.

Que: What is maximum number of EAI steps allowed in a process?

Ans: No Limit

                                 

Que: Where is it possible to change the priority of a workitem while it is in a work queue?

Ans: SW_IP_xxx system field values

Que: What is the recommended step to use to start up a parallel branch of a case as a result of some external trigger?

Ans: Event

Que: What happens when an Event is used to interrupt a case and the Event step is NOT linked to any other steps?

Ans: Case data changes will be imported, but the case will NOT be moved along the process.

Case data changes will be imported, and the audit trail will be updated to record the Event trigger.

Que: What is short lock and long lock in tibco iProcess?

Ans: Short lock. This is the standard lock normally set by the TIBCO iProcess Workspace. A short lock is removed when a user keeps or releases a work item. In the event that short locks are left behind because, for example, the iProcess Workspace crashed, the only way to remove the short lock is to re-start the iProcess Engine or use the following command.

Long lock. A lock that is persistent and can only be removed using sal_llock_frm_init() by the user holding the lock. Long locks are not normally used by TIBCO iProcess Workspace, but may be set by SAL SDK programs or the TIBCO iProcess Objects Client. Re-starting the iProcess Engine has no effect on long locks, so a work item locked in this way remains inaccessible to every iProcess user until it is manually unlocked.

Que: What is the difference between iProcess Server Objects and iProcess Objects server?

Ans: Client applications make use of the objects in the TIBCO iProcess Server Objects by making method calls that either retrieve or modify data. These method calls cause messages to be sent to a TIBCO iProcess Objects Server. The TIBCO iProcess Objects Server acts as a gateway between the client applications created with TIBCO iProcess Server Objects, and the TIBCO iProcess Engine, where the actual processing and storage of data occurs. The TIBCO iProcess Engine manages all data, routing work items and updating the appropriate work queues.

Server Objects communicate with the TIBCO iProcess Objects Server via TCP/IP .Objects Server communicate with the TIBCO iProcess Engine via UDP

Que: Where can you see the description of the error when a Case is terminated abnormally?

Ans: Check the SWDIR\logs\sw_warn or sw_error log files to see if any error messages were logged.