To run and use Scheer PAS Process Mining you need a database to store the collected statistical and tracing data. Process Mining can be connected to a MySQL, an Oracle, or an SQLServer database. To set up the analytic database, you need a valid installation of one of these three.
When preparing the database installation, please consider the following: The Process Mining database contains analytic data for statistical analysis and can reach a considerable size. But, in contrast to databases that store application data, it does not need to be highly available and fulfill strict recovery requirements.
This may lead to the fact that a point in time recovery is not possible, but this will not cause problems as lost data can be simply reloaded from the BRIDGE logs. |
The analytical database is composed of two parts:
To use a MySQL database, you need to
SELECT
privileges on table mysql.proc.
GRANT SELECT ON 'mysql'.'proc' TO '<user>'@'<mysql server>'; |
|
All tables and procedures will be created by the analytics-etl-service at startup.
To use an SQLServer database, you only need to create an empty schema. All tables and procedures will be created by the analytics-etl-service at startup.
To use an Oracle database, you need to create an empty schema. All tables and procedures will be created by the analytics-etl-service at startup.
The Oracle database user need to be granted the following minimum privileges for Process Mining to work:
GRANT CONNECT, RESOURCE TO <database user the process mining services will use> CONTAINER=CURRENT; |
For both setup scenarios the database administrator needs to grant access to package sys.dbms_crypto to the Process Mining database user:
GRANT EXECUTE ON SYS.DBMS_CRYPTO TO <database user the process mining services will use>; |