Defining different shared file systems
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-10-2006 08:40 AM
Objective: I want to define several (shared) file systems from the same Alfresco tree so as to make mapping a network drive more easy (and so as to make the distance to the files of interest shorter).
Attempted solution: I edited "file-servers.xml".
Basically, I added the following lines:
<filesystem name="Test">
<store>workspace://SpacesStore</store>
<rootPath>/app:company_home/Test</rootPath>
</filesystem>
Where "Test" is indeed the name of a workspace below the company home space.
Outcome: The file system was recognized, but it started showing the space store from the top down, not from the Test subspace. Moreover the standard Alfresco file system was no longer available.
Obviously, I seem to have misunderstood the config file. Could anyone provide a working example? A full example of the <homeFolder name=“Home†/> feature would be appreciated as well. Does it have to be included in a <filesystem> configuration of its own?
Thanks
Ludo
Attempted solution: I edited "file-servers.xml".
Basically, I added the following lines:
<filesystem name="Test">
<store>workspace://SpacesStore</store>
<rootPath>/app:company_home/Test</rootPath>
</filesystem>
Where "Test" is indeed the name of a workspace below the company home space.
Outcome: The file system was recognized, but it started showing the space store from the top down, not from the Test subspace. Moreover the standard Alfresco file system was no longer available.
Obviously, I seem to have misunderstood the config file. Could anyone provide a working example? A full example of the <homeFolder name=“Home†/> feature would be appreciated as well. Does it have to be included in a <filesystem> configuration of its own?
Thanks
Ludo
Labels:
- Labels:
-
Archive
15 REPLIES 15
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2006 04:45 AM
Hi,
The fix is in the 1.3 code. The documentation has been updated - http://wiki.alfresco.com/wiki/File_Server_Configuration. There is now an outer <fileystems> tag.
You can also override the filesystems by creating an alfresco/extension/file-servers-custom.xml file. This saves having to edit the main configuration file.
Cheers
Gary
The fix is in the 1.3 code. The documentation has been updated - http://wiki.alfresco.com/wiki/File_Server_Configuration. There is now an outer <fileystems> tag.
You can also override the filesystems by creating an alfresco/extension/file-servers-custom.xml file. This saves having to edit the main configuration file.
Cheers
Gary
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2006 12:13 PM
The documentation has been updated - http://wiki.alfresco.com/wiki/File_Server_Configuration. There is now an outer <fileystems> tag.
All I see on the linked page is "(There is currently no text in this page)"
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2006 12:24 PM
Hi,
The full stop on the end seems to have messed it up, had me confused for a while.
Try this link :-
http://wiki.alfresco.com/wiki/File_Server_Configuration
Cheers
Gary
The full stop on the end seems to have messed it up, had me confused for a while.
Try this link :-
http://wiki.alfresco.com/wiki/File_Server_Configuration
Cheers
Gary
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2006 01:15 PM
Hi,
The full stop on the end seems to have messed it up, had me confused for a while.
Ah, thanks. I didn't notice the period at the end of the link. ops:
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2006 10:17 AM
Hi,
I've just been trying again to map multiple shares from a single store in the 1.3.0 Community version.
In addition to the standard Alfresco filesystem, I defined the following two filesystems:
Result:
1. The Mapping Filesystem can be mapped without any problems
2. The two other filesystems (Alfresco and Processors) cannot be mapped. When I tried it, Windows (XP) complained about "More data is available". On a linux system I noticed the same behaviour. The error message there reads:
I've just been trying again to map multiple shares from a single store in the 1.3.0 Community version.
In addition to the standard Alfresco filesystem, I defined the following two filesystems:
<filesystem name="Processors"> <store>workspace://SpacesStore</store> <rootPath>/app:company_home</rootPath> <relativePath>/Desics/Pipelines/Processors</relativePath> </filesystem> <filesystem name="Mapping"> <store>workspace://SpacesStore</store> <rootPath>/app:company_home</rootPath> <relativePath>/Desics/Pipelines/Mapping</relativePath> </filesystem>
Result:
1. The Mapping Filesystem can be mapped without any problems
2. The two other filesystems (Alfresco and Processors) cannot be mapped. When I tried it, Windows (XP) complained about "More data is available". On a linux system I noticed the same behaviour. The error message there reads:
15625: tree connect failed: ERRSRV - ERRinvnetname (Invalid network name in tree connect.)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-08-2006 05:06 AM
Hi,
I've just tried adding Processors and Mapping shares to the filesystems list and it's working ok.
The 'More data is available' usually indicates a low level protocol error, in this case probably in the DCE/RPC request that gets the share list.
I'll try again with the community version when I get a chance, I'm currently running with the latest enterprise code, but there haven't been any changes in the DCE/RPC code for a long time so that would be the same anyway.
Cheers
Gary
I've just tried adding Processors and Mapping shares to the filesystems list and it's working ok.
The 'More data is available' usually indicates a low level protocol error, in this case probably in the DCE/RPC request that gets the share list.
I'll try again with the community version when I get a chance, I'm currently running with the latest enterprise code, but there haven't been any changes in the DCE/RPC code for a long time so that would be the same anyway.
Cheers
Gary