Metadata Harvesting 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 must use either local physical drives or the Universal
Naming Convention (UNC) paths such as
\\RemoteHost\C\Data\Lake.
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.
|
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.
|