topic Re: File Transfer Receiver in Alfresco Archive

File Transfer Receiver

aussen2 — Tue, 04 Oct 2011 09:25:15 GMT

I want to give the new File Transfer Receiver a try but cannot find much information about it. Not sure if this question belongs in this forum but my understanding is that this feature grew out of a WQS requirement anyway. I already read through the section "Configuring the File System Transfer Rece

Re: File Transfer Receiver

bremmington — Tue, 04 Oct 2011 09:35:25 GMT

The file transfer receiver (FTR) is not related to WQS at all. WQS requires an Alfresco repository on the delivery tier. The FTR is more useful if you are not using WQS, or if you want to push some static content to a web server to supplement a WQS website.

Re: File Transfer Receiver

aussen2 — Tue, 04 Oct 2011 09:44:06 GMT

Thanks for the quick response. It already clarifies a lot. 😉 But wasn't there supposed to be some mechanism for exporting a WQS site to a file system in Alfresco Community 4.0? Is this still something for the future or did I get this completely wrong at all?

Re: File Transfer Receiver

bremmington — Tue, 04 Oct 2011 10:01:34 GMT

I think that was a misunderstanding. WQS is an example of a coupled (aka "frying") WCM system similar to the likes of Drupal and FatWire. It requires the repository to be in place at delivery time, and caches content and metadata to allow it to scale out well. There are no plans to convert it to run off a file system.

Re: File Transfer Receiver

sam1980 — Tue, 04 Oct 2011 16:54:10 GMT

Wouldn't it make sense to push binary files such as documents and images which are part of a WQS site directly to the file system on the content delivery server?

Re: File Transfer Receiver

bremmington — Tue, 04 Oct 2011 18:55:46 GMT

You may want to do that yes, which is why I said in my initial reply:

The FTR is more useful if you are not using WQS, or if you want to push some static content to a web server to supplement a WQS website

Although WQS caches all content on the local file system anyway, so binaries are delivered very quickly indeed. It just periodically tests whether the content has been updated in the repository (like a reverse proxy cache would do).