Uploading database files manually

You can manually copy FileMaker Pro database files to FileMaker Server; however, you must do the following:

  • Place the database files in the proper location. FileMaker Server hosts database files in a default database folder (Databases), a secure database folder (Secure), and an additional database folder. The default database folder and the additional database folder support hosting files in subfolders one level down. You can select or change folders on the Configuration > Folders tab. See Database and backup folder settings.

  • If your database uses container fields that store objects externally, then place the externally stored container field objects in the proper location. If you created folders for your database, then make sure you create the correct folders on the server and copy the field objects into those folder.

  • macOS (FileMaker Server only) and Linux: Change group ownership for database files and container field objects.

    Important  If you need to move, copy, or rename a hosted file, be sure to close it first. A database file must be closed before you can manually move, copy, or rename the hosted file. You can close the open databases on the Databases page. See Closing hosted files.

Notes 

  • The Database Server checks whether a database has some form of sharing enabled when the database is opened. If no sharing is enabled, the Database Server automatically enables sharing via FileMaker Network (extended privilege fmapp) for the Full Access privilege set. If you enable only the fmwebdirect extended privilege for sharing via FileMaker WebDirect and don't enable fmapp, then users can't access the file with FileMaker Pro.

  • To remove databases that are already hosted, see Removing hosted files.

  • Database filenames must be unique for the entire server regardless of the folder or subfolder.

  • For security reasons, the databases you manually upload must not have a Guest account using the Full Access privilege set, a Full Access account with an empty password, or a Full Access account with the password stored in the database using the File Options dialog box Log in using option. Database files with these types of accounts are insecure.

    If you need to host insecure database files, use the CLI command fmsadmin set serverconfig securefilesonly=false.

    Restart FileMaker Server for this configuration setting change to take effect. See Using the command line interface.

    This command will allow insecure database files in the default database folder and the additional database folder; it will not allow insecure database files in the secure database folder. If you have not changed this default behavior, then FileMaker Server will not let you open database files with these types of insecure accounts. (If you manually upload insecure database files to the secure database folder, they will not open—even if you change this default behavior.)

Place database files in the proper location

Place the FileMaker Pro database files that you want FileMaker Server to open—or shortcuts (FileMaker Server only, Windows) or aliases (FileMaker Server only, macOS) to those files—in one of the following folders.

Folder

Folder location

The default database folder

A folder for hosting encrypted and unencrypted files. See Database and backup folder settings.

The secure database folder

A folder for hosting encrypted database files. See Database and backup folder settings.

An additional database folder

An additional database folder that you can specify if you want. See Setting up an additional database folder.

Place the externally stored container field objects in the proper location

If your database uses container fields that store objects externally, you must also place the externally stored container field objects in the proper location when you manually upload the database.

  1. In the folder where you placed the database, create a folder named RC_Data_FMS, if it doesn't already exist.

  2. In the RC_Data_FMS, create a folder with a name that matches the name of your database file. For example, if your database file is named Customers, then create a folder named Customers: RC_Data_FMS\Customers.

  3. Place the externally stored objects in the new folder you created.

    For example, your database file, Customers.fmp12, has a table named Rewards with a container field named Photo. Photo is a managed container that stores externally and uses open storage. By default, FileMaker Pro creates the following folder structure as the base directory for your externally stored objects:

    Files\Customers\Rewards\Photo

    Note  To see the base directory for your container fields, in FileMaker Pro, choose File menu > Manage > Containers and click Storage.

    If your database file is encrypted, choose the Options for Field dialog box Secure storage option for the container fields to ensure the security of the data. (Selecting Open storage for the container fields doesn't encrypt the data.) See Claris Pro and FileMaker Pro Help.

    Copy the folders for your base directory (with the contents of the folders) into the RC_Data_FMS\Customers folder on the server, giving you this folder structure:

    RC_Data_FMS\Customers\Files\Customers\Rewards\Photo

    Place the externally stored objects into this folder on the server.

Note  When databases are hosted on FileMaker Server, multiple databases can't share a common folder of container objects. The container objects for each database need to be in a folder identified by that database's name. The information about the container folders is stored with the database. See Setting up an additional database folder.

Change group ownership for files (macOS and Linux)

For files that will be shared from macOS (FileMaker Server only) or Linux, change the files (database files and container field objects) to belong to the fmsadmin (FileMaker Server only) or claris (Claris Server only) group. To edit databases shared from macOS or Linux, files should also have group read and write access enabled.

See Users, groups, and permissions (FileMaker Server only, macOS).

Note  Any macOS or Linux subfolders containing databases, external container field objects, backups, script files, or plug-in files must also be readable and executable by the fmsadmin or claris group. Database and backup folders need to be writable by the fmsadmin or claris group for backups and uploads. Some plug-in files or scripts that use preferences or folders of additional files may require write permission to those files or folders.

Related topics