Plug-In Installation Locations

From 360Works Product Documentation Wiki
(Difference between revisions)
Jump to: navigation, search
(updated installation instructions)
(updating installation instructions)
Line 22: Line 22:
 
'''If you are running FMS 12v2 or later on a Mac machine''', you should use the .fmplugin plug-in included with the download.
 
'''If you are running FMS 12v2 or later on a Mac machine''', you should use the .fmplugin plug-in included with the download.
  
 +
When installing manually, you should stop the Web Publishing Engine, install, and start the Web Publishing Engine. This can be done in the Admin Console.
 
<pre>
 
<pre>
 
FileMaker Server/Web Publishing/publishing-engine/cwpc/Plugins
 
FileMaker Server/Web Publishing/publishing-engine/cwpc/Plugins

Revision as of 15:56, 9 December 2014

There are four ways that you can install FileMaker plugins, depending on where you need them to run.

Contents

FileMaker Pro (Windows or Mac)

This is the standard place that you're used to putting plugins. These plugins will run in the FileMaker Pro client software.

Mac 
/Users/[username]/Library/Application Support/Filemaker/Extensions 
Windows 
C:\Users\[username]\AppData\Local\FileMaker\Extensions

FileMaker Web Publishing Engine (Windows or Mac)

You would install plugins on the Web Publishing Engine in order to invoke them from Instant Web Publishing. On FileMaker Server 9 (and later versions), the Plugins folder may not exist - just create it and put the plugin there. Do not confuse this folder with the already existing "Extensions" folder. All 360Works plugins will run in the Web Publishing Engine. When installing manually, you should stop the Web Publishing Engine, install, and start the Web Publishing Engine. This can be done in the Admin Console.

FileMaker Server/Web Publishing/publishing-engine/wpc/Plugins

FileMaker Custom Web Publishing (Windows or Mac)

You would install plugins for Custom Web Publishing to use the FileMaker API for PHP if you want more control over the way your data displays in web browsers.

If you are running FMS 12v2 or later and have a 64-bit Windows machine, you should use the .fmx64 plug-in included with the download. For any other Windows installation, use the .fmx plug-in included with the download. If you are running FMS 12v2 or later on a Mac machine, you should use the .fmplugin plug-in included with the download.

When installing manually, you should stop the Web Publishing Engine, install, and start the Web Publishing Engine. This can be done in the Admin Console.

FileMaker Server/Web Publishing/publishing-engine/cwpc/Plugins

FileMaker Server (Windows or Mac)

For most plugins, the primary reason to install them on FileMaker Server (this is NOT the same thing as the Web Publishing Engine) is to use them with scheduled scripts in FileMaker Server 9 or later (this feature is not available in earlier versions of FileMaker Server). There are a few plugins, such as AdminAnywhere, which perform other functions on the server. All 360Works plugins can be used with scheduled scripts in FileMaker Server. Do not confuse the "Database Server" folder with the "Database Server x64" folder sometimes found with installations of FileMaker Server.

FileMaker Server/Database Server/Extensions

Note: 360 Works plug-ins require a 32-bit Java Runtime Environment in order to run. 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 may be required to manually download a 32-bit JRE if you do not already have one. On Windows, you will need a 32-bit version of Java 7 from Oracle. On Mac, you will need the latest Java 6 update from Apple. For Mac OS 10.6, click here. For Mac OS 10.7+, click here

Personal tools
Namespaces

Variants
Actions
Plug-in Products
Other Products
Navigation
Toolbox