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
The first step is to determine where to install the plugin.
FileMaker Pro: If you are running FileMaker Pro, then you will need to install the plugin for FileMaker Pro. If your database is hosted on FileMaker Server AND uses the "Perform Script on Server" to run scripts on the server that call plugin functions, then you will also need to install the plugin on the server.
FileMaker Server: If your database utilizes the "Perform Script on Server" script step to run scripts that call plugin functions (from FileMaker Pro, Data API, or Web Direct), or if you intend to use the plugin in a scheduled script, you will need to install the plugin for FileMaker Server
Web Direct: If users will be accessing the database through Web Direct then the plugin needs to be installed into the FileMaker Server Web Publishing Engine.
FIleMaker Go 360Works plugins cannot be installed on iOS, but you can install them on FileMaker Server and then use "Perform Script on Server" to run them.
FileMaker Pro Installation
Step 1: Unzip the downloaded .zip file. Leave this Finder(Mac) or File Explorer(Windows) window open
Step 2: Open FileMaker Pro
Step 3: Open FileMaker Pro Preferences.
On Mac this is under the FileMaker Pro menu.
On Windows this is in the Edit Menu
Step 4: In the Preferences window, click on the plugin tab and then click on the button that says "Reveal plug-in folder". This will open another Finder(Mac) or File Explorer(Windows) to the FileMaker Pro installation location
Step 5: On the window from Step 1 navigate into the folder that corresponds with your operating system. If you are using a Mac go into the "MAC" folder, a Windows go into the "WIN" folder.
For Mac: Copy/paste or drag/drop the .fmplugin file that is inside the MAC folder into the folder that was opened in Step 4
For Windows: There will be two files inside the WIN folder. The file that has the extension of .fmx is 32-bit. The file that has the extension .fmx64 is 64-bit. If you do not see the file extensions, right click on the file and select Properties. The extension will be shown next to "Type of File". Once you have determined the correct file copy/paste or drag/drop it into the folder that was opened in Step 4.
Step 6 Quit and restart FileMaker Pro
Step 7 Check to make sure that the plugin is installed and enabled. You can do so by opening FileMaker Preferences and going to the plugins tab and making sure the plugin is listed there and is checked to indicate it is enabled. See the screen shot in step 3 that shows 360Works plugins installed with a check mark to show they are enabled. If the plugin is not listed there, then it is not installed correctly. If it is listed there and not checked as enabled, try to check it to enable it. If you get an error when trying to enable it, please contact us by sending an email to email@example.com.
FileMaker Server and WebDirect/Web Publishing Installation
Installation for FileMaker Server and WebDirect/Web Publishing can be done via script or manually. Make sure you have enabled the "FileMaker Script Engine Plug-ins" for FileMaker Server and/or the "Web Publishing Plug-ins" option in the admin console
Manual installation: Place the appropriate plugin file for your operating system in the corresponding installation location.If you have a Windows machine this needs to be the 64-bit plugin. Please see the Plug-in Installation Locations page for default installation locations. After installing a plug-in, restart the FileMaker Server Scripting Engine (FMSE) or for Web Direct, the Web Publishing Engine. This can be done via Terminal or CMD/PowerShell by using the FMSadmin utility. The command to restart the FMSE is:
fmsadmin restart fmse -y
The command to restart the WPE is:
fmsadmin restart wpe -y
You can confirm that the plugin is installed and enabled in the FileMaker Server Admin console. If you do not see the plugin listed there, try restarting the Admin server with the command:
fmsadmin restart adminserver -y
If you do not see the plugin listed or it will not enable, please contact support at firstname.lastname@example.org
NOTE:Web Publishing Engine plugins do not show up in the admin console. You can confirm that they are installed by calling the Get(InstalledFMPlugins) script step from a Web Direct context.
Installation via Script: Make sure you have turned on the "Install Plug-in File Script Step" for Server plugins and/or Web Publishing plugins. Create a new file with a container on a layout. Insert the appropriate plug-in for your operating system into a container field, and write a script(installation script) that calls the script step "Install Plug-in File" and reference the container field. If you want to install for FileMaker Server, create another script that calls the installation script via the "Perform Script on Server" (PSOS) script step. For Web Direct, put a button on the layout that calls the installation script. Host this file on FileMaker Server and then access it through FileMaker Pro or through Web Direct, whichever is appropriate for you install. For FMS, call the PSOS script. For Web Direct, click the button that runs the install script.
If you have any difficulties getting the plugins installed please send us an email to email@example.com
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 with this fmp URL fmp://autoupdate.360works.com/AutoUpdate360Works