Connecting a macOS Client to a Database Server

Depending on your version of macOS, connecting a macOS client to a database server can be done in one of the two following ways:

  • On macOS clients prior to macOS 10.15 (Catalina), you can do it using the traditional method, that is by creating mount points to the network shares of your database server and your scene data servers in the root of the file system, like so: /USA_DB, /usadata000, /usadata001, etc.
  • macOS clients with macOS 10.15 (Catalina) or later: Create your mount points (USA_DB, usadata000, usadata001, etc.) in /System/Volumes/Data/mnt, and then configure shortcuts.conf to indicate their location—see About the Location of Mount Points on macOS.

The main reason for the different configuration methods is that, starting from macOS 10.15 (Catalina), macOS does not allow you to create files or directories at the root folder (/) of the filesystem.

TIP If you upgraded to macOS 10.15 (Catalina) or later from an earlier version of macOS, anything you have created in the root folder (/) was automatically moved to /Users/Shared/Relocated Items.

If your client currently has an older version of macOS, but you plan to upgrade to macOS Catalina in the future, you can immediately future-proof your setup by configuring it in the way that is compatible with macOS 10.15 (Catalina) or later, as it also works on previous versions of macOS.

If your network shares use the NFS protocol, you can create mount points for them using macOS‘s autofs system.

However, if your network shares use the Samba protocol, the only known working way of mounting them automatically on log-in is to connect to these shares manually in Finder, creating symbolic links to those shares in the appropriate locations and then, if those symlinks are not in the root folder (/) of your filesystem, configuring shortcuts.conf to indicate the location of those symlinks. Note that this method has two important limitations:

  • If your client needs to run background services, those must be launched using the Service Launcher application, rather than by the services created using Harmony‘s Configuration Assistant application.
  • If several users are configured to mount those network shares, only one of these users at a time can be logged-in. This is because if two logged-in users have the same network shares mounted via Finder or log-in items, the name of the mount points for second user to log-in will be different. One macOS, a mounted Samba share can only be accessed by the user who mounted it. Therefore, on the second logged-in user’s account, Harmony will try to access the first logged-in user’s mount points and will be denied access.