ProM Import Framework 3.1 review

ProM Import Framework project allows you to extract process enactment event logs from a set of information systems. These can be e

License: GPL (GNU General Public License) File size: 0K Developer: Christian W. Guenther

0

ProM Import Framework project allows you to extract process enactment event logs from a set of information systems.

These can be exported in the MXML format, which is the standard event log data format for Process Mining analysis techniques.

Process Mining is a family of a-posteriori analysis techniques to extract abstract information from process enactment logs. More in-depth information about the are of process mining is available at processmining.org.

Installation:

- Decompress and extract the provided *.tar.gz archive.
- This will create a folder 'ProMimport', containing all files necessary.
- Start the application by running the provided shell script 'start.sh'.
- The import filter plugins delivered with your installation package are located in the 'Plugins' folder inside the 'ProMimport' directory.
- Load the plugins (which are packaged in *.jar files) that you want to use from within the running app. For that, use 'Load filter plugin..' from the 'Filters' menu.
- 3rd party plugins, or plugins developed by you, can be added to the application in exactly the same manner.
- Once imported, filters are automatically added to the application's filter cache, and zre re-loaded on every successive startup. Further, all filter and application configuration data is transparently made persistent by the application.
- Thus, after importing all filter plugins necessary, you can safely delete the 'Plugins' folder.

What's New in This Release:
This is the initial release of the ProM framework under the new open source CPL license.
Installers / disk images are provided for Windows and Mac OS X, while the provided source archive is also executable on all platforms supporting Java 5.0.
Notice that this release depends on a Java runtime environment of version 1.5 / 5.0 or later.
Prior JRE releases may yield unexpected errors.