Unable to create a PM application using Sample data

News Knowledge Base
1

The application creation process fails due to incorrect configuration in the cluster_config.json related to the Process Mining setup.

Issue Description

The application creation process fails due to incorrect configuration in the cluster_config.json related to the Process Mining setup.

Example of Incorrect cluster_config.json

"processmining": {
"enabled": true,
"app_security_mode": "system_managed",
"warehouse": {
"sql_connection_str": "Server=tcp:xxx.com,1433;Initial Catalog=DB_NAME_PLACEHOLDER;Persist Security Info=False;User Id=creatoruser;Password='pass';MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=True;Connection Timeout=30;Max Pool Size=100;",
"sqlalchemy_pyodbc_sql_connection_str": "mssql+pyodbc://creatoruser:xxx.com:1433/DB_NAME_PLACEHOLDER?driver=ODBC+Driver+17+for+SQL+Server&TrustServerCertificate=YES&Encrypt=YES",
"master_sql_connection_str": "Server=tcp:xxx.com,1433;Initial Catalog=master;Persist Security Info=False;User Id=creatoruser;Password='pass';MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=True;Connection Timeout=30;Max Pool Size=100;"
},
"blob_storage_account_use_presigned_uri": true
},

Root Cause

The cluster_config.json file was not configured properly. Specifically, the placeholder DB_NAME_PLACEHOLDER was not replaced with the actual database name according to the documentation.

Resolution

Ensure that the cluster_config.json file is updated with the correct database name. This is a critical step when configuring Process Mining.

  1. Open the cluster_config.json file.
  2. Replace the placeholder DB_NAME_PLACEHOLDER with the actual database name used for Process Mining.
  3. Check that proper database credentials (username and password) are added. Do not use anonymized credentials such as creatoruser or pass.

Important: The username and password shown in the connection string examples are anonymized and must not be used in production. Do not use creatoruser and pass. Replace them with your actual database credentials.

Final Note

Always adhere to the documentation when configuring or editing files to avoid such errors. Double-check the database details and make sure the configuration matches your environment.