< Day Day Up > |
You'll use FileMaker Server to make your FileMaker Pro databases available to many users at once across a network. On its own, the FileMaker Pro software can host files for networked access from up to five users at a time, in what's called a peer-to-peer configuration. In practice, except for developmental configurations, or production deployments to very small groups, peer-to-peer sharing is unlikely to be a suitable choice for making files available to multiple networked users. Unless you're in that rather small minority of situations, you'll want to look at FileMaker Server instead. The FileMaker Server Product LineThree separate products are available under the name FileMaker Server:
The essential distinction here is between Server and Server Advanced. Server allows connections from only FileMaker Pro clients. To allow access from ODBC, JDBC, or Web clients, you need to purchase Server Advanced, or use the Option Pack to upgrade an existing copy of Server. Installing and working with the components of FileMaker Server Advanced is covered extensively in other chapters. This chapter focuses on the administration and configuration tools and techniques that pertain to the core Server product. FileMaker Server Versus Peer-to-Peer Database HostingThere are some major differences between FileMaker Server and peer-to-peer database hosting. We've alluded to the differences between these methods in the preceding chapter. The limitations of the peer-to-peer sharing method are fairly severe: With peer-to-peer sharing, no more than ten database files may be served , to no more than five clients at a time. The peer-to-peer method uses a regular copy of FileMaker Pro as the database host, so a deployment of this type also forgoes important features of FileMaker Server, especially the ability to make regular, scheduled backups of the databases. Though such schedules could be created with operating-system-level scripting technologies, it's much simpler to use FileMaker Server's built-in tools. Additionally, peer-to-peer configurations tend to be run on less capable hardware than Server-based configurations. In some cases, we've even seen peer-to-peer configurations hosted on an individual's personal workstation, in constant daily use for many tasks . Neither lower-end hardware nor constant competition for machine resources is a good foundation for a stable multi- user deployment. If you do choose to begin with a peer-to-peer configuration for multi-user database sharing, we recommend that you still treat this situation as a "server-type" deployment as far as possible. Give the database host its own dedicated machine on which to run ”one that people won't casually use for other daily tasks; make sure you have a reliable solution for regular backups; make sure the machine at least meets the minimum specifications for the FileMaker Pro client software, and add a bit more RAM if you possibly can.
The extremely limited scalability and lack of backup automation capabilities ought to discourage you from using FileMaker's peer-to-peer sharing for production use. For the cost of a handful of copies of the FileMaker Pro client, you can host your databases on a solid server platform (FileMaker Server) that can handle 125 database files ( potentially comprising thousands of tables) and up to 250 users. FileMaker Server CapabilitiesWe've talked about some of the features that set the FileMaker Server product line apart as a hosting solution: much greater scalability than the plain FileMaker Pro software, and the capability to perform automated tasks such as backups. There are quite a number of other distinguishing features as well. Here are some of the most important:
In addition to these features, FileMaker Server offers a large number of other important functions as well, such as the capability to send messages to guests, to disconnect idle guests, to limit the visibility of database files based on user privileges, to be run in a scripted fashion from the command line, and to capture a variety of usage statistics and server event information for logging and analysis. All of these features are discussed in the sections to come. FileMaker Server RequirementsLike any piece of server software, FileMaker Server has certain minimum hardware and software requirements. You'll achieve the best results with a dedicated server; as with any piece of server software, it's best if FileMaker Server is the only significant server process running on a given machine. Forcing FileMaker Server to compete with other significant processes, such as mail services or domain controller services, is likely to hurt Server's performance.
The server machine, in addition to being dedicated as far as possible to FileMaker Server, and having the minimum amount of file sharing enabled (preferably none), also needs the things discussed in the following sections. Static IP Address(es)The server machine needs to be enabled for TCP/IP networking with one or more static IP addresses. (Earlier versions of FileMaker Server supported the IPX/SPX protocol in addition to TCP/IP, but this has not been the case for several versions of Server.) Note, by the way, that in contrast with earlier versions of FileMaker Server, FileMaker Server 7 is capable of multi-homing , meaning that it can take full advantage of multiple physical network interfaces, each with its own IP address. FileMaker Server listens on all available network interfaces. As far as we know, it's not possible to configure FileMaker Server to ignore one or more of the available interfaces; if the interface is available, FileMaker Server tries to bind to port 5003 on that interface and begins listening for FileMaker traffic. (The FileMaker client-server port number, 5003, is also not configurable.) Fast Hard Drive
Fast Processor(s)
Lots of RAM
Fast Network Connection
Supported Operating SystemFileMaker Server 7 supports the following operating systems: Mac OS X Server, Mac OS X client, Windows 2000 Server, and Windows 2003 Server. On the Mac OS X side, Mac OS X Server is listed as the "recommended" choice. FileMaker, Inc., has indicated that this means they have not tried to verify the acceptability of the regular Mac OS X operating system for loads greater than 50 connected FileMaker users. Data Center EnvironmentThough not strictly a "requirement" for running FileMaker Server, proper care and housing of server equipment is a necessity, one that's often overlooked, especially in the small- and medium- sized business sectors, some areas of education, and among non-profit groups. These are all key groups of FileMaker users, ones that do not always have sufficient resources to build and maintain anything like a data center. Ideally, a server of any kind should be housed in a physically secure and isolated area, with appropriate cooling and ventilation , with technical staff on hand 24 hours a day to troubleshoot any issues that arise, and with automated monitoring software that periodically checks key functions on the server and notifies technical personnel by email or pager if any services are interrupted . Some organizations are fortunate enough to be able to house their FileMaker Servers in such an environment. But even if you can't provide all those amenities, you can see to the key areas. The server should minimally be up off the floor, well ventilated, and under lock and key if possible. And some sort of monitoring software is nice, and need not break the bank: the open source package Nagios (http://www.nagios.org) is a popular and powerful open-source monitoring package. NOTE Nagios runs on Unix, but can monitor servers running on almost any platform. Many server monitoring packages exist for Windows deployment as well. NOTE It's sometimes a point of confusion, but it's important to know that FileMaker Server 7 will not run on a machine running an earlier version of FileMaker Server at the same time. If you want to run Server 7 and Server 6 at the same time, you need two machines to do so. |
< Day Day Up > |