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

62.What are the mandatory configuration parameters for FTP Connection & FTP with firewall ?

The mandatory configuration parameters for FTP Connection

• FTP host
• Port
• Username & Password>

63.how to design a process such that depending on number of records updated in a database, 3 different sub-processes may be called ?

Define 3 transitions from JDBC update with condition on the no of updates and call appropriate child processes.

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

65.What are the encodings supported by designer ?

Encodings supported by designer are

• ISO8859-1(Latin-1)
• UTF-8

66.What are the 4 main panels of the Designer window ?

The 4 main panels of the Designer window are

• Project panel
• Palette panel
• Design panel
• Configuration panel

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

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

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.

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

70.What are the uses of grouping activities ?

Uses of grouping activities are:

• Create a set of activities having a common error transition.
• Repeat group of activities based on a condition.

- Iterate over a list.
- Repeat until condition true.
- 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.

71.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'.

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

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.

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

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

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

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

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

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

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

• $_globalVariables
• $_processContext

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

78.What are the three scenarios where BW engine has to be configured with database persistence instead of Local File ?

The three scenarios are:

• Shared Variables across BW engines.
• Locking across groups in multiple BW engines.
• Wait Notify across BW engines.

79.If you want a group to be executed if there is some unhandled error but subject to some max number of iterations which group do you use ?

We can use Repeat on Error until true

80.When is a 'Generate Error' activity useful?

When you handle an error inside a called subprocess or group and want to rethrow the error to the caller(happens by default if you dont handle the error in the called process)