
Chapter 3 | Deploying FileMaker Server across multiple machines 27
The following illustration shows the ports that must be open in a firewall in order for FileMaker
clients and Admin Console to communicate with FileMaker
Server.
1 To upgrade from an earlier version of FileMaker Server, see chapter 6, “Upgrading or moving
an existing installation.”
1 If you already have an single-machine deployment of FileMaker Server 13, you can add a
second machine to your existing deployment. To add a second machine, install
FileMaker
Server on the second machine as a worker (see “Installing on the worker machine”
on page 28). Then in Admin Console on your existing master machine, change the deployment
to two machines. For more information on editing an existing deployment, see FileMaker Server
Help.
1 Locate your license key. See “About the license key” on page 8.
1 If you are currently running FileMaker Pro on the same machine, you must quit FileMaker Pro
before installing FileMaker
Server.
Also keep in mind the following:
1 If the machine has anti-virus software installed, you may need to disable or uninstall it before
running the FileMaker
Server installer. Don’t enable anti-virus software again until after the
Deployment assistant has finished.
1 You cannot run two different versions of FileMaker Server on the same machine at the same time.
1 Because some DHCP servers cycle IP addresses, FileMaker recommends using a static IP
address.
1 OS X: Avoid using the OS X Server application to enable any HTTP services while running
FileMaker
Server. HTTP services provided by OS X Server can interfere with
FileMaker
Server. See “Using the Apache web server in OS X” on page 72.
FileMaker Server Clients
FileMaker Pro
Master
machine
FileMaker Go
FileMaker WebDirect
Custom Web Publishing
80, 443, 5003
80, 443, 5003
ODBC/JDBC
80, 443
80, 443
2399
Ports that must be open for clients
Worker
machine
80, 443, 2399,
5003, 16000
80, 443
Admin Console
16000
Commenti su questo manuale