#Filemaker server 12 ports pro#

But what happens when a web page is no longer is responsive? Which process failed? Is it a page error, a Database Server problem, or an issue with the WPE? As you can imagine, manually checking the state of the server becomes tedious. Custom web publishing such as PHP communicates to the Database Server via the WPE. The Database Server is perhaps the most obvious component, as this hosts the databases that are shared with clients.Īny type of web publishing requires the Web Publishing Engine (WPE) to be active and running.

#Filemaker server 12 ports pro#

Opening files in FileMaker Pro that were removed by the FMS admin consoleįileMaker Server 11 includes several components to publish databases to client machines.Opening backup files in FileMaker Pro - ie, not hosted by a server.Uploading FMP12 backup files with the FileMaker Server admin console.

FileMaker Server 12 Configuration Guide (also found at TechNet)Ĭircumstances where external container data will break (container fields will show files as missing):.Using Container Fields in FileMaker 12 (log in to FileMaker TechNet to download).In case you need to get some basic knowledge about FileMaker Server 12 and the new features related to backup and enhanced container fields, here are some great resources to get you started: Understanding these situations will help you properly restore FileMaker 12 files that use external container storage. In the course of my work on a customer project, I discovered that the links to externally stored container fields with a FileMaker Server 12 backup can break if the backup is not restored properly. After trying a number of different scenarios, I have come up with a list of circumstances where container fields will remain intact and when they won’t.Īll examples are using a Windows based FileMaker server and apply equally to both secure and open external container storage.