Skip to main content Skip to complementary content

Configuring a remote harvesting server using the configuration files

Before you begin

You have downloaded and decompressed the or TDC-x.y-YYYYMMDD.tbz2 file on your machine.


  1. In the software home directory, open the <TDC_HOME>\TalendDataCatalog\conf\ configuration file.
  2. Configure the following parameters:
    Parameter name Description
    M_BROWSE_PATH Type in the local and mapped network drives that will be available in the Talend Data Catalog user interface during the metadata harvesting.

    You should limit the access to a common shared data location and avoid the system area.

    The server must have access to the metadata harvesting files and directories anytime another event is to occur such as a scheduled harvest. When harvesting a model, the user interface presents a set of paths that can be browsed to select these files and directories.

    For Windows based application servers, when running as a service, you should specify the physical drives by letters and the complete network paths, for example M_BROWSE_PATH=C:\, E:\, \\network-drive\shared\.

    The mapped drive names and paths cannot be the same as what a user sees when logged in. It is not sufficient to enter the mapped drive ID such as N:\, as that drive mapping is generally not available to services. It also applies to script backup and restore drives.

    M_DATA_DIRECTORY Optionally, enter a new location to relocate the data files such as the log files and the metadata incremental harvesting cache, if needed for very large Data Integration or Business Intelligence tools.

    By default, the data directory is located in the data subdirectory of the application server home directory. It is recommended to separate the program data from the program files. It allows you to provide a new location for the data in a separate area.

    M_JAVA_OPTIONS Optionally, enter a new default maximum to increase the maximum memory used by Java bridges during the metadata harvesting of large databases, Data Modeling, Data Integration or Business Intelligence tools.

    This parameter defines the default maximum for all Java bridges. Most memory-intensive Java bridges such as JDBC bridges have the ability to define their own maximum memory in the Miscellaneous parameter.

  3. If the remote harvesting server is connected to a Talend Data Catalog server installed on the cloud, open the <TDC_HOME>\TalendDataCatalog\conf\ configuration file to perform additional customizations.
  4. Configure the following parameters:
    Parameter name Description
    M_SERVER_URL Enter the URL of the Talend Data Catalog server installed on the cloud.
    M_AGENT_NAME Type in a shared secret set to anything as long it is unique, reasonably descriptive so it can usefully be identified in the UI, hard to guess since it also works as a shared secret string.

    You will use this shared secret when adding the remote harvesting server in the Talend Data Catalog UI.

  5. Save your changes.


You are ready to add the remote harvesting server in Talend Data Catalog.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!