There are various settings that control how triggers are executed. These are defined in the Triggers > Settings panel in JSCAPE MFT Server Manager.
Limiting number of concurrent triggers
Limiting number of concurrent transfers
Automatically clearing recent trigger history
Figure 139
Limiting number of concurrent triggers
You may wish to limit the number of concurrent triggers that are running in JSCAPE MFT Server. Since each trigger and it's associated actions take up a portion of memory and CPU this is useful in cases where many triggers could be running simultaneously causing your server to be overloaded. To prevent this you can optionally set the maximum number of concurrent triggers. If the maximum number of concurrent triggers is reached then triggers will be placed in a queue for later execution. If the size of the queue is exceeded then an error message will be written to the server activity log.
Limiting number of concurrent transfers
You may wish to limit the number of concurrent file transfer related trigger actions that are running in JSCAPE MFT Server. Since each file transfer related trigger action takes up a portion of bandwidth and disk I/O this is useful in cases where many file transfer triggers could be running simultaneously causing your server to be overloaded. To prevent this you can optionally set the maximum number of concurrent file transfers. If the maximum number of concurrent file transfers is reached then file transfer triggers actions will be placed in a queue for later execution, or depending on the trigger action priority they may interrupt an existing file transfer action and be given execution priority. Interrupted file transfer actions will automatically resume upon completion of higher priority file transfer actions. If the size of the queue is exceeded then an error message will be written to the server activity log.
Automatically clearing trigger history
Over time the history of executed triggers can grow and become quite large, in particular in systems that execute a large number of triggers on a regular basis. You may optionally automatically clear the history of trigger execution using the Clear recent triggers older than N days option. If enabled, the recent trigger history will be cleared of those executed triggers older than the specified value on a scheduled basis. If the value is set to zero (0) days, trigger state information will not be saved in the database.
You may wish to define global event variables that can be used by all of your triggers. Once created these global variables can be accessed from any of your trigger actions using the Add button.