Configuring plugin behavior

Plugins are either executables, Python scripts or PSLang scripts run by the CGI modules or in-process by the Workflow Manager Service (IDWFM).

The PSLang CALL DEPTH setting can be used to troubleshoot problems that occur when running plugins, such as exceptions or performance problems caused by idwfm memory usage increases. It is used to adjust the maximum function call depth for PSLang scripts run in-process. This can help to avoid problems caused by too many, or recursive, function calls. It is located under Manage the system > Workflow > Options > Plugins .

By default, plugin and external interface (exit trap) scripts are run by the built-in Python interpreter if they have a .py extension, or by the PSLang interpreter if they have a .psl extension. You can specify an external interpreter, such as PERL, in the PLUGIN PROGRAM setting in the Manage the system > Workflow > Options > Plugins menu. For example, to specify PERL, type:

.pl c:\perl.exe

This will execute the script (for example, C:\perl.exe <plugin-script>.pl) with no additional arguments. Information will be passed by standard I/O. All plugins scripts must be in the script directory, and exit trap scripts must be in the interface directory.

If you are specifying an external interpreter, ensure that the directory for the interpreter is included in the system path.

Detailed information about users and resources in not included in plugin output by default. This detail is available via API calls. See the Bravura Security Fabric Remote API (api.pdf) manual for details.

You can add more detail to plugin output using the following settings in the Workflow > Options > Plugins :