Tibco Interview Questions
1.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).
2.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:
* Java Transaction API (JTA) UserTransaction
* XA Transaction
3.What activities are supported in JTA Transaction?
The Java Transaction API (JTA) UserTransaction type allows:
* ActiveEnterprise Adapter (using JMS transports)
* EJB activities
4. 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.
5.How can unauthorized users be prevented from triggering a process ?
Unauthorized users be prevented from triggering a process by giving ‘write’ access for the process engine to only selected users. Only users with ‘write’ access can do activities like deploying applications, starting/stopping process engines etc.
6. How to use legacy .dat file format with latest designer?
Convert .dat file to multi file project using Administration tab while starting up Designer (Other one being Project tab) and then open the multifile project in the normal way.
7.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.
8.Explain the process configuration parameters – Max Jobs, Flow Limit & Activation Limit ?
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 memmory till it completes execution. By default it is enabled.
9.Process engines in a fault tolerant group can be configured as peers or master secondary.How do these differ ?
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.
10.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 processs definition inside one engine, just specify the scope as ‘Single’.
11.Which mechanism can be used to pass data between a process instance and a called sub process other than mapping from/to the callee’s input/output ?
This can be accomplished using job shared variables, unless in the call process activity the ‘Spawn’ flag is enabled in which case the called sub process is a new job and hence gets a fresh copy of the job shared variable initialized as per its configuration. A shared variable can overcome this limitation as it’s scope is not limited to one job.