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.
The analytical database is composed of two parts:
- The first part contains stored procedures and working tables used during the collection of data.
- The second part contains the front-end tables which are queried by the Process Mining services to present the data in a user interface.
Setting up a MySQL Database
To use a MySQL database, you need to
- create an empty schema.
- grant the Process Mining user
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.
Setting up an SQLServer Database
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.
Setting up an Oracle Database
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;
Access to sys.dbms_crypto
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>;