Install MPM |
Scroll Previous Topic Top Next Topic More |
In order to use MEHRWERK ProcessMining, a Qlik Sense® environment is neccessary.
Before installing, it's important to decide which version of Qlik Sense® is best suited. You can find an overview of the different versions and explanations for each installation in the Qlik help.
•By default, all Qlik Sense® versions of the last 12 months are supported
•The deployment on Qlik Sense® Enterprise on Windows is fully supported. Qlik Sense Enterprise SaaS is also supported with some exceptions (e.g. Wizard).
•Apple Safari 10 or later
•Google Chrome (recommended)
•Mozilla Firefox (requires a hardware acceleration, not supported in virtual environments)
The installation bundle can be downloaded in the MPM Support Portal https://portal.mehrwerk.net/. Therefore, login to the support portal, navigate to the section Documents and select "All" as shown in the screenshot below. You can then download the three installation files per release. The following documentation is based on the November 2021 release. Simply add the release-specific information in the corresponding fields.
With the installation bundle, the three ZIP-files TemplateApp.zip, ExtensionBundle.zip and ImportWizard.zip are provided. Their contents are shown in the following list.
The 202203_TemplateApp.zip includes:
oApps
oMPM_Data
oMPM_LangAndMasterItems
oMPM_Scripts
The 202203_ExtensionBundle.zip includes:
oBPMNModeler
oProcessActivityFilter
oProcessAnalyzer
oProcessModeler
oStateToStateButton
oProcessVariantsInspector
oQueryBuilder
oDialog Box
oGrouped Container
oLead Time Filter
oMPM Theme
The 202203_ImportWizard.zip includes:
oBPMNImportWizard
oImportWizard
1.Install MPM
1.Import the MPM EventLogGeneration Apps and the MPM Template App via the Qlik Management Console (QMC).
2.Create the following folder structure in your server with the files received as below (Example based on Installation of November 2021):
•MPM ProcessMining
oNovember2021
oMarch2022
▪MPM_Data
•MPMData.qvd (just a test-file)
▪MPM_LangAndMasterItems
•MasterItems_MPM.csv
•MPM_Translations.csv
oMPM_ScriptFolder
▪202203
▪202111
3.Place the MPM scripts under MPM ProcessMining/MPM_ScriptFolder/ReleaseMonth that is accessible to all MPM users within the organization.
4.Place the files MasterItems_MPM.csv and MPM_Translations.csv under MPM ProcessMining/ReleaseMonth/MPM_LangAndMasterItems that is accessible to all MPM users within the organization.
5.Upload the MPM extensions via the QMC. If the extensions were already uploaded, delete the old ones first before updating. You can import the zipped file at once in one-premise deployments. For Qlik Sense Enterprise SaaS, please unzip the folder, create one zip per extension and upload each zip on its own.
2.Test run the MPM Template App
1.Go to the Hub and open the imported MPM Template App.
2.Create a MPM data connection:
a)Go to the data load editor and click on the "create new connection" button on the right hand side.
b)Search for the "MPM ProcessMining/March2022" folder and select MPM_Data.
c)Name the connection (if possible) MPM_Data.
d)Go to the QMC (if possible) and change the connection name by deleting the user-id from the connection name.
e)Give the required users access rights to this data connection.
3.Create a MPM script connection:
a)Go to the data load editor and click on the "create new connection" button on the right hand side.
b)Search for the "MPM_ScriptFolder" folder within “MPM ProcessMining” and select MPM_ScriptFolder.
c)Name the connection (if possible) MPM_ScriptFolder.
d)Go the QMC (if possible) and change the connection name by deleting the user-id from the connection name.
e)Give the required users access rights to this data connection.
4.Create a MPM_LangAndMasterItems connection:
a)Go to the data load editor and click on the "create new connection" button on the right hand side.
b)Search for the "MPM_LangAndMasterItems" folder within “MPM ProcessMining” and select MPM_LangAndMasterItems.
c)Name the connection (if possible) MPM_LangAndMasterItems.
d)Go the QMC (if possible) and change the connection name by deleting the user-id from the connection name.
e)Give the required users access rights to this data connection.