Subtitles of the Movie

We're continuing now our review of all of the items that we've learned about Filemaker Server 9 and FileMaker Server 9 Advanced. We've learned a significant number of best practices to use in the deployment of FileMaker Server 9 and Filemaker server 9 Advanced and we've learned why best practices are important. Some of the specific best practices that we've learned about are the use of dedicated hardware and the importance of proper configuration and selection of the hard drive subsystem. These two factors are at the top of our list of best practices, they have a greater impact on the performance, behavior and capability of FileMaker Server then anything else. We've learned about best practices regarding the operating systems and particularly that the two best platforms on which to run FileMaker Server 9 or Server 9 Advanced are Windows Server 2003 or Macintosh OS X Server. We've learned about the importance of running at the log out prompt on both platforms. We've learned about other services or demons on the server including the Web Publishing Engine but also the Web Server, either ISS or Apache and we've learned how to configure and manage them. We've learned about the importance of selecting good processors for the computer. We've learned about the importance of using server quality NEC cards because this is the gateway between the machine and the network. We've learned about the importance of memory and that four gigabytes of RAM is the optimal amount in most conditions. We've learned how to configure cache and the importance and the role of the cache. We've learned about ports management, the various ports that have to be open, FileMaker Data ports, FileMaker Server Administration ports, Web Publishing ports, Web Publishing Engine ports, ODBC ports, all of the various ports that are involved. We've learned about the best type of network typology to use. We've learned about the importance of using smart switches verses Dom hubs to vacillate and expedite traffic across our networks. We've learned about ten base T, 100 base T and a thousand base T connectivity. We've learned about the importance of having an uninterruptible power supply and how to prevent a very serious amount of damage from occurring to a FileMaker file if the power on the server should die. We've learned about the importance of minimizing and mitigating heat, humidity, dirt and dust in the server environment and how particularly these can adversely effect the hardware. We've learned about the importance of keeping our server in a secured physical environment and this applies to the backups of the databases as well. We've learned about backups and we've learned about their importance, we've learned about how to back up and we've learned about how not to back up. We've learned about the logs that FileMaker server and FileMaker Server advanced can generate. We've learned what their purpose is, we've learned about the different types of logs from the database server to the access logs to the various web logs and we've learned how to read these web logs. We've learned perhaps more importantly then anything else that server is at the core of effective FileMaker Pro Database Deployment. We've learned that FileMaker is a vital and indispensable ingredient for the preservation of the confidentiality, integrity and availability of the database files and we've learned that the server must be configured correctly in order to work correctly and that misconfiguration of server can be the root cause of much of the difficulties that can arise and less then optimal performance. nd that misconfiguration of server can be the root cause of much of the difficulties that can arise and less then optimal performance.