Advanced configuration and integration

The application configuration is stored in the following file:

<PM_HOME>/etc/processmining.conf

When you introduce changes to the processmining.conf file, make sure you do it correctly. For more information, see Configuration file editing guidelines.

Password encryption

You must encrypt the passwords for DB connection or SMTP connection before storing the information in the configuration file.

You can use the crypto-utils command-line tool to encrypt and decrypt passwords, located in <PM_HOME>/crypto-utils:

./crypt-utils.bat myPassword
./crypt-utils.sh myPassword

If the original password includes the $ character, then you must enclose the password in single quotation marks as denoted in the following sample:

./crypt-utils.sh 'test$1'

Horizontal Scaling of long running procedures

Some of the methods, for example Running case detection, Computing replay, and Computing case analysis, started by Process Mining are time-intensive and are currently performed as a single-thread process.

The following table describes the parameters that you can use to improve this process.

Parameter Description Default value
engine.defaults.runningCaseDetectionParallelism Indicates the parameter to set parallelism for the running case detection algorithm. (machine core number)-4
engine.defaults.processReplayParallelism Indicates the parameter that determines the parallelism of the replayLog.
You might not get a better performance when the value is set to more than 4 or 5. Hence for better performance, set the value to 4.
This is applicable only for legacy multilevel processes. There is no impact on flat processes.
2
engine.defaults.caseAnalysisParallelism Indicates the parameter to parallelize the calculation algorithm of the case analysis Max(2, (machine core number) -1)
engine.defaults.defaultParallelism Indicates the parameter to set the value of parallelism for most of the long running executions. For example: log variants extraction for analytics, custom metric filters, and diff analysis. 4
*If the workstation has more than 16 cores, set the value to 6.
engine.defaults.planner.maxWidthPerQuery Indicates the parameter to set the value of parallelism for analytics queries executions. If you encounter performance problems when retrieving analytics widgets, increase this parameter gradually until reaching a maximum of half the maximum number of cores of the workstation. 4