Tibco-Interview-Questions-page3

46. Explain the process configuration parameters - Max Jobs, Flow Limit & Activation Limit ?

Answer:

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

47. What are the options for configuring storage for process engine's checkpoint repository ?

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

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

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

49. What are the uses of grouping activities ?

Answer: 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 occurence of multiple events and proceed along a path following the first event to occur.

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

Answer: 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'.

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

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

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

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

53. When is a 'No Action' group used ?

Answer: 'No Action' group used to have a set of activities having a common error transition

54. What activity can be used to set the value of a 'User defined process variable' ?

Answer: The 'Assign' activity can be used to set the value of a 'User defined process variable'.

55. Which are the two process variables available to all activities with inputs ?

Answer: 

• $_globalVariables
• $_processContext

« Previous |1 2 3 4 5| Next »

Posted in: