Plug-In Installation
(→Platforms) |
|||
| Line 5: | Line 5: | ||
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 [http://support.apple.com/kb/dl1572 here], or for Mac OS 10.6, [http://support.apple.com/kb/dl1573 here]. On Windows, you will need a current version of Java, which you can download from [http://www.oracle.com/technetwork/java/javase/downloads/index.html Oracle]. | 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 [http://support.apple.com/kb/dl1572 here], or for Mac OS 10.6, [http://support.apple.com/kb/dl1573 here]. On Windows, you will need a current version of Java, which you can download from [http://www.oracle.com/technetwork/java/javase/downloads/index.html Oracle]. | ||
| − | All 360Works | + | All 360Works plug-ins also, of course, require one of the FileMaker platforms to function. |
| − | == | + | ==Manual Installation== |
| − | + | To manually install, place the plugin file in the proper [[Plug-In Installation Locations|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. | |
| − | == | + | ==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 [[Plug-In Installation Locations|location associated with the context]] the script is run in. Our AutoUpdate file (see below) uses this method for FileMaker 12+. | |
| − | == | + | ==AutoUpdate== |
| − | + | 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 (or at fmnet:/autoupdate11.360works.com/AutoUpdate360Works for FileMaker 11) | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Revision as of 20:07, 5 January 2016
This is a guide to installing 360Works plug-ins, though information may also apply to other FileMaker plugins.
Contents |
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 plug-ins also, of course, require one of the FileMaker platforms to function.
Manual Installation
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.
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+.
AutoUpdate
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 (or at fmnet:/autoupdate11.360works.com/AutoUpdate360Works for FileMaker 11)
