(imported topic written by cstoneba)
I’m trying to create a fixlet that downloads a file from the BES root servers via the TEM infrastructure. They downloaded file that resides on the BES root server will change every day (as will the sha1 and the size of it). How do i go about creating a policy action that will run and download the file regardless of the file’s sha1/size?
(imported comment written by jgstew)
I don’t believe this is possible, but you could do this if the file exists externally from the root server I believe.
Try:
prefetch filename.txt http://domain.com/filename.txt
or
download http://domain.com/filename.txt
(imported comment written by sinucus)
To expand on this you can also you symbolic links within the sha1 folder to point to other locations.
mklink myrotatingfile.log “c:\my custom logs\blah.txt”
then use a download command
download
http://myhostname:52311/bfmirror/downloads/sha1/myrotatingfile.log
which will point to “c:\my custom logs\blah.txt” which is OUTSIDE of your wwwroot folder
The download command cannot do relevance substitution, so if you need to do any custom file naming stuff, you’ll need to do that in the back end and recreate your symlink
(imported comment written by Tim.Rice)
You could try using the
_BESClient_Download_Direct
setting to let the clients download directly rather that through the infrastructure.
(imported comment written by JonLandis)
Dynamic downloads with relevance substitution are possible. They are not well documented. See the second item in the post below.
(imported comment written by cstoneba)
I’d prefer to use the native download commands rather than a manifest if possible. Do the prefetch or download commands require the sha1 and size to e called out? If they don’t need them and it does work, do the relays not cache the download as it goes from the BES root to the endpoint?