FILEMAKER SERVER SOFTWARE LICENSE IMPORTANT -- READ CAREFULLY: BY INSTALLING, COPYING, DOWNLOADING, ACCESSING OR OTHERWISE USING THE SOFTWARE, YOU AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. IF YOU DO NOT AGREE TO THE TERMS OF THIS LICENSE, DO NOT INSTALL, ACCESS OR USE THE SOFTWARE, AND PROMPTLY RETURN IT (IF APPLICABLE) TO YOUR PLACE OF PURCHASE FOR A FULL REFUND. IF YOU LICENSED THIS SOFTWARE UNDER A FILEMAKER VOLUME LICENSE AGREEMENT, THEN THE TERMS OF SUCH AGREEMENT WILL SUPERSEDE THESE TERMS, AND THESE TERMS DO NOT CONSTITUTE THE GRANTING OF AN ADDITIONAL LICENSE TO THE SOFTWARE. The software and documentation accompanying this License ("Software") are licensed, not sold, to you by FileMaker, Inc. and/or FileMaker International (collectively referred to as "FMI") for use only under the terms of this License, and FMI reserves any rights not expressly granted to you. The rights granted are limited to FMI's and its licensors' intellectual property rights in the Software and do not include any other patents or intellectual property rights. You own the media on which the Software is recorded or xed, but FMI and its licensors retain ownership of the Software itself. 1. License.
(a) General License. The Software includes the following components: (1) database server, (2) web publishing engine, and (3) web server module. Each Software component may only be installed and used on a single computer. These three Software components may be installed on the same computer or on different computers. You may install and use only one copy of the Software on a single computer at a time, except as provided in this Section 1. Even though both Windows and Mac OS versions of the Software may be provided in multiple languages, you are only licensed to use one version of the Software on one platform (i.e., the Windows or Mac OS version) in one language at a time. You may not use or run more than one instance of the Software from the same operating system (e.g., using virtualization or other technologies) at the same time. The ODBC/JDBC connectivity APIs and the instant web publishing functionality may only be used if you have licensed FileMaker Server Advanced. (b) Additional Software. If you have paid for and licensed the additional FileMaker Server advanced functions for web serving and ODBC/JDBC connectivity APIs ("Additional Software"), then the Additional Software may be installed on the same computer or a different computer than the main Software application. The Additional
Software is otherwise subject to the terms and conditions governing the Software. (c) Client Drivers. The FileMaker ODBC/JDBC "Client Drivers" are the driver portions of the Software that allow third party applications or custom applications to access FileMaker Server as an ODBC or JDBC data source. You may copy and distribute the Client Drivers for use on more than one computer, provided that the Client Drivers may only be used with the Software. (d) FileMaker Server Admin. You may copy and distribute the FileMaker Server Admin portion of the Software for use on more than one computer, provided that it may only be used with the Software. (e) Backup. You may make one copy of the Software in machine readable form solely for backup purposes. As an express condition of this License, you must reproduce on each copy any copyright notice or other proprietary notice that is on the original copy supplied by FMI. (f) Upgrades & Updates. If the Software is licensed as a version or feature upgrade or update, then you may only use the Software to replace a validly licensed version of the same software. You agree that the upgrade or update does not constitute the granting of a second license to the Software (i.e., you may not use the upgrade or update in addition to the software it is replacing, nor may you transfer the software which is being replaced to a third party). (g) Education. If the Software is licensed at an education discount, then the Software may only be used by enrolled students, faculty, teachers and administrators at an accredited K-12 educational institution (or equivalent) or higher education institution exclusively for educational purposes. 2. Restrictions.
(a) Maximum Number. The "Maximum Number" of clients or sessions as used in this Section2 is stated in your Software documentation and in the "Clients" tab of the FileMaker Server Admin Software. (b) FileMaker Pro Clients. You may not allow more that the Maximum Number of FileMaker Pro clients to concurrently access the Software. In addition, this License does not grant you any rights to use FileMaker Pro software, and you must separately pay for and license each copy of FileMaker Pro that is used with the Software. (c) FileMaker Server Advanced. You may not allow any clients or technologies other than FileMaker Pro and FileMaker Server Admin to access the Software unless you have paid for and licensed the Additional Software. Runtime versions developed with FileMaker Pro Advanced or other tools may not be clients of the Software. (d) ODBC/JDBC Clients. If you have paid for and licensed the Additional SoftwareFileMaker Server Advanced, then you may allow ODBC/JDBC clients to access

the Software. However, you may not allow more than the Maximum Number of ODBC/ JDBC clients to concurrently access the Software, and you may not allow more than the Maximum Number of total ODBC/JDBC clients plus FileMaker Pro clients to concurrently access the Software. (e) Web Session. You may allow FileMaker custom web publishing "Web Sessions" (e.g., XSLT) to access the Software. s. If you have paid for and licensed the Additional SoftwareFileMaker Server Advanced, then you may also allow FileMaker instant web publishing "Web Sessions" (which is dened as FileMaker instant web publishing clients and FileMaker custom web publishing clients using sessions) to access the Software. However, youYou may not allow more than the Maximum Number of Web Sessions to concurrently access the Software. (f) Other Web Connections. If you have paid for and licensed the Additional Software, then you may allow access to the Software through web connections that do not employ sessions, and the number of these web connections is not limited by these license restrictions. (g) FileMaker Server Advanced Development License. If you have licensed the FileMaker Server Advanced Development License then FileMaker Server Advanced is limited to the Maximum Number of FileMaker Pro/ODBC/JDBC clients and the Maximum Number of Web Sessions as specied for the Development License. In addition, the Software provided under the Development License may only be used for development and testing purposes and it may not be used in a production environment. (h) Other Limitations. YOU MAY NOT REVERSE ENGINEER, DECOMPILE OR DISASSEMBLE THE SOFTWARE, EXCEPT AND ONLY TO THE EXTENT EXPRESSLY PERMITTED BY APPLICABLE LAW. YOU MAY NOT MODIFY, ADAPT, TRANSLATE, RENT, LEASE, LOAN OR CREATE DERIVATIVE WORKS BASED UPON THE SOFTWARE OR ANY PART THEREOF. (i) Restricted Uses. THE SOFTWARE IS NOT INTENDED FOR USE IN THE OPERATION OF NUCLEAR FACILITIES, AIRCRAFT NAVIGATION OR COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL SYSTEMS, LIFE SUPPORT MACHINES OR OTHER EQUIPMENT IN WHICH THE FAILURE OF THE SOFTWARE COULD LEAD TO DEATH, PERSONAL INJURY, OR SEVERE PHYSICAL OR ENVIRONMENTAL DAMAGE. (j) Transfer Restriction. YOU MAY NOT TRANSFER OR ASSIGN YOUR RIGHTS UNDER THIS LICENSE TO ANOTHER PARTY WITHOUT FMI'S PRIOR WRITTEN CONSENT. 3. Termination. This License is effective until terminated. This License will terminate automatically without notice from FMI or judicial resolution if you fail to comply with any provision of this License. Upon such termination you must destroy the Software, all accompanying written materials and all copies thereof, and Sections 5, 6, and 7 will

survive any termination or cancellation of this License. 4. Export Law Assurances. You may not use or otherwise export or re-export the Software except as authorized by United States law and the laws of the jurisdiction in which the Software was obtained. In particular, but without limitation, the Software may not be exported or re-exported (a) into (or to a national or resident of) any U.S. embargoed countries (currently Cuba, Iran, Libya, North Korea, Sudan and Syria), or (b) to anyone on the U.S. Treasury Department's list of Specially Designated Nationals or the U.S. Department of Commerce's Denied Person's List or Entity List. By using the Software you represent and warrant that you are not located in, under control of, or a national or resident of any such country or on any such list. 5. Limited Warranty. FMI warrants for a period of ninety (90) days from your date of purchase that the Software as provided by FMI will perform substantially in accordance with the accompanying documentation. FMI's entire liability and your sole and exclusive remedy for any breach of the foregoing limited warranty will be, at FMI's option, replacement of the Software, refund of the purchase price or repair or replacement of the Software which is returned to FMI or an FMI authorized representative with a copy of the receipt. THIS LIMITED WARRANTY IS THE ONLY WARRANTY PROVIDED BY FMI AND FMI AND ITS LICENSORS EXPRESSLY DISCLAIM ALL OTHER WARRANTIES, CONDITIONS OR OTHER TERMS, EITHER EXPRESS OR IMPLIED (WHETHER COLLATERALLY, BY STATUTE OR OTHERWISE), INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES, CONDITIONS OR OTHER TERMS OF MERCHANTABILITY, SATISFACTORY QUALITY AND/OR FITNESS FOR A PARTICULAR PURPOSE WITH REGARD TO THE SOFTWARE AND ACCOMPANYING WRITTEN MATERIALS. FURTHERMORE, THERE IS NO WARRANTY AGAINST INTERFERENCE WITH YOUR ENJOYMENT OF THE SOFTWARE OR AGAINST INFRINGEMENT OF THIRD PARTY PROPRIETARY RIGHTS BY THE SOFTWARE. FMI DOES NOT WARRANT THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT DEFECTS IN THE SOFTWARE WILL BE CORRECTED. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY FMI OR AN FMI AUTHORIZED REPRESENTATIVE SHALL CREATE A WARRANTY. BECAUSE SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF IMPLIED WARRANTIES, CONDITIONS OR OTHER TERMS THE ABOVE LIMITATION MAY NOT APPLY TO YOU. THE TERMS OF THIS DISCLAIMER AND THE LIMITED WARRANTY UNDER THIS SECTION 5 DO NOT AFFECT OR PREJUDICE THE STATUTORY RIGHTS OF A CONSUMER ACQUIRING THE SOFTWARE OTHERWISE THAN IN THE COURSE OF A BUSINESS, NEITHER DO THEY LIMIT OR EXCLUDE ANY LIABILITY FOR DEATH OR PERSONAL INJURY CAUSED BY FMI'S NEGLIGENCE.

Exclusion and Limitation of Remedies and Damages.
(a) Exclusion. IN NO EVENT WILL FMI, ITS PARENT, SUBSIDIARIES, OR ANY OF ITS LICENSORS, DIRECTORS, OFFICERS, EMPLOYEES OR AFFILIATES OF ANY OF THE FOREGOING BE LIABLE TO YOU FOR ANY CONSEQUENTIAL, INCIDENTAL, INDIRECT OR SPECIAL DAMAGES WHATSOEVER (INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION AND THE LIKE) OR DIRECT LOSS OF BUSINESS, BUSINESS PROFITS OR REVENUE, WHETHER FORESEEABLE OR UNFORESEEABLE, ARISING OUT OF THE USE OF OR INABILITY TO USE THE SOFTWARE OR ACCOMPANYING WRITTEN MATERIALS, REGARDLESS OF THE BASIS OF THE CLAIM (WHETHER UNDER CONTRACT, NEGLIGENCE OR OTHER TORT OR UNDER STATUTE OR OTHERWISE HOWSOEVER ARISING) AND EVEN IF FMI OR A FMI REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. (b) Limitation. FMI'S TOTAL LIABILITY TO YOU FOR DAMAGES FOR ANY CAUSE WHATSOEVER NOT EXCLUDED BY SECTION 6(a) ABOVE HOWSOEVER CAUSED (WHETHER IN CONTRACT, NEGLIGENCE OR OTHER TORT, UNDER STATUTE OR OTHERWISE HOWSOEVER ARISING) WILL BE LIMITED TO THE GREATER OF U.S.$5.00 OR THE MONEY PAID FOR THE SOFTWARE THAT CAUSED THE DAMAGES. THE PARTIES AGREE THAT THIS LIMITATION OF REMEDIES AND DAMAGES PROVISION SHALL BE ENFORCED INDEPENDENTLY OF AND SURVIVE THE FAILURE OF ESSENTIAL PURPOSE OF ANY WARRANTY REMEDY.THIS LIMITATION WILL NOT APPLY IN CASE OF DEATH OR PERSONAL INJURY CAUSED BY FMI'S NEGLIGENCE ONLY WHERE AND TO THE EXTENT THAT APPLICABLE LAW REQUIRES SUCH LIABILITY. BECAUSE SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE LIMITATION OF LIABILITY IN THIS SECTION 6 MAY NOT APPLY TO YOU. NOTHING IN THIS LICENSE AFFECTS OR PREJUDICES THE STATUTORY RIGHTS OF A CONSUMER ACQUIRING THE SOFTWARE OTHERWISE THAN IN THE COURSE OF A BUSINESS. General. If there is a local subsidiary of FMI in the country in which this License was purchased, then the local law in which the subsidiary sits shall govern this License. Otherwise, this License shall be governed by the laws of the United States and the State of California. The parties agree that the United Nations Convention on Contracts for the International Sale of Goods (1980), as amended, is specically excluded from application to this License. This License constitutes the entire agreement between the parties with respect to the Software licensed under these terms, and it supersedes all prior or contemporaneous agreement, arrangement and understanding regarding such subject matter. You acknowledge and agree that you have not relied on any representations made by FMI,

however, nothing in this License shall limit or exclude liability for any representation made fraudulently. No amendment to or modication of this License will be binding unless in writing and signed by FMI. If any provision of this License shall be held by a court of competent jurisdiction to be contrary to law, that provision will be enforced to the maximum extent permissible, and the remaining provisions of this License will remain in full force and effect. No failure or delay by FMI in exercising its rights or remedies shall operate as a waiver unless made by specic written notice. No single or partial exercise of any right or remedy of FMI shall operate as a waiver or preclude any other or further exercise of that or any other right or remedy. All Software provided to the U.S. Government pursuant to solicitations issued on or after December 1, 1995 is provided with the commercial license rights and restrictions described in this License. All Software provided to the U.S. Government pursuant to solicitations issued prior to December 1, 1995 is provided with RESTRICTED RIGHTS as provided for in FAR, 48 CFR 52.227-14 (JUNE 1987) or DFAR, 48 CFR 252-227-7013 (OCT 1988), as applicable.

1 If you use your own PHP engine, you must manually install the FileMaker API for PHP to use PHP
publishing. See FileMaker Server Custom Web Publishing with PHP for more information. Note Instant Web Publishing requires a FileMaker Server Advanced license.
23. Select a web server and click Next. Note If the Deployment assistant fails to detect the web server, see chapter 6, Setting up the web server. Also be sure that the necessary firewall ports are open. See Before you begin on page 11.
Note To specify a web server later, select Skip this step and select a web server later and click Next. 24. If you see the following Web Server Test Failed step, the Deployment assistant detected but could not communicate with the web server. Specify the Protocol, Host address, and Port for the web server and click Retry. For more information, see Troubleshooting on page 43.
25. A deployment summary appears. Click Finish or click Back to change any of your choices.
26. FileMaker Server is being deployed. This may take a few minutes.
27. FileMaker Server Admin Console starts. Click OK in the Welcome dialog box. If you dont see the Welcome dialog box, open a web browser and enter: http://localhost:16000 Note You can register FileMaker Server and verify the FileMaker Server deployment now or later. See Next steps on page 20.
28. In the FileMaker Server Overview pane, note the IP address of the server. Tip Write down the IP address so that you can start the Admin Console from another computer. Windows: When Admin Console starts and the firewall is on, an alert displays. Click Unblock to start Admin Console.
Write down the IP address

Next steps

Now that you have deployed FileMaker Server, get started using your new software. 1. Start Admin Console: See Starting Admin Console on page 49. 2. Test your installation: FileMaker Server provides a sample database and a one-click method to verify that your installation is working. See chapter 3, Testing your deployment. 3. Register your software: Register your copy of FileMaker Server. See Registration and customer support on page 68. 4. Administer FileMaker Server: For information on how to upload databases, schedule backups, and other regular tasks, see chapter 4, Administration overview.

FileMaker Server allows you to deploy its components on multiple machines to improve overall performance. In many environments, a single-machine deployment provides sufficient performance for web publishing. However, if FileMaker Server will be used frequently by internet clients accessing data with Instant Web Publishing, XSLT, or PHP, then you can deploy the components of FileMaker Server across two or three machines. You can first deploy FileMaker Server on fewer machines. If the web publishing load increases, you can change your initial deployment to improve FileMaker Servers performance. Note If youre not using web publishing, you dont gain performance improvements from a multiplemachine deployment.

Deployment alternatives

The diagram below shows the major components of FileMaker Server. You can deploy them all on one machine or across two or three machines. The operating systems of the machines can be all Windows, all Mac OS, or any combination of the two.
FileMaker Server components

Web Server

Web Server Module PHP Engine

Web Publishing Engine

Database Server

Admin Console

FileMaker Server uses the following components:
1 Web Server: FileMaker Server requires Internet Information Services (IIS) on Windows or an Apache
web server on Mac OS. For Windows, install and enable IIS before deploying the Web Server Module. The Apache web server is installed as part of Mac OS, but you need to enable web sharing.
1 Web Server Module: this FileMaker Server software component is installed on the web server host
machine. The Web Server Module enables the Web Publishing Engine to connect to the web server.
1 Web Publishing Engine: provides the Custom Web Publishing services for databases hosted by
FileMaker Server and the Instant Web Publishing services (for FileMaker Server Advanced).
1 PHP Engine: for Custom Web Publishing with PHP, FileMaker Server requires a PHP engine to respond
to requests from the web server and to process PHP code. FileMaker Server includes a PHP engine and the FileMaker API for PHP. When PHP code calls the FileMaker API for PHP, those calls are interpreted and sent to the Web Publishing Engine.
1 Database Server: hosts the databases that you share with FileMaker Pro users and publish on the web.
In a multiple-machine deployment, the machine running the Database Server is called the master machine. See the description below.
1 Admin Console: runs on any client computer from which you want to configure and administer
FileMaker Server. When you deploy FileMaker Server across two or three machines, one machine is always the master and the others are workers.

1 The master machine is always the machine on which the Database Server is deployed. 1 The worker machines are the machines that run the Web Publishing Engine and the web server.
The master communicates with the workers to handle database requests from users, configure the settings on all machines, and monitor the status and activity of all components. Important To enhance the security of your database solution, especially on the internet, consider using a firewall on the public side of a FileMaker Server deployment. Also consider using SSL for the web server. For more information on setting up security for web published solutions, see www.filemaker.com/support/security.

One-machine deployment

You can deploy FileMaker Server on one machine in two ways: Database Server only or Database Server and Web Publishing Engine. For information on installing FileMaker Server in a one-machine configuration, see chapter 1, Installation quick start. Database Server only You can install FileMaker Server on one machine with web publishing disabled. With this type of deployment, you can serve FileMaker Pro clients and, if you have a FileMaker Server Advanced license, serve ODBC/JDBC clients. Benefits: This is the easiest deployment to set up and administer, if you don't need web publishing.
Admin Console Ports 5003, 16000, and 16001 must be open. Ports 5013, 16004, and 50003 must be available.

Chapter 2

Deploying FileMaker Server across multiple machines
Database Server and Web Publishing Engine You can install Database Server, the Web Publishing Engine, and all of the associated software components on the same machine as your web server. Benefits: This is the simplest deployment and the one that most FileMaker Server users will use. This configuration is suitable for small deployments (up to 50 FileMaker Pro clients) and limited web publishing.
Admin Console Ports 80, 5003, 16000, 16001, 16016, and 16018 must be open. Ports 5013, 16004, 16006, 16008, 16010, 16012, 16014, and 50003 must be available.

Two-machine deployment

You can deploy FileMaker Server across two machines in two ways. Two-machine You deploy the Web Publishing Engine, web server, and Web Server Module on one machine. You deploy the Database Server on a second machine. Benefits: This deployment separates all of the web publishing-related components from the Database Server. Under most conditions, this configuration is the highest performing FileMaker Server deployment.

17. A FileMaker Server Start Page opens in the web browser. It may take a few minutes for the Admin Console to start and the Deployment assistant to appear.
Note If the Admin Console and Deployment assistant do not start, see Deployment assistant does not start after installation on page 44. 18. Click Run (Windows) or Allow (Mac OS) to respond to the security message. 19. In the first step of the Deployment assistant, assign the user name and password you want to use whenever you log into Admin Console as the server administrator. The server administrator is responsible for installing and configuring FileMaker Server as well as managing the FileMaker Pro databases hosted on FileMaker Server. Click Next. Note User Name is not case-sensitive. Password is case-sensitive.
20. Specify a name, description, and contact information for this deployment of FileMaker Server, then click Next. This information will appear on the FileMaker Server Admin Console Start Page. The Server Name is displayed to FileMaker Pro users in the Open Remote dialog box.
21. If you purchased a FileMaker Server Advanced license, you can enable a hosted FileMaker Pro file to be a data source via ODBC and JDBC. Click Yes, enable ODBC/JDBC or No, do not enable ODBC/JDBC. Click Next. Important This feature allows clients to use FileMaker files as data sources using ODBC and JDBC. This feature is not needed to host FileMaker Pro databases that access ODBC data sources. For more information, see FileMaker Pro Help.
22. If you want to publish FileMaker data on the internet or intranet, click Yes, enable Web Publishing. Otherwise, click No, do not enable Web Publishing. Then click Next. Continue with step 28 if you are not enabling web publishing. Note To use web publishing, the web server must be installed and running. See chapter 6, Setting up the web server.
23. Select the web publishing technologies you want to use and click Next.
24. Select a deployment type. Click Next. For more information, see Deployment alternatives on page 21.
25. Assign a worker machine to each role (Web Publishing Engine or web server). Click Next.
1 The Deployment assistant detects all unassigned worker machines on the local network and shows
their IP addresses in the Machines list beside each role. If a worker is not listed, click Rescan. Then check to see whether the worker is listed.
1 If a worker's IP address is still not listed, enter the address in IP Address and click Lookup. The IP
address you entered is added to the Machines list if the machine responds and is an available worker. Note You will not be able to see the worker machines if the required ports of the firewall are not open. See Before you begin on page 25.
26. Select a web server and click Next. The available choices of web servers are those supported by the worker machines. Note If the Deployment assistant fails to detect the web server, see chapter 6, Setting up the web server. Also be sure that the necessary firewall ports are open. See Before you begin on page 25.

Note To specify a web server later, select Skip this step and select a web server later and click Next.
27. If you see the following Web Server Test Failed step, the Deployment assistant detected but could not communicate with the web server. Specify the Protocol, Host address, and Port for the web server and click Retry. For more information, see Troubleshooting on page 43.
28. A deployment summary appears. Click Finish or click Back to change any of your choices.
29. FileMaker Server is being deployed. This may take a few minutes.
30. FileMaker Server Admin Console starts. Click OK in the Welcome dialog box. If you dont see the Welcome dialog box, open a web browser and enter: http://localhost:16000 Note You can register FileMaker Server and verify the FileMaker Server deployment now or later. See Next steps on page 39.
31. In the FileMaker Server Overview pane, note the IP address of the master machine. Tip Write down the IP address so that you can start the Admin Console from another computer. Windows: When Admin Console starts and the firewall is on, an alert displays. Click Unblock to start Admin Console.
Write down the IP address of the master machine

Installation notes

1 On Windows, you can install FileMaker Server in a non-default location including a non-boot volume,
but not on remote network drives or external removable drives. The path you specify replaces the beginning of the default installation path, \Program Files\FileMaker\FileMaker Server (Windows 32-bit) or \Program Files (x86)\FileMaker\FileMaker Server (Windows 64-bit). For example, if you specify the My_Path installation folder, the Databases, Scripts, and Extensions folders are installed as follows:
1 \My_Path\Data\Databases 1 \My_Path\Data\Scripts 1 \My_Path\Database Server\Extensions 1 Bonjour installation: 1 Windows: Do not uninstall or disable Bonjour for Windows if FileMaker Server is installed on your

computer.

1 Mac OS: If Bonjour is not installed and enabled, then you cannot install FileMaker Server. 1 On Windows 64-bit editions, FileMaker Server requires the 32-bit version of Java 6 Update 16. Even if
the 64-bit version of Java 5 or Java 6 is already installed, the FileMaker Server installer requires you to install the 32-bit version of Java 6 Update 16.
1 On Windows, do not uninstall the Microsoft Visual C++ 2008 Redistributable Package (x86) if

To create a scheduled task for backing up databases, choose the Admin Console Schedules pane, select Create a Schedule from the Actions menu, and click Perform Action. Then, choose Verify Databases, and specify how often you want to verify the databases.
Hosting databases connected to ODBC data sources
FileMaker Server can host FileMaker Pro databases that are connected to external SQL data sources. In FileMaker Pro, you can work with the ODBC data in much the same way that you work with data in a FileMaker file. For example, you can add, change, delete, and search external data interactively. To host databases connected to ODBC data sources after the ODBC data source has been defined in FileMaker Pro, on the master machine create the DSNs (Data Source Names) required by each database. To create the DSN, choose Control Panel > Administrative Tools > Data Sources (ODBC) (Windows) or ODBC Administrator (Mac OS). See FileMaker Server Help for more information on using ODBC and JDBC with FileMaker Server and accessing external ODBC data sources. Note You do not need to enable the OBDC/JDBC data source feature of FileMaker Server Advanced to host FileMaker Pro databases that access an external SQL data source via ODBC.
Enabling ODBC data source single sign-on (Windows only)
If you work with FileMaker Pro databases hosted by FileMaker Server that access ODBC data from Microsoft SQL Server, you can configure the master machine to enable single sign-on (SSO). ODBC data source single sign-on allows FileMaker Pro clients to use their Windows-authenticated login credentials and permissions to access Microsoft SQL Server without logging in.
To enable ODBC data source single sign-on with FileMaker Server, you must configure the FileMaker Server service on the master machine to log in using the privileged user account. That is, this user account must have the Impersonate a client after authentication privilege enabled, and the account must be an Administrator account and configured in Windows Active Directory on the network. Important Before you can enable ODBC data source single sign-on, your Windows domain administrator must:
1 Configure the Account is trusted for delegation security setting for each users Windows user account. 1 Configure the Trust this user for delegation and Use Kerberos only security settings for the privileged user
account on the master machine.
1 Enable the Impersonate a client after authentication privilege for the privileged user account on the

master machine.

1 Configure the ODBC DSN to use Windows authentication on the master machine. 1 Configure Microsoft SQL Server to use Windows authentication.
To enable ODBC data source single sign-on on the master machine: 1. Choose Control Panel > Administrative Tools > Services > FileMaker Server, then choose Action > Properties. 2. On the Log On tab, choose This account. 3. For This account, enter the privileged user account on the master machine, then click OK. 4. Choose Control Panel > Administrative Tools > Local Security Policy > Local Policies > User Rights Assignments > Act as part of the operation system. 5. On the Local Security Setting tab, click Add User or Group, then enter the privileged user account you specified earlier for This account. 6. Click OK, then restart the FileMaker Server service. Important You must also enable ODBC data source single sign-on in the FileMaker Pro databases hosted by FileMaker Server. For more information, see FileMaker Pro Help.
Running a server-side script
You can create scheduled tasks to run:
1 FileMaker scripts in databases hosted by FileMaker Server 1 system-level scripts for example, Windows batch, Perl, VBScript, and AppleScript 1 script sequences that combine a FileMaker script with an optional pre-processing system-level script and
an optional post-processing system-level script To create a scheduled task for scripts, choose the Admin Console Schedules pane, select Create a Schedule from the Actions menu, and click Perform Action. Then, choose Run Script. The Schedule assistant starts and guides you through the rest of the process.

FileMaker scripts

To schedule a FileMaker script to run, start the Schedule assistant as described above, then choose Run Script. Next, select the FileMaker Script type, then select the database that contains the script you want to run. FileMaker scripts can do simple tasks or complex tasks. For example, you can write a FileMaker script to remove duplicate records or to validate the format of phone numbers. You can schedule these scripts to run during off hours, perhaps before a daily backup. Scripts can incorporate conditional decisions (if-else statements) and perform repetitive tasks (loop statements). You use the Manage Scripts feature in FileMaker Pro to build scripts by selecting from a list of web-compatible FileMaker Pro commands, called script steps, and specifying options (if necessary). To find out if a FileMaker script step is web-compatible, see the script step reference in FileMaker Pro Help.

System-level scripts

Script files must be placed in the Scripts folder on the master machine in your FileMaker Server deployment. To schedule a system-level script to run, start the Schedule assistant as described above, then choose Run Script. Next, select the System-level Script type, then select the script file you want to run. System-level scripts can perform whatever tasks you need to perform at the operating system level on the master machine. For more information, see the documentation for the scripting language you want to use. See FileMaker Server Help for more information about running scripts as scheduled tasks.

Script Sequences

To create a script sequence, start the Schedule assistant as described above, then choose Run Script. Next, select the Script Sequence type, then select the database that contains the script you want to run. Next, select the script file you want to run, then select an optional pre-processing system-level script, an optional postprocessing system-level script, or both. See FileMaker Server Help for more information about running script sequences as scheduled tasks.
Sending messages to FileMaker Pro clients
You can send messages to notify FileMaker Pro clients about important events such as server shutdowns, database maintenance, or deadline reminders. You can send messages to:
1 all FileMaker Pro clients or selected FileMaker Pro clients connected to hosted databases 1 FileMaker Pro clients connected to any database or selected databases hosted by FileMaker Server 1 FileMaker Pro clients as a scheduled task
To send messages to FileMaker Pro clients, choose the Admin Console Clients pane and select one or more clients from the list. Select Send Message or Send Message to All Clients from the Actions menu, and click Perform Action to enter the message. To send messages to FileMaker Pro clients connected to hosted databases, choose the Admin Console Databases pane and select a folder or database file. Select Send Message (for database files only) or Send Message to all from the Actions menu, and click Perform Action to enter the message. To create a scheduled task for sending messages, choose the Admin Console Schedules pane, select Create a Schedule from the Actions menu, and click Perform Action. Then, select Send Message, create the message, and set up a schedule to deliver it.

You can upgrade an existing installation of FileMaker Server 9 or 10 to FileMaker Server 11. You can also move an existing installation of FileMaker Server 11 to other machines. If you are upgrading from a previous version of FileMaker Server 11, you must have the license key of the previous version. The installer prompts you to enter the new upgrade license key and the previous license key. To upgrade the license of an existing deployment of FileMaker Server 11 to FileMaker Server 11 Advanced, see Upgrading the FileMaker Server 11 license on page 10. The steps listed below outline the process. See the remaining sections for information about each step. Important You must perform the steps in the order they are presented. 1. If you are using FileMaker Server 11, save the settings for your schedules and administrator groups. 2. Note your existing FileMaker Server settings. 3. Stop FileMaker Server. 4. Make a copy of any database files, shell script files, and plug-ins you used with FileMaker Server. 5. Uninstall FileMaker Server. 6. Install FileMaker Server 11. 7. Move any database files, script files, and plug-ins you used with the previous version of FileMaker Server to the proper folders within the FileMaker Server 11 folder structure. 8. If you are using FileMaker Server 11, load the settings for your schedules and administrator groups. 9. Configure FileMaker Server.
Step 1. Save your schedules and administrator groups
Note This step applies to FileMaker Server 11 only. If you need to reinstall FileMaker Server 11 on the same machine or move the installation to another machine, you can save the settings for your schedules and administrator groups that are configured in the current installation. After you install FileMaker Server 11, you can then load the settings for your schedules and administrator groups to instantly configure them in the new installation. 1. Start the FileMaker Server 11 Admin Console. See Starting Admin Console on page 49. 2. Choose Server menu > Save Schedules and Groups. 3. Click Browse, navigate to the folder where you want to save the Schedules and Groups settings file, and click Open.
4. Click Save to save the Schedules and Groups settings file, then click OK. Note The default name of the Schedules and Groups settings file is fms11_settings.xml. You cannot specify a different name when you save the file in Admin Console. If you prefer, you can change the filename using your operating system tools after you save the file.
Step 2. Note your FileMaker Server settings
Make a note of your existing FileMaker Server settings because you will have to re-enter your settings manually later. Some examples are:
1 Note the name of your FileMaker Server installation (the name users see in the Open Remote dialog box

in FileMaker Pro).

1 If you are using FileMaker Server 9 or 10, note the settings for schedules for backing up databases,

Mac OS To uninstall FileMaker Server: 1. Insert the CD into the drive or follow your electronic download instructions. 2. Double-click the FileMaker Server 11 installation icon.
3. Enter your Mac OS user name and password. 4. Read the Before You Begin information and click Continue (Mac OS). 5. Review and accept the end user license agreement. 6. For Installation Type, choose Uninstall and click Next. 7. Click Yes to confirm that you want to uninstall FileMaker Server 11. Some files and folders cannot be removed. 8. Click OK. 9. Restart the machine after uninstalling FileMaker Server 11.
Step 6. Install FileMaker Server 11
To install FileMaker Server, you must use an account with administrative privileges. To deploy on a single machine, see chapter 1, Installation quick start. To deploy across multiple machines, see chapter 2, Deploying FileMaker Server across multiple machines. Note If you enter an upgrade license key in the Personalization dialog box, the Upgrade dialog box prompts you for a valid license key from the previous version of the product. The FileMaker Server installer and the Deployment assistant prompts you for some of the settings that you noted in Step 2. Note your FileMaker Server settings on page 56.
Step 7. Move files to the proper location
Move the script files and plug-ins you used with the previous version of FileMaker Server to the proper folders within the FileMaker Server 11 folder structure. See Step 4. Make a copy of databases, scripts, and plug-ins on page 57. Note You can use the Upload Database assistant to transfer your existing databases to your new FileMaker Server deployment. See Uploading a database on page 50. To transfer your database files manually, see FileMaker Server Help. Important If you are using FileMaker Server 11 and you want to transfer settings by loading the Schedules and Groups settings file, make sure you have created a folder structure in the new FileMaker Server installation that is identical to the source server installation. Copy the databases, scripts, and other solution files from the source installation to the new FileMaker Server installation, and set the appropriate permissions on Mac OS. For more information, see FileMaker Server Help.
Step 8. Load your schedules and administrator groups
Note This step applies to FileMaker Server 11 only. If you are using FileMaker Server 11, you can load the Schedules and Groups settings file you saved earlier. See Step 1. Save your schedules and administrator groups on page 55. Important Whenever you load a Schedules and Groups settings file, all existing schedules and administrator groups settings in the new FileMaker Server installation are deleted and replaced by the settings in the Schedules and Groups settings file. You cannot merge the schedules and administrator groups settings from multiple FileMaker Servers. 1. In Admin Console for the new FileMaker Server 11 installation, choose Server menu > Load Schedules and Groups. 2. Click Browse and navigate to the folder where you saved the Schedules and Groups settings file. The default filename is fms11_settings.xml, unless you changed the filename using your operating system tools. 3. Select the Schedules and Groups settings file and click Open. 4. Click Load to load the Schedules and Groups settings file into FileMaker Server. 5. Click Yes to replace all of the existing schedules and administrator groups in the new FileMaker Server installation with the schedules and administrator groups from the source installation. 6. Do one of the following:

1 Enable Anonymous access. 1 Enable Basic Authentication along with any of the other authentication methods under Authenticated

access. 5. Click OK.

Product documentation
Using FileMaker Server documentation
The following manuals are included:
1 FileMaker Server Getting Started Guide (this manual): describes how to deploy FileMaker Server 11 and
how to move from FileMaker Server 9 or 10
1 FileMaker Server Custom Web Publishing with PHP: describes how to develop Custom Web Publishing
solutions using PHP on FileMaker Server
1 FileMaker Server Custom Web Publishing with XML and XSLT: describes how to develop Custom Web
Publishing solutions using XML or XSLT on FileMaker Server
1 FileMaker Server Guide to Updating Plug-ins: describes how FileMaker Server Auto Update can
download the most current plug-in to FileMaker Pro database client computers The following manuals describe features available only in FileMaker Server Advanced:
1 FileMaker Instant Web Publishing Guide: describes how to make FileMaker Pro databases accessible to
web browser users over an intranet or the Internet
1 FileMaker ODBC and JDBC Guide: describes concepts and details to help you share FileMaker data with
other applications using ODBC and JDBC Online Help is accessible from FileMaker Server Admin Console, Help menu > FileMaker Server Help.
Where to find PDF documentation
To access PDFs of FileMaker Server documentation:
1 In the Admin Console, choose Help menu > FileMaker Server Product Documentation. 1 Click the links in the FileMaker Server Admin Console Start Page. 1 On the web, go to www.filemaker.com/documentation.
To view the PDF files, you need a PDF reader. In Mac OS X, you can use either the built-in Preview application or Adobe Reader. Windows users need Adobe Reader. If you do not have Adobe Reader, you can download it from the Adobe website at www.adobe.com. All of the PDF files use the tagged Portable Document Format (PDF). Tagged PDF files work with assistive technology such as the screen readers JAWS and Window-Eyes for Windows. For more information about tagged PDF files, see the Adobe website at www.adobe.com.
Registration and customer support
Please take the time to register your product during installation. By registering your software, you may be eligible for upgrade offers and other customer services. Follow the prompts to provide your registration, product, and additional information. You can register by choosing Help menu > Register Now in FileMaker Server Admin Console. You must register with a valid license key. For information about Technical Support and Customer Assistance, visit www.filemaker.com/intl. To access resources on the FileMaker website such as ready-made solutions and the FileMaker Knowledge Base, open the FileMaker Server Admin Console Start Page and click Customer Support Services. If you do not have access to the web, please refer to the FileMaker Service Directory that comes with your software.

Check for software updates
From the FileMaker Server Admin Console Start Page, you can check for software updates. In the Software Update section, click Check Now. If an update is available, you can click a link to download the update.
accounts Admin Console login 15, 31 IIS and Basic Authentication 64 web server 65 Windows user accounts 65 Admin Console described 22, 47 Overview pane 20, 38 passwords 15, 31 requirements 9 shortcuts, creating 50 starting 49 troubleshooting deployment 44 user names 15, 31 admin_console_webstart.jnlp 44, 49 administrators, contact information 15, 32 alerts, sending to clients 53 anti-virus software 12 Apache web server 63 assistive technology 67 authentication setting up (Windows IIS) 64 web server 64 Custom Web Publishing enabling 17, 34 testing 41 customer support 68
data sources FileMaker files as 16, 32 ODBC files as 51 data, synchronizing 51 Database Server described 22 stopping 56 databases. See files deploying FileMaker Server multiple machine 21, 3138 single machine 1519 testing deployment 41 deployment alternatives 21 multiple machines master machine 28 worker machines 26 type, selecting 34 Deployment assistant 15, 31 DSNs for files connected to ODBC data sources 51
backing up files 50 backups, for migration 57 Basic Authentication 65 Bonjour, requirements 12, 26, 29 browser support 9
electronic documentation 67 email notifications 54 enabling Custom Web Publishing 17, 34 Instant Web Publishing 17, 34 ODBC and JDBC 16, 32 PHP 17, 34 web publishing 16, 33 XML 17, 34 XSLT 17, 34
client applications 9 clients maximum number of 9 sending messages to 53 clone databases 51 computers master and workers 22 remote 44 configuring web server 63
FileMaker API for PHP 17, 34 FileMaker Pro, testing connection to files 41 FileMaker scripts 53 FileMaker Server administering 47 client applications supported 9 components, described 21 deploying on multiple machines 21 Deployment assistant 15, 31 described 7 documentation 67 installing on multiple machines 2538 installing on one machine 1120 requirements 7 setting up email notifications 54 Start Page 31 testing deployment 41 toolbar 48 uninstalling, in Mac OS 59 uninstalling, in Windows 58 updates 68 updating to FileMaker Server Advanced 10 upgrading from a previous version 55 FileMaker Server Admin Console. See Admin Console FileMaker Server Advanced, updating to 10 FileMaker Server Start Page 31 files backing up 50 clone databases 51 DSNs for ODBC data sources 51 maximum number of 9 synchronizing data 51 testing database deployment 41 uploading 50 verifying 51 firewalls 50 configuring 25 FMServer_Sample.fpfolders for backups 50 uploading files to 50