This section contains frequently asked questions and their possible solutions.
Performance Issues
If you experience slow performance of your Web application server, we recommend optimizing the memory for Java VM in the catalina.sh or catalina.bat (Windows) file of the Apache Tomcat Web application server. Under Linux, we also recommend checking the limits for file descriptors, as in most cases the soft limit should be increased. For more information on both topics, see the documentation of the Apache Tomcat Web application server.
Asset Download and Preview not Possible
How is the Cumulus Server able to access an asset and which settings are required?
There are two possible reasons for most problems:
• permission problem: The user under which the Cumulus Server is running might not have read permission for these assets. Check for the right permissions.
• wrong entries in the FileSharing.info file: The Cumulus Server is not able to create correct UNIX asset references due to wrong entries in the FileSharing.info file. Check the FileSharing.info file. (For details, see below.)
Use of the FileSharing.info File with UNIX or macOS Installations
What is the FileSharing.info for?
If a user wants to preview or download an asset via the Internet, Web Client or the Cumulus Server must have access to the actual asset. To do this Cumulus reads the stored asset reference and uses it to find the asset. This is also called “resolving” an asset reference.
If assets have been cataloged by macOS or Windows Clients, their asset references cannot be resolved by Cumulus under UNIX or macOS.
So Cumulus needs to create UNIX asset references based upon the macOS or Windows file system asset references. This is done by employing a special file that contains information on how a Windows or macOS asset reference should be transferred to a corresponding UNIX reference. This special file is named FileSharing.info. The information stored in this file must be adapted to your Cumulus configuration.
You can have a separate FileSharing.info file for your Web Client installation. If a FileSharing.info file is not available with your Web Client installation, the FileSharing.info file of your Cumulus Server installation is used. The FileSharing.info file for your Cumulus Server installation can be edited with a utility provided by the Remote Admin module of the Server Console.
If you want a separate FileSharing.info file for your Web Client installation, this file must be adapted manually to your Cumulus configuration.
For example:
The file picture.jpg is stored on a UNIX or macOS file server and can be accessed
• by Windows via the following path: \\FILESERVERWINNAME\WINVOLUMEONSERVER\images\
• by macOS via the following path: *:FILESERVERMACNAME:MACVOLUMEONSERVER:images:
Under UNIX or macOS this file is stored under:
• /shares/volume/images/
The Filesharing. info needs the following information to create the correct UNIX asset reference based upon the given Windows asset references:
[Windows] # Begin of the Windows section Server Name = FILESERVERWINNAME Volume Path = /shares/volume Volume Name = WINVOLUMEONSERVER
The Filesharing. info needs the following information to create the correct UNIX asset reference based upon the given macOS asset references:
[Macintosh] # Begin of the Macintosh section Server Name = FILESERVERMACNAME Volume Path = /shares/volume Volume Name = MACVOLUMEONSERVER
Make sure that you enter the exact server names and volume names (case sensitive) as you see them from the appropriate platform (in the Chooser on macOS and Explorer on Windows). Never enter the UNIX server name.
HELIOS EtherShare 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 PCShare, you do not need to update the Windows section settings manually.