The FileSharing.Info file is used by Cumulus Servers to build:
• UNIX asset references based upon OS X or Windows file system asset references
• OS X asset references based upon UNIX or Windows file system asset references
It contains information on how a Windows, UNIX or OS X asset reference should be converted to a corresponding UNIX or OS X reference. The information stored in this file must be adapted to your Cumulus configuration.
Remote Admin provides a utility to ease the configuration of the FileSharing.Info file. The utility provides different tabs:
For the volumes from which assets are cataloged, you need to add entries for the FileSharing.Info that contain the required information.
NOTE: HELIOS EtherShare and HELIOS PCShare If HELIOS EtherShare is installed on the machine that runs the Cumulus Server, you do not need to update the Macintosh section settings of the FileSharing.Info file manually; Cumulus does this automatically. If you have also installed HELIOS PCShare, you do not need to update the Windows section settings manually. The HELIOS EtherShare and HELIOS PCShare tabs display the information that is provided to the FileSharing.Info by this software.
To add the information on the platform volume from which assets are cataloged, click the tab for the appropriate platform and click the Add button. A dialog opens that asks for the information needed to create the correct platform asset reference based upon the asset references already provided.
Information Needed
• Volume Path – volume path of the share point in the notation of the platform (e.g. UNIX notation: /shares/volume)
• Server Name – Name of the file server. This can be the IP address or the real server name (DNS-resolvable name).
• Zone Name – AppleTalk zone name as it appears to OS X clients (OS X only)
• Volume Name – Name of the volume on the file server
• Encoding – The encoding for the Macintosh section definitions should always be set to UTF-8. The encoding for the Windows section definitions should always be set to WinLatin1.
Make sure you enter the server names and volume names (case sensitive) exactly as they are displayed for the appropriate platform in an Asset Reference field of the Cumulus Information window/view. This field also shows what you should enter as server name (the IP address or the real server name). The volume names entered must match exactly the names of the volumes themselves. (Note that spaces must not be escaped by quotes.) Make sure you don’t enter a UNIX server name.
After the FileSharing.Info is edited, the records must be updated to get valid entries for the missing platform asset references. Use a Cumulus Client (Mac or Windows) to update the records (Metadata > Update Records > Update now). Use an Asset Handling Set that has theFile System AssetStore for the missing platform asset references activated. After doing so, the Asset Reference field in the Information window/view will show the following UNIX path for a cataloged asset: //MyServer/MySharedVolume/MyFolderStructure/MyAsset
Without correct FileSharing.Info entries, a UNIX reference would look something like this: MyServer:/home/LoginName/MySharedVolume/MyFolderStructure/MyAsset This is a non existing path and Cumulus cannot resolve it.
The entries on the Cumulus FileSharing.Info Macintosh and Cumulus FileSharing.Info Windows tab of Remote Admin FileSharing.Info Settings window can be edited or deleted. To edit an entry, select the desired entry and click Edit. To delete an entry, select the desired entry and click Delete.
To save the changes you made in the Remote Admin FileSharing.Info Settings window, select Actions > Save.
Additional Notes
• Best Guess If the Unix File System AssetStore is activated, during cataloging, the Cumulus Client tries to create a corresponding UNIX asset reference and sends a request to the Cumulus Server. Using the FileSharing.Info file, the Cumulus Server answers this request. If a UNIX asset reference could be created, it is stored with the cataloged asset. If the Cumulus Server cannot create a UNIX asset reference, it stores instead a “best guess” reference such as: /usr/home/images/picture.jpg.
• Asset Handling Sets When working in a cross-platform environment, Canto recommends using Asset Handling Sets that have the Asset Storage modules for all three different file systems activated: Mac OS File System, UNIX File System and Windows File System.
• Cumulus Internet Solutions and Local Access If you run Cumulus Web Client or Portals on a computer other than your Cumulus Server, you might need a configured FileSharing.Info file on the computer running the Cumulus Internet Solution. The FileSharing.Info file is needed in case the Cumulus Internet Solution accesses assets that were cataloged locally from the same computer the Cumulus Internet Solution is running on. In this special case, a properly configured FileSharing.Info file must be copied to the etc (UNIX) or conf (Windows) subfolder of the installation folder of the Cumulus Internet Solution. If you use a Cumulus Java Classes installation different from the one in the Cumulus Internet Solution installation folder, the configured FileSharing.Info file must be copied to the etc (UNIX) or conf (Windows) subfolder of that Cumulus Java Classes installation folder.
• Applications based on Cumulus Java Classes If you use an additional application with your Cumulus installation, and this application is running under UNIX or OS X on a computer other than your Cumulus Server, you might need a FileSharing.Info file on this computer. In this case the configured FileSharing.Info file must be copied to the etc (UNIX) or conf (Windows) subfolder of the Cumulus Java Classes installation folder used by the application.