Administrator’s Guide
Table Of Contents
- Preface Using the FileMakerServer documentation
- Chapter 1 Welcome to FileMakerServer 5
- Chapter 2 Installing FileMakerServer in Windows
- What you need
- Installing FileMakerServer
- Where files are stored on your hard disk
- Starting FileMakerServer (WindowsNT)
- Starting FileMakerServer (Windows2000)
- Stopping FileMakerServer (WindowsNT)
- Stopping FileMakerServer (Windows2000)
- Installing the Server Administration plug-in on a remote computer running Windows
- Enabling the Server Administration plug-in using FileMakerPro (Windows)
- Uninstalling FileMakerServer (Windows)
- Chapter 3 Installing FileMakerServer in the MacOS
- What you need
- Installing FileMakerServer
- Adjusting memory (MacOS)
- Where files are stored on your hard disk
- Starting FileMakerServer (MacOS)
- Quitting FileMakerServer (Mac OS)
- Installing the Server Administration plug-in on a remote computer running the MacOS
- Enabling the Server Administration plug-in using FileMaker Pro (MacOS)
- Chapter 4 Configuring FileMakerServer
- Using the configuration assistants (Windows)
- Opening the Properties dialog box (Windows)
- Opening the Preferences dialog box (MacOS)
- Setting the number of guests
- Allowing disconnection of idle guests
- Setting the maximum number of files
- Changing the amount of memory used by FileMakerServer
- Setting how often the cache is flushed
- Allowing single user files to be hosted
- Opening runtime solutions automatically (Windows)
- Opening runtime solutions automatically (Mac OS)
- Enabling remote administration
- Specifying a custom host name
- Maximizing performance (MacOS)
- Choosing network protocols
- Setting the preferred IP address
- Recording usage statistics and settingsizelimits
- Setting a size limit for the application log (WindowsNT)
- Setting a size limit for the application log (Windows2000)
- Setting a size limit for the Server Event Log (MacOS)
- Protecting files with a password
- How FileMakerServer behaves during system sleep
- Chapter 5 Administering FileMakerServer
- Administering FileMakerServer remotely
- Opening the Remote Administration window
- Listing hosted files and current guests remotely
- Viewing usage statistics for FileMakerServer remotely
- Hosting FileMakerPro5 files remotely
- Closing hosted files remotely
- Disconnecting guests remotely
- Viewing detailed information about hosted files and guests remotely
- Sending messages to guests remotely
- Sending messages to all guests remotely
- Administering FileMakerServer locally
- Monitoring performance locally (WindowsNT)
- Monitoring performance locally (Windows2000)
- Opening the local administration window (MacOS)
- Listing hosted files and guests locally (MacOS)
- Viewing usage statistics locally (MacOS)
- Hosting FileMaker Pro 5 files locally (MacOS)
- Closing hosted files locally (MacOS)
- Disconnecting guests locally (MacOS)
- Sending messages to guests locally (MacOS)
- Using reported events to track activities
- Recalculating the Today function inhosteddatabases
- Administering FileMakerServer remotely
- Chapter 6 Scheduling administrative tasks with FileMakerServer
- Scheduling tasks to run automatically (Windows)
- Scheduling tasks to run automatically (MacOS)
- Viewing scheduled tasks in the Schedules list (Windows)
- Viewing scheduled tasks in the Schedules window (MacOS)
- Running scheduled tasks manually
- Changing scheduled tasks
- Duplicating scheduled tasks
- Deleting scheduled tasks
- Enabling and disabling scheduled tasks
- Using the command line to automate tasks (Windows)
- Using an AppleScript to automate tasks (MacOS)
- Making sure you don’t run out of disk space
- Appendix A Technical specifications and optimization
- Appendix B Performance and usage tips
- Appendix C Event log messages and troubleshooting
- Appendix D About the TechInfo database
Configuring FileMaker Server
4-5
Mac OS: The amount of application memory specified in the
FileMaker Server Info dialog box also affects the operation of
FileMaker Server. For more information, see “Adjusting memory
(Mac OS)” on page 3-2.
To change the amount of memory FileMaker Server uses:
1. In the Properties (Windows) or Preferences (Mac OS) dialog box,
click the Files tab.
2. Enter the amount of RAM you want to allocate in the Reserve
n
MB
of RAM for database cache box.
The minimum setting is 2 MB and the maximum is 40 MB.
Important Do not specify more RAM than is physically available on
the server computer. Be sure to leave at least 16 to 32 MB (Windows)
or 24 MB (Mac OS) of physical RAM available for the operating
system.
3. Set any other options, then click OK.
You must restart FileMaker Server for the new setting to take effect.
Setting how often the cache is flushed
FileMaker Server writes (flushes) information stored in temporary
storage (the cache) to disk whenever FileMaker Server is idle, but
you can set the cache to be flushed at specific intervals. If the cache
is flushed frequently, data integrity in hosted files is improved but
performance may decline.
1. In the Properties (Windows) or Preferences (Mac OS) dialog box,
click the Files tab.
2. Select Flush cache every
n
minutes or hours.
3. Click the up or down arrow to select the time interval.
The minimum setting is 15 minutes and the maximum setting is 2
hours.
4. Set any other options, then click OK.
Allowing single user files to be hosted
For your convenience, you can set FileMaker Server to host single
user files. This setting lets you host databases without first having to
manually change them to multi-user in FileMaker Pro.
1. In the Properties (Windows) or Preferences (Mac OS) dialog box,
click the Files tab.
2. Select Allow FileMaker Server to host Single User files.
3. Set any other options, then click OK.
Opening runtime solutions automatically
(Windows)
You can have FileMaker Server automatically host runtime solution
files that have been bound using FileMaker Developer 5 and have a
custom filename extension.
About FileMaker Developer
FileMaker Developer lets database developers create and distribute
complete single user database solutions with layouts that are not
modifiable by users.
Runtime solution files typically have unique filename extensions.
For example, rather than the standard .fp5 extension, a runtime
solution file might have the extension .cm1. Registering these
runtime solution filename extensions in the FileMaker Server
Properties dialog box enables FileMaker Server to open these files
automatically when they are placed in the same folder as the
FileMaker Server application (or subfolders one level down).
To enable FileMaker Server to open runtime solution files
automatically:
1. In the Properties dialog box, click the File Types tab.