Uploading data

Introduction

Note: Always make sure that the data is in the required format for the app template that used for the process app. See App Templates.

When you create a new process app, you must upload data before you can publish the process app. You can also upload data for a published process app. In this case, the app will be published with new data.

Follow these steps to load data for a published app.

1. Open the Process Mining Portal.
2. Go to the Process apps tab and locate the app for which you want to upload data.
3. Click in the Actions column of the process app for which you want to ingest data and select Upload data.

You can use a sample dataset, upload a dataset with .tsv or .csv files, or load data using an extractor. See Selecting the Data Source.

Important:

When uploading data using the Upload data option, make sure the.csv or .tsv files have the suffix _raw.

Loading Data Using an Extractor

The default extraction tool is CData Sync and it is recommended for any non-SAP source systems such as Oracle. For SAP, the recommended extraction tool is Theobald Xtract Universal.

Important:

When loading data using an extractor, note that tables that are uploaded once are not cleared when re-ingesting data. If you want to clear a previously uploaded table, then re-upload a dataset with that table having 0 records.

CData Sync

If you want to load data from your source system directly into a process app in Process Mining, you can use CData Sync. CData Sync supports various source systems to which it can connect for data extraction for example files, databases, APIs, and so on.

See Loading data using CData Sync.

Theobald Xtract Universal

For SAP source systems, the recommended tool is Theobald Xtract Universal. Theobald Xtract Universal provides fast data access and extractions to SAP ECC and SAP HANA data sources. See Loading data using Theobald Xtract Universal.

DataBridgeAgent

Important:

DataBridgeAgent is only needed if you are migrating from an on-premises stand-alone Process Mining version.

Only use DataBridgeAgent if you have a custom .mvp connector. Otherwise, use CData Sync, Theobald Xtract Universal for SAP, or files to upload data.

If you have a custom .mvp connector you can use the Process Mining on-premises (stand-alone) extractor DataBridgeAgent to load data for a process app in Process Mining. See Loading Data Using DataBridgeAgent.

Viewing Ingestion Logs

When you upload data and the data ingestion failed, an ingestion log is created. You can click on the View log icon to see more details on the ingestion errors. See the illustration below.

Below is an example of an ingestion log.

No logs available

It can happen that there are no log files available after a failed datarun. For example, when you have accidentally started a new datarun that failed because the previous datarun was not finished. In this case, you should not start a new data run, and wait for the first run to be completed. When the run is finished, the log messages of the first run will show, and the corresponding run status (run failed/run successful) is displayed.