This is a guide to installing 360Works plug-ins, though information may also apply to other FileMaker plugins. If you are using a plugin released prior to May 2017 or using FileMaker 15 or below please see this page for plugin installation instructions.
As long as your system meets the recommended minimum requirements set by FileMaker then you meet the requirements to use 360Works Plugins
To manually install, place the plugin file in the proper location for the context in which you wish to use the plugin. After installing a plug-in in any location, that platform needs to be restarted.
- For FileMaker Pro, just restart the application.
- For FileMaker Server, restart the FileMaker Script Engine using the fmsadmin tool.
- For FMS Web Publishing Engine, restart the WPE itself, either through the Admin Console or the fmsadmin tool. Note that only plug-ins installed in the script engine will show up in the Admin Console; plug-ins installed in Web Publishing will not.
For FileMaker Server and Web Publishing Engine, you must enable the option to allow plug-ins. See screenshots below.
Installation via Script
In FileMaker 12+, you can install and update plug-ins from container fields using the Install Plug-In File script step. Simply insert the plug-in into a container field, and call a script including that script step. This makes it possible to deploy your solution with a plug-in bundled in that installs and registers itself with a script. You can then call the function Get (InstalledFMPlugins) to see the display name, version, and state. This script step will install plug-ins in the location associated with the context the script is run in. Our AutoUpdate file (see below) uses this method for FileMaker 12+.
For FileMaker Server and FileMaker Cloud 1 - you will need to host the solution described above on your server and then call the script that installs the plugin via the Perform Script on Server script step. It is important to call the script with the PSOS script step else the plugin will install locally in FileMaker Pro.
If you are using your plug-in to run server-side scripts (either with 'Perform Script on Server' or with scheduled scripts) with FileMaker Server, then you will need to enable the FileMaker Script Engine (FMSE) to allow the use and installation of plug-ins, as show in this screen shot:
The same applies to using plug-ins with the Web Publishing Engine, either for Web Direct or Custom Web Publishing.
We also offer an AutoUpdate file to help install or update any of our plug-ins. For more information on the process, open the database at fmnet:/autoupdate.360works.com/AutoUpdate360Works