Files

Classic Manager supports the upload and download of various file types. Files are treated as assets in Manager, and pipelines can read from and write to these files. This feature is known as sldb, and it is available in certain Snaps, such as File Reader and File Writer, primarily for development testing.

However, do not use the Manager Files feature as a file system or for storage purposes. For production data storage, use a Cloud storage provider. File Assets should not serve as the source or destination in production pipelines. When configuring File Reader and Writer Snaps, set the file path to a cloud provider or an external file system

Note:

Supported use cases for reading from and writing to sldb:

JAR files
JDBC files
Expressions libraries (.expr)
Account-relatedconfiguration files

Pipelines can reference these types of files when processing data. Otherwise, do not use sldb to store data.

During pipeline development, you can use Manager > Files to store static JAR files, expression library files, JDBC drivers, and parameter files for SnapLogic to use during pipeline development.

For example, you might upload .xls, txt, .json or .csv files to design a pipeline that executes on files stored in an S3 bucket during production.

The maximum file size is 100MB. You can upload them using Snaps that support file upload or in the Classic Manager, as described on this page. To reference an uploaded file in a pipeline's field, use the following convention: sldb:///<YOUR_FILE_PATH>.

Limitations

File Assets are intended only for specialized files that a Pipeline uses to reference certain data, such as accounts, expressions, or JAR files. Because the platform does not restrict how files are used, admins should audit File uploads in their Orgs through the Activity Log.

File Assets have the following limitations:

The maximum file size is 100MB.
Projects should not contain more than 100,000 total Assets. File Assets count towards that total.
The following table lists files types that are not supported and describes why:


HTML-associated files can contain cookie-stealing JavaScript and web bugs:	PHP scripts might execute arbitrary code on the server:	Other types that might be interpreted by some servers:	Window executable files that can cause harm:
HTML HTM JSB MHTML MHT XHTML XHT	PHP PHTML PHP3, PHP4, PHP5 PHPS	SHTML JHTML PL CGI DMG	EXE SCR DLL MSI VBS BAT COM PIF CMD VSD CPL VXD APP