Hi everyone,
I was wondering if anyone knows how to or if it is possible to upload files to a sharepoint (v3/MOSS) document library over FTP. I know it is possible with webdav. If it is possible is this even supported by Microsoft?
Hi everyone,
I was wondering if anyone knows how to or if it is possible to upload files to a sharepoint (v3/MOSS) document library over FTP. I know it is possible with webdav. If it is possible is this even supported by Microsoft?
I don't think so. I think you're options are:
Yeah i know about those 4. A customer of ours claims to have successfully done this over FTP. I'll try and get more info from them, but was just curious if anyone in the community has accomplished this and if there are any gotchas about security/speed/etc that i need to be aware of.
You can map a drive to a SharePoint document library, for example \\serveraddress.domain.com\Documents. So I would try mapping a drive on your FTP server, then making sure files that come in over FTP get sent to that drive.
Direct FTP into SharePoint is not one of your options. You would need to have a timer job run that checks your FTP directory and uploads into the document library.
Thank you all for your responses. We will most likely use the web service API.
Big edit: Have any of you figured out how to upload to SharePoint (WSS) ... I've tried drive mapping and then using Robocopy and Synctoy to copy files thinking a tool might offer greater control (i.e. a Copy Date Modified control). This was confusing to a rookie like me because the files are actually stored in SharePoint as database objects (as I understand it) and therefore SharePoint views display the database object (SQL object's) properties in Document Libraries where a new user would expect to see the file properties. Those file properties are still alive! They just need to be uncovered by a different view, I particularly like the mapped network drive view of a SharePoint Document Library. File attributes are pretty important to my team, so we were concerned about that at the start. As an opinion note though, the default view showing attributes that appear as incorrect is just plain annoying!
The best solution we've come up with for doing large file migrations into SharePoint is a mapped network drive then using a tool called FreeFileSync available at SourceForge to move your files and folders. It's great because it produces verbose error messages and give a lot of control. Especially for the instances that SharePoint trys to block a particular filename or file extension.
I'm new to StackOverflow, but I think it rocks so far!