![]() ![]() It will work on Windows, or on 8.0v1 - 8.0v3 Note: * = FileMaker Server / Server Advanced 8.0v4 on OS X will not work with the optional SuperContainer Companion Plugin. See the section on Plugin autoupdate Compatability matrixĪccessing SuperContainer from FileMaker ProįileMaker Pro Server, Custom Web PublishingįileMaker Pro Server Advanced, Instant Web PublishingįileMaker Pro Server Advanced, Custom Web Publishing You will need to create this file if you have not done so before. QuickLook library is enabled by default.*** OS X 10.6 Snow Leopard and newer /Library/Preferences/ Thumbnails will now be generated using OS X image libs, and PDF will appear as thumbnails instead of icons. The contents of the file should be the following line:Īnd then restart SuperContainer. Just create a new file at the following location: It doesn't matter what the client machines are using, however. It will not work on a Windows server, or when running in Tomcat. This only works if you're running SuperContainer server in standalone mode on an OS X box. This means it can generate thumbnails of PDFs, as well as just about any other image type you throw at it. There's a mac-specific feature that lets SuperContainer use native OS X image processing libraries for its image handling. It will not generate thumbnails for PDF files, CMYK JPEG or TIFF files, RAW files, or Photoshop files. In it's normal configuration, SuperContainer can generate thumbnail images of JPEGs, PNGs, GIF files, and most TIFF files. Core Image library is enabled by default.*** They are listed in order of when they first contacted us: ![]() The following companies have told us that they are set up or willing to configure their servers to host SuperContainer. The URL will become whatever you name the folder, so if you change the folder name from 'SuperContainer' to 'ClientX', the URL to access SuperContainer will be List of hosting providers Change the name of the SuperContainer folder to that client's name and put it into the webapps folder.Modify SuperContainer/WEB-INF/web.xml file and put in valid values for the 'activationCode' and 'registeredTo' settings for your client.Each client will need to purchase a separate license of SuperContainer, or you may purchase a license for them.Please see the Tomcat installation instructions here.You can run SuperContainer version 1.72 or later for your clients in Tomcat by following these steps: to ensure SuperContainer is running on port 80. This is available by selecting Start -> All Programs -> Apache HTTP/Tomcat Server -> Monitor Apacheįinally, launch the standalone SuperContainerServer.jar file as normal and navigate to: Then, you will need to restart your Apache server:Įasiest way to control Tomcat on Windows is to use the Tomcat Monitor tool. You can find more information on these directives by visiting: ProxyPass "/SuperContainer" " ProxyPassReverse "/SuperContainer" " The ProxyPass and ProxyPassReverse are two Tomcat directives that allows remote servers (SuperContainer in this case) to be mapped into the space of the local server (Tomcat). Now, add the following two lines to the nf file after the appropriate "DocumentRoot" as shown below:ĭocumentRoot "/Library/WebServer/Documents" Windows: C:\Program Files (x86)\Apache Software Foundation\Apache2.2\conf NOTE: This may be hidden on Mac OS X and can be reached by using "Go" -> "Go To Folder." in the Finder. In order to use the standalone SuperContainer applet, which by default runs on port 8020, on port 80 you will need to configure some settings within your Apache Tomcat server.įirst, you will want to navigate on your machine to the Apache nf file: Tips and Tricks Using port 80 with standalone SuperContainer deployment 2.6 Tying into FileMaker account privileges. ![]() 1.27 Moving SuperContainer Contents to a New Location.1.24.1 Using /Single File instead of /Files.1.24 Why can't SuperContainer store multiple files in a single directory?. ![]() 1.21 Storing the filename of an uploaded file in a FileMaker field.1.20 Using image transparency with SuperContainer.1.19 Getting the file name of a SuperContainer file.1.17 Viewing multiple page PDFs within the web viewer.1.15 Single record linking to multiple web viewers (ie.1.14 Opening a file in it's native program without Java Applets.1.13 SuperContainer Security and Web Hosting.1.12 Is opening the file to view it different with the noapplet parameter?.1.9 Locking the SuperContainer Registration.1.8.3 'vistasFilesPath' for Vista or later.1.8.1 Change the 'macintoshFilesPath' for OS X.1.8 Configuring where SuperContainer saves files.1.2 SuperContainer for hosting providers.1.1 Using port 80 with standalone SuperContainer deployment. ![]()
0 Comments
Leave a Reply. |