Configure Engine Execution Properties

The Engine Execution properties affect engine startup, memory allocation, thread processing, and timeouts.

To configure Engine Execution properties:

 
Start automatically during Process Administrator initialization When selected, the engine automatically starts when the Process Administrator application is initialized.
Additional arguments used in startup Specifies arguments to be passed to the engine during startup, which can include:
  • -c (rebuilds instance counters in WorkSpace, in case they become corrupted)
  • -p (rebuilds instance counters for a specified process)
  • -t (a delay, in seconds, that occurs before the engine shuts down)
Additional java arguments used in startup Specifies arguments to be passed to the JVM during startup, which can include:
  • -c (rebuilds instance counters in WorkSpace, in case they become corrupted)
  • -p (rebuilds instance counters for a specified process)
  • -t (a delay, in seconds, that occurs before the engine shuts down)
Maximum JVM Heap Size The maximum amount of memory the engine can use. If the engine reaches this limit it will shut down and restart with memory cleared. Available engine memory is determined by the number of processes deployed, how much memory each process uses, and the size of the Instances and Participants Cache.
Maximum Instance Size The maximum amount of memory an instance can occupy. The variables contained in an instance primarily determine how much memory it requires. Notes and attachments added to instances in WorkSpace do not affect its size.
Participant Cache The maximum size of the cache for storing participant data.
Instances Cache The maximum number of recently accessed instances to be stored in a cache for the engine. Larger caches require more memory. Smaller caches may cause instances to be retrieved from the engine database more frequently (thereby slowing performance).
Maximum number of execution threads used for interactive executions The maximum number of threads the engine will use for interactive executions. This value may need to be changed from the default if there are a large number connected users and interactive executions that must be processed.
Maximum number of execution threads used for automatic tasks The maximum number of threads the engine will use for automatic tasks (those requiring no user interaction). If the number of automatic tasks exceeds this value, the tasks are placed in a queue until a thread becomes available. This value should be lower than the maximum number connections allowed by the database.
Priority of Automatic Execution Threads Sets the priority of the threads for automatic tasks. When processing a large amount of automated tasks, this value should be increased. However, setting this value too high could adversely affect performance, or even cause some external connections to be unattended.
Automatic Items Queue Size Determines the number of automatic tasks in the queue for the engine. Larger queues require more engine memory but require less database access.
Retry Times The number of times the engine will retry automatic tasks that have timed out (after the Retry Interval has elapsed), after which the instance is sent to an exception handler.
Retry Interval The length of time, in seconds, that will elapse before an automatic task is retried.
Persist instance data  
Maximum BP-Methods Timeout The length of time, in seconds, that will elapse before a BP-Method times out.
Interactive Component Timeout The length of time, in minutes, that will elapse before an interactive component times out. Shorter times allow resources to be freed sooner when interactive components are left unattended.
Maximum Process Web Service Session Timeout The length of time, in seconds, that will elapse before an inactive Web Service session times out.
Trace Components When selected, enables transmission of FBL data to the Engine log. Enabling this option will slow engine performance.