# Loading data using DataBridgeAgent

> :::note
**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.
:::
:::important
Using a proxy server is not supported for loading data using **DataBridgeAgent**.
:::
:::important
Always make sure that the data is in the required input format for the app template. See [App Templates](https://docs.uipath.com/process-mining/automation-suite/2024.10/user-guide/app-templates#app-templates). This can be done either in the Data transformations, or by renaming the output fields of the on-premises stand-alone connector (.mvp).
:::

:::note
**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.
:::
:::important
Using a proxy server is not supported for loading data using **DataBridgeAgent**.
:::
:::important
Always make sure that the data is in the required input format for the app template. See [App Templates](https://docs.uipath.com/process-mining/automation-suite/2024.10/user-guide/app-templates#app-templates). This can be done either in the Data transformations, or by renaming the output fields of the on-premises stand-alone connector (.mvp).
:::

## Introduction

Similar to extracting data and preparing a dataset for use in a on-premises (stand-alone) **Discovery Accelerator**, you must extract data from the source system and create a dataset for use in **Process Mining**. This page describes how you can extract data from your source system for use in **Process Mining** using **DataBridgeAgent**.

**DataBridgeAgent** is used to extract data from the source system, and exports `.tsv` files. These `.tsv` files are loaded into the Microsoft SQL Server database using CData Sync. The following illustration shows an overview of the data flow.

![Data flow for loading data using CData Sync](https://dev-assets.cms.uipath.com/assets/images/process-mining/process-mining-data-flow-for-loading-data-using-cdata-sync-19563-abe9545e-a3baddb5.webp)

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

### Using .mvp Connectors

In **Process Mining** (Automation Suite), an existing **Process Mining** on-premises (standalone) connector (`.mvp` file) can be loaded using **DataBridgeAgent**. This enables you to reuse the existing Data transformations, and load the output data into a process app in **Process Mining** Automation Suite.

See [Adding a custom connector to DataBridgeAgent](https://docs.uipath.com/process-mining/automation-suite/2024.10/user-guide/adding-a-custom-connector-to-databridgeagent#adding-a-custom-connector-to-databridgeagent) for a detailed description on how to add a `.mvp` connector file created in **Process Mining** on-premises (standalone) to **DataBridgeAgent**.

### Downloading DataBridgeAgent

Use the following link to download DataBridgeAgent: https://download.uipath.com/ProcessMining/versions/21.10.4/DataBridgeAgent/DataBridgeAgent-21.10.4.zip

:::note
You can only use `.mvp` connectors of a **Process Mining** on-premises standalone version that is the same version as the DataBridgeAgent. (v2021.10.4).
:::

**DataBridgeAgent** is a standalone tool. It is recommended to create a separate folder on the server to use **DataBridgeAgent**.
:::note
Make sure to install **DataBridgeAgent** in a folder on the `C:\` drive. Since **DataBridgeAgent** contains connectors that have rather long names, file paths can become very large, which may cause issues when running the `datarun.bat` file to create the dataset. Do **not** install **DataBridgeAgent** in the in the Process Mining installation folder (`PLATFORMDIR`). Also, do **not** install **DataBridgeAgent** in the **Downloads** folder.
:::

## DataBridgeAgent

**DataBridgeAgent** is a standalone package that can be used to extract data from your source system to the blob storage for use in **Process Mining Automation Suite**. It contains the **Process Mining** on-premises (stand-alone) build and the on-premises `.mvp` connector used to prepare the dataset. Currently, the following on-premises `.mvp` connectors are included in **DataBridgeAgent**:
* **SAP Connector for Purchase-to-Pay Discovery Accelerator**; See [Using DataBridgeAgent with SAP Connector for Purchase-to-Pay Discovery Accelerator](https://docs.uipath.com/process-mining/automation-suite/2024.10/user-guide/using-databridgeagent-with-sap-connector-for-purchase-to-pay-discovery-accelerator#using-databridgeagent-with-sap-connector-for-purchase-to-pay-discovery-accelerator).
* **SAP Connector for Order-to-Cash Discovery Accelerator**; See [Using DataBridgeAgent with SAP Connector for Order-to-Cash Discovery Accelerator](https://docs.uipath.com/process-mining/automation-suite/2024.10/user-guide/using-databridgeagent-with-sap-connector-for-order-to-cash-discovery-accelerator#using-databridgeagent-with-sap-connector-for-order-to-cash-discovery-accelerator).

If you want to use your own custom `.mvp` connector, you can add it to **DataBridgeAgent**. In this case, you need to configure **DataBrigdeAgent** for use with your connector. See [Adding a custom connector to DataBridgeAgent](https://docs.uipath.com/process-mining/automation-suite/2024.10/user-guide/adding-a-custom-connector-to-databridgeagent#adding-a-custom-connector-to-databridgeagent).

:::important
**DataBridgeAgent** automatically converts input field names to lowercase and special characters to underscores. If you use **DataBridgeAgent** to load data, make sure to edit the transformations of your process app and set **all** input fields to lowercase. For example: {{ pm_utils.to_varchar('Cases_base_raw."Case_ID"') }} as "Case_ID", must be changed to {{ pm_utils.to_varchar('Cases_base_raw."case_id"') }} as "Case_ID",.
:::

### Difference from an on-premise installation

**DataBridgeAgent** is different from an on-premise (stand-alone) installation since it:
* is a command-line tool, and therefore does not have a user interface;
* does not require a separate license;
* does not require IIS.
  :::note
  The **DataBridgeAgent** already includes the connectors. You do not need to download and deploy the connector itself.
  :::

## Prerequisites

See [System requirements](https://docs.uipath.com/process-mining/automation-suite/2024.10/user-guide/system-requirements-dba#system-requirements).

### Setup credentials for the SQL Server database

Uploading data to **Process Mining** (Automation Suite) requires access to the SQL Server database location to which the extracted data needs to be uploaded. To set up a SQL Server destination connection you need the following setup parameters to authenticate access to the SQL Server database location.

* `Server`
* `Database`
* `Schema`
* `Role`

See [Retrieving the SQL Server database parameters](https://docs.uipath.com/process-mining/automation-suite/2024.10/user-guide/retrieving-the-sql-server-database-parameters#retrieving-the-sql-server-database-parameters)

### Extracting data from an SAP source system

If you want to use data directly from your SAP system in Process Mining Automation Suite you must set up the SAP extraction before you can use **DataBridgeAgent**. See [Set up Native SAP Extraction](https://docs.uipath.com/process-mining/standalone/2021.10/user-guide/set-up-native-sap-extraction) for a detailed description.

### Extracting data via loading .csv files

If you want to use data loaded from `.csv` files always make sure that:

* a separate `.csv` file is available for each table.
* the file names of the `.csv` files are the same as the names of the input tables of the connector.
* all the fields used in **Process Mining** are present in the `.csv`file.
* the fields in the `.csv` files have the same names as the field names used in **Process Mining** column.

The CSV settings can be defined in the [CSV parameters](https://docs.uipath.com/process-mining/automation-suite/2024.10/user-guide/loading-data-using-databridgeagent#loading-data-using-databridgeagent) of the DataBridgeAgent.

### Extracting data via an ODBC connection

If you want to use data from an external data source via an ODBC connection, make sure that the required ODBC driver is installed on the server.

:::note
All databases that have a 64-bit version can be accessed using an ODBC connection. The required 64-bit ODBC driver must be installed on the **Process Mining** server, and the server must be able to access that specific system.
:::

### Using a Credential store

A Credential store allows you to use passwords without showing the actual password. See [Set up a Credential Store](https://docs.uipath.com/process-mining/standalone/2021.10/user-guide/set-up-a-credential-store) for a detailed description.

By default, an encrypted credential store is used. See [Setting up an encrypted file-based credential store](https://docs.uipath.com/process-mining/standalone/2021.10/user-guide/set-up-a-credential-store#Setting%20up%20an%20Encrypted%20File-based%20Credential%20Store) for more information.

:::note
To change the Server Settings you edit the `&lt;EXTRACTORDIR&gt;\databases\ServerSettings.json` file.
:::
