Please enable JavaScript to view this site.

fileTempUpload

Specifies the temporary folder to where “big” files are uploaded before they’re moved to the file repository.

As of Efficy 11, you can store large files – bigger than 32 MB and up to 4 GB – in the Efficy database.

dsgn_large-attachment

Efficy users can interrupt and resume uploads.

dsgn_sidebar-file-transfer

When a download is completed, the file’s CRC is checked before the file is moved to the repository. The folder that holds the file repository is specified with the parameter FileRepository. (The files are stored in subfolders; each subfolder holds up to 1,000 “big” files.)

Preliminary steps: specify Efficy’s file server with the parameter URL (when the Efficy server also functions as file server) or FileURL (when a dedicated file server is used).

Necessary complementary step: specify the root folder where “big” files are stored on Efficy’s file server with the parameter FileRepository.

Next steps: 1. set the minimal file size of files considered as “big” (with the parameter FileMinSize), 2. set their maximum size (with the parameter FileMaxSize) and 3. adapt IIS to the maximum size.

Complementary step: configure the related clean-up service Large File Maintenance.

Efficy services and processes: Large File Maintenance service

dsgn_large-file-maintenance-service

reference information: supported and default values

related parameters (in Servicy): FileMaxSize, FileMinSize, FileRepository, FileURL, URL

© 2006-2020 Efficy All rights reserved