Guide to Updating Plug-ins
Table Of Contents
- Preface Using the FileMakerServer documentation
- Chapter 1 Welcome to FileMakerServer 5.5
- Chapter 2 Installing FileMakerServer in Windows
- Chapter 3 Installing FileMakerServer in MacOS 8.6 to 9.1
- Chapter 4 Installing FileMakerServer in MacOS X
- Chapter 5 Installing FileMaker Server in Red Hat Linux
- Chapter 6 Configuring FileMakerServer (Windows and Mac OS)
- Using the configuration assistants (Windows)
- Opening the Properties dialog box (Windows)
- Opening the Preferences dialog box (MacOS 8.6 to 9.1)
- Opening the Preferences dialog (MacOSX)
- Setting the number of guests
- Allowing disconnection of idle guests
- Authenticating guest log on (Windows)
- Setting the maximum number of files
- Changing the amount of memory used by FileMakerServer
- Adjusting memory (MacOS 8.6 to 9.1)
- Setting how often the cache is flushed
- Allowing single user files to be hosted
- Allowing software updates to be downloaded automatically
- Opening runtime solutions automatically (Windows and MacOS X)
- Opening runtime solutions automatically (MacOS 8.6 to 9.1)
- Enabling remote administration
- Specifying a custom host name
- Maximizing performance (MacOS 8.6 to 9.1)
- 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 event log (MacOS)
- Using FileMaker Server with a directoryservice
- Restoring FileMaker Server defaultsettings
- Protecting files with a password
- How FileMakerServer behaves during system sleep (Windows 2000 and Mac OS)
- Chapter 7 Administering FileMakerServer (Windows and Mac OS)
- Starting FileMakerServer (WindowsNT)
- Starting FileMaker Server (Windows 2000)
- Stopping FileMakerServer (WindowsNT)
- Stopping FileMakerServer (Windows2000)
- Starting FileMakerServer (MacOS8.6to9.1)
- Quitting FileMakerServer (MacOS8.6to9.1)
- Starting FileMakerServer (MacOS X)
- Quitting FileMakerServer (Mac OS X)
- Using remote administration
- Automatically downloading the Server Administration plug-in to a remote computer
- Opening the Remote Administration window
- Listing hosted files and current guests
- Viewing usage statistics for FileMakerServer
- Hosting FileMakerPro5.x files
- Closing hosted files
- Disconnecting guests
- Viewing detailed information about hosted files andguests
- Sending messages to guests
- Sending messages to all guests
- Determining if you have exclusive access to hosteddatabases
- Using local administration (Mac OS 8.6 to 9.1 )
- Opening the local administration window (MacOS 8.6 to 9.1)
- Listing hosted files and guests (MacOS 8.6 to 9.1)
- Viewing usage statistics (MacOS 8.6 to 9.1)
- Hosting FileMaker Pro 5.x files (MacOS 8.6 to 9.1)
- Closing hosted files (MacOS 8.6 to 9.1)
- Disconnecting guests (MacOS 8.6 to 9.1)
- Sending messages to guests (MacOS 8.6 to 9.1)
- Monitoring server performance (Windows)
- Using reported events to track activities
- Recalculating the Today function inhosteddatabases
- Chapter 8 Scheduling administrative tasks (Windows and Mac OS)
- Scheduling tasks to run automatically (Windows)
- Scheduling tasks to run automatically (MacOS 8.6 to 9.1)
- Scheduling tasks to run automatically (Mac OS X)
- 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 a script to automate tasks (MacOS)
- Making sure you don’t run out of disk space during backups
- Chapter 9 Using FileMaker Server in Red Hat Linux
- Getting onscreen help with command and preference syntax
- Administering FileMaker Server
- Starting and stopping FileMaker Server automatically
- Configuring FileMaker Server
- Editing the configuration file
- Applying configuration changes
- Setting the number of guests
- Disconnecting idle guests
- Setting the maximum number of files
- Changing the amount of memory used by FileMaker Server
- Setting how often the cache is flushed
- Allowing single user files to be hosted
- Allowing software updates to be downloaded automatically
- Specifying the location of hosted files
- Specifying a user account name and group name for FileMaker Server
- Enabling remote administration in FileMaker Server
- Using the fmspasswd utility to encryptpasswords
- Specifying a custom host name
- Specifying the preferred IP address
- Opening runtime solutions automatically
- Using reported events and statistics to track activities
- Using FileMaker Server with a directoryservice
- Chapter 10 Manually installing the Server Administration pluginonaremote computer
- About the Server Administration plug-in
- Manually installing the plug-in on a remotecomputer (WindowsNT and Windows2000)
- Manually installing the plug-in on a remote computer (Windows95 or Windows 98)
- Enabling the Server Administration plug-in using FileMakerPro (Windows)
- Manually installing the Server Administration plug-in on a remote computer (MacOS)
- Enabling the Server Administration plug-in using FileMaker Pro (MacOS)
- 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
- Index
Configuring FileMaker Server (Windows and Mac OS) 6-7
FileMaker Server, virtual memory, and physical
memory requirements
FileMaker Server and the virtual memory option (available with
Mac OS 8.6 to 9.1) both use your hard disk to store temporary
information. Virtual memory provides file mapping, which can
improve the performance of FileMaker Server. If you choose to turn
on virtual memory while FileMaker Server is running, ensure that
you have enough physical memory to satisfy the requirements of
both the Mac OS and FileMaker Server so that virtual memory won’t
degrade the performance of FileMaker Server.
To determine how much physical memory you need to use
FileMaker Server with virtual memory turned on:
1. Click the desktop to switch to the Finder.
2. Choose 4 > About This Computer and note how much memory the
Mac OS is using.
3. Add this figure to the preferred amount of memory to determine
how much physical memory you need for optimal performance of
FileMaker Server with virtual memory turned on. FileMaker Server
requires 8 MB for 25 guests and 50 files.
Setting how often the cache is flushed
FileMaker Server flushes (writes) information stored in the cache
(temporary storage) 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 hours or minutes.
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.
Allowing software updates to be
downloaded automatically
You can store software updates on the server computer and allow
FileMaker Pro 5.5 guests to download these files automatically when
they open database files hosted by FileMaker Server 5.5. Examples
of files you can download automatically are plug-in files or plug-in
license files, sometimes required by FileMaker Pro databases.
When a FileMaker Pro file is hosted using FileMaker Server, any
plug-ins required by the file must exist on each guest computer used
to open the database. By allowing plug-in updates to be downloaded
automatically, you ensure that all guests have access to plug-ins
required by a database the first time they attempt to open it. In
addition, when plug-ins are changed by database developers, you can
store new versions on the server computer, so you don’t have to
update plug-ins on many individual guest computers.
For automatic file downloading to work correctly, you must place
current plug-in files and text files containing plug-in version
information in the correct location on the server computer. In
addition, guests must activate the Auto Update plug-in in the
Application preferences in FileMaker Pro 5.5 before attempting to
open hosted files that require plug-ins.