After we upgraded to OES Linux from NetWare, we found one of the many advantages of running the OES stack on Linux.
We host a private intranet for employees. This intranet allows them to order marketing materials, company uniforms, request vacation time, etc..... We are a small company, and I am the only IT person. In the past, my users had to give me their file for the intranet, such as PDF's of the marketing materials, or photos of the uniforms for the ordering system. Now I am able to give them a mapped drive with directories for all of their stuff for the intranet to go into - "MarketingMaterials", "UniformImages". Access to these directories is controlled by eDir. So far, this is nothing earth shattering, right? The next step is to mount these directories on my SLES web server that is hosting our Intranet. I mount each directory where it needs to be - for example, the "MarketingMaterials" system is looking for a directory named "Images", so I mount "MarketingMaterials" from the OES server to the /srv/www/http/intranet/marketing/images" location on the web server. Now, when the user updates images of the marketing material, the change is instantaneous. They don't have to use some other program to transfer files up to a web server, they simply put the files in a normal mapped drive like they are used to. The magic of mounting the file system from the OES server to the SLES web server takes care of making it all work.
Use YaST to setup both the SLES web server and the OES server to export and mount the file system.
We use this same concept to do file based backup of SQL data from our Windows servers. We use YaST > Network Services > Samba server to setup a share, then map a drive to that share from the windows box. Then simply schedule a task on the windows box that handles copying your data to the OES server.