You can transfer files from on-premises and cloud sources that File Ingestion and Replication support to supported targets.
You can add a source to a file ingestion and replication task in the following ways:
Through data catalog discovery
If your organization administrator has configured Enterprise Data Catalog integration properties, you can perform data catalog discovery to find the source object in the catalog. You can discover Amazon S3 V2, Microsoft Azure Blob Storage V3, or Hadoop Files V2 objects to use as sources in new file ingestion and replication tasks.
Search for the source object on the Data Catalog page, select the object in the search results, and then add it to a new file ingestion and replication task.
When you configure the task
Select the source connection and source object on the Source tab when you configure the file ingestion and replication task.
File Ingestion and Replication supports the following source types:
•Source Connection— Supports the following sources:
- Local folder
- Advanced FTP V2
- Advanced FTPS V2
- Advanced SFTP V2
- Amazon S3 V2
- Cloud Integration Hub
- Google Cloud Storage V2
- Hadoop Files V2
- Microsoft Azure Blob Storage V3
- Microsoft Azure Data Lake Store Gen2
- Microsoft Azure Data Lake Store V3
- Microsoft Fabric OneLake
- Oracle Cloud Object Storage
•File Listener— Use a file listener component as a source.
To determine the connectors to use for these source types, see Connectors and Connections > File Ingestion and Replication connectors.
A connection fails if "/" is incorrectly provided in the source folder path of connectors while configuring the connection properties.
Use file ingestion and replication tasks to transfer many files of any file type between on-premises and cloud repositories. Create connections and use them in file ingestion and replication tasks. When you create a file ingestion and replication task, you select the source and target connections and specify which files to move from the source to the target.
When you configure the source for a connection, note that the use of slashes around the source folder path differs between connectors. Using slashes incorrectly will result in connection failures.
The following table lists the connectors that you can use in a file ingestion and replication task and the use of slashes around the source folder path for each connector:
Source
Use of Slashes Around Folder Path
Folder Path
Local_Linux
Before and after the folder path
/<folder path>/
For example, /root/user/qa/test/automation/RSFiles
Local_Windows
None
<folder path>
For example, C:\user\qa\test\automation
FTPV2
Before and after the folder path
/<folder path>/
For example, /root/user/qa/test/automation/RSFiles
SFTPV2
Before and after the folder path
/<folder path>/
For example, /root/user/qa/test/automation/RSFiles
FTPSV2
Before and after the folder path
/<folder path>/
For example, /root/user/qa/test/automation/RSFiles
Amazon S3 V2
None
<folder path>
For example, t-shain-mum/user/qa/test/RSFiles
Google Cloud Storage V2
None
<folder path>
For example, mibucketnew/user/files
Microsoft Azure Data Lake storage Gen1
Before the folder path
/<folder path>
For example, /MIQA/Automation
Microsoft Azure Data Lake storage Gen2
Before the folder path
/<folder path>
For example, /B2B/MI
Microsoft Azure Blob Storage V3
None
<folder path>
For example, snowflakemi/MI
Microsoft Fabric OneLake
None
<folder path>
For example, <Lakehouse Name>/<Files>/<<FolderName>>