Revision as of 19:25, 5 January 2016

This is a guide to installing 360Works plug-ins, though information may also apply to other FileMaker plugins.

Requirements

360Works plug-ins require a Java Runtime Environment (JRE) in order to run, where the bitness (32 bit or 64 bit) of the JRE matches the bitness of FileMaker. FileMaker Pro will prompt you on startup to download the appropriate software if it is not found on your computer, but FileMaker Server has no such prompt, and you will need to manually download a 64-bit JRE if you do not already have one. On OS X, we require the Apple-provided Java 6. For Mac OS 10.7+, you can find this here, or for Mac OS 10.6, here. On Windows, you will need a current version of Java, which you can download from Oracle.

All 360Works plugins also, of course, require one of the FileMaker platforms to function.

Platforms

Client Install

Open the .zip file from your plug-in download. Locate the appropriate plugin for your operating system inside the MAC or WIN folder. Drag the plugin to your FileMaker Extensions Folder.

Server Install

When installing a plug-in on FileMaker Server, follow a similar process. Drag the appropriate extension to FileMaker Server/Database Server/Extensions.

WPE Install

Install plug-ins on the Web Publishing Engine in order to access them from Instant Web Publishing. Installation is similar: drag the appropriate plugin to FileMaker Server/Web Publishing/publishing-engine/wpc/Plugins. If the Plug-ins folder does not exist, create one. NOTE: The Extensions folder is NOT the same as the Plugins folder in this situation.

CWP Install

If you are going to use Custom Web Publishing instead of Instant Web Publishing then install the plugin to FileMaker Server/Web Publishing/publishing-engine/cwpc/Plugins. Again, you may need to create the Plugins folder.

WebDirect Install (FMS 13+)

Install plug-ins for use with WebDirect by dragging the appropriate plugin to FileMaker Server/Web Publishing/publishing-engine/cwpc/Plugins

AutoUpdate

If you have a plug-in that needs to be installed on multiple client machines accessing FileMaker Server, you can use the Auto Update function to streamline the process. For more information on the process, visit: fmp12://autoupdate.360works.com/AutoUpdate360Works

FileMaker 12 Installation Options

New in FileMaker 12, you can install and update plug-ins from container fields. Simple insert the plug-in into a container field, and call the Install Plug-in File 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 new script step will install plug-ins to:

Windows XP: \Documents and Settings\[User Name]\Local Settings\Application Data\FileMaker\Extensions

Windows Vista / 7: \users\[User Name]\AppData\Local\FileMaker\Extensions


Mac OS: /Users/[User Name]/Library/Application Support/FileMaker/Extensions

Plug-ins found in the old location will continue to work and are overridden by plugins installed in the new location.

Install Plugin File - FileMaker Script Step

In order to use the "Install Plugin File" script step, you must be using FM12+.

1. On a layout, create a container field that will hold the appropriate plugin for your operating system ( .fmplugin for Mac, .fmx for Windows 32-bit , .fmx64 for Windows 64-bit ).
2. Place the plugin in the container field
3. Create a script that utilizes the "Install Plug In File" script step, save the script, and run it

The plugin should now be installed in the appropriate extensions folder. Where the plugin is physically installed depends on the context from which the script is executed (e.g., FileMaker Pro, FileMaker Server Scripting Engine, FileMaker Server Custom Web Publishing, FileMaker Server IWP/Web Direct). You can install several plugins at the same time by having separate containers on your layout and "Install Plugin File" script steps for each plug in in your script.