I have SC installed as stand alone on Mac OSX SL server. That lets me take advantage of the Mac OSX to generate PDF thumbnails. But I can not seem to get the files to store on the the RAID drive. The system drive is small on 120G and we want all files stored on the 1T raid. I put the SC folder on the RAID and ran the server jar from there. But when I put the raid filepath into the server it just creates that path on the system drive. When I chose to browse it doesn't let me browse to the RAID drive.

SuperContainer writes to the directory specified as the root directory in the configuration. In stand-alone mode, this is configured in the options screen. When you have installed it with Tomcat or FileMaker server you can configure this in the web.xml file. the Web.xml file is located at /Library/FileMaker Server/Web Publishing/publishing-engine/cwpe-tomcat/bin/SuperContainer/WEB-INF/web.xml

David,

So I will lose my ability to generate the pdf thumbnail and take advantage of being on the Mac OS in order to store the files where I want. Thats disappointing. I can't afford to put them on the root drive. We will have a lot of document storage to deal with. But I really like the way the thumbnail is rendered in the viewer. So there is no workaround for this?

SuperContainer writes to the directory specified as the root directory in the configuration. In stand-alone mode, this is configured in the options screen. When you have installed it with Tomcat or FileMaker server you can configure this in the web.xml file. the Web.xml file is located at /Library/FileMaker Server/Web Publishing/publishing-engine/cwpe-tomcat/bin/SuperContainer/WEB-INF/web.xml

Selecting a root directory for SuperContainer does not change SuperContainer's ability to generate PDF previews or any other SuperContainer functionality.

Right but I though you told me that running it stand alone was the only way to take advantage of Mac OS ability o generate PDF's and that was the advantage of stand alone vs with FMP server. If thats not the case then what are the advantages and what do I give up.

Selecting a root directory for SuperContainer does not change SuperContainer's ability to generate PDF previews or any other SuperContainer functionality.

You are correct. You can only generate previews of pdf documents when running in stand-alone mode on a mac. Setting a root directory does not affect your deployment method, it's just a setting in the options screen or web.xml file that changes where supercontainer stores files.

Just to clarify on here, on a mac you can reach an external drive through the /Volumes/ directory, so if your main hard drive is "Macintosh Hard Drive" but you need to go to "External Drive" your path will be /Volumes/External Drive/myFolder/. You can select this drive through the options screen.