# Configuring the extraction script

> Follow these steps to configure the extraction script.

Follow these steps to configure the extraction script.

1. Go to the [App Templates](https://docs.uipath.com/process-mining/automation-cloud/latest/user-guide/app-templates#app-templates) page and open the documentation page for your app template.
2. Locate the section **Loading data using Theobald Xtract Universal** and download the `extract_theobald.zip` file for your app template. This `extract_theobald.zip` file contains the `extract_theobald.ps1` script and the `config.json` file.
3. Unzip the content of the `extract_theobald.zip` file on the server where Theobald Xtract Universal is installed.
4. Configure the variables for the script in the `config.json` as listed in the following table.

 <colgroup>
  <col/>
  <col/>
 </colgroup>
 
  
     Variable  
     Description  
  
 
 
  
    <code>xu_location</code> 
    The Xtract Universal installation folder. This is the folder where you can find the <code>xu.exe</code> . For example: C:\\MyFolder. 
  
  
    <code>xu_server</code> 
    Address of the server where Xtract Universal is installed. The default is <code>localhost</code> . 
  
  
    <code>xu_port</code> 
    Port of the server where Xtract Universal is installed. The default port of an installation is <code>8065</code> . 
  
  
    <code>sas_uri</code> 
     The SAS uri of the Azure blob storage to which the extracted data needs to be uploaded. Refer to  Retrieving the credentials for the Azure blob storage  .  
  
  
    <code>end_of_upload_api</code> 
    The API that is called to start data processing in Process Mining, once all data has been uploaded.  Refer to  Retrieving the credentials for the Azure blob storage  .  
  
  
    <code>extraction_start_date</code><sup> * </sup> 
    Start date to be used to limit extractions. Only tables where a date filter is applied are filtered on this date. Format is <code>YYYYMMDD</code> . The default is no limitation indicated by the start date <code>19700101</code> . Note:
      
         <code>extraction_start_date</code> must have a value. 
         all events that happened before <code>extraction_start_date</code> &nbsp; will&nbsp; be excluded from the extracted data. 
      

  
  
    <code>extraction_end_date</code><sup> * </sup> 
    End date to be used to limit extractions. Only tables where a date filter is applied are filtered on this date. Format is <code>YYYYMMDD</code> . The default is no limitation indicated by the end date <code>20991231</code> . Note:
      
         <code>extraction_end_date</code> must have a value. 
         all events that happened after <code>extraction_end_date</code> &nbsp; will&nbsp; be excluded from the extracted data. 
      

  
  
    <code>language</code> 
    The language in which data is extracted from the source system. The default is <code>E</code> . 
  
  
    <code>exchange_rate_type</code> 
    The exchange rate type that is used for currency conversion. The default is <code>M</code> . 
  
  
    <code>is_sap_hana</code> 
    Specifies if the source system is SAP HANA. Other versions of SAP might give errors in the extraction because of clustered tables. The default value is <code>true</code> . 
  
  
    <code>extraction_type</code> 
     Defines the extraction type used for the extraction. Possible values: full , incremental .  Check out  Incremental extraction  for more information on how to configure incremental extraction for Theobald Xtract Universal.  
  
  
    <code>extraction_tables_incremental</code> 
     Enables you to specify the tables used for incremental extraction. 
      
         This setting is only applicable when extraction_type is set to incremental . 
         By default, all transactional tables are defined. 
      
Important: Make sure to configure incremental extraction for the (transactional) tables in Xtract Universal Designer and in the input data mapping in Process Mining. Check out  Incremental extraction  for more information. 
  
 

*) To achieve a more complete overview of all events, it is recommended to set `extraction_start_date` and `extraction_end_date` so that the interval exceeds twice the known throughput time of the business process.