![]() Into the FileMaker Server/Web Publishing/publishing-engine/wpc/Plugins folder. If there is no Plugins folder inside the wpc folder, then create it manually. Restart FileMaker Web Publishing, and now the plugins should be ready to go. The easiest way to test whether the plugin is working is to call the version function of the plugin, and display that on an If it shows "?", then the plugin is not working. If it shows a number, then the plugin has been installed successfully. If you are using FileMaker Server 12.0v1, you can follow the same procedure as detailed above for custom web publishing. However, in FileMaker Server 12.0v2 and later, custom web publishing now runs as a 64-bit application and requires the 64-bit version of the pluginįor Mac, the single plug-in file in the MAC directory contains both 32-bit and 64-bit versions. For Windows, look for the plug-in that has the extension. fm圆4 and use it in exclusively in custom web publishing. fmplugin to the following directory:įileMaker Server / Web Publishing / publishing-engine / cwpc / Plugins To install 64-bit plug-ins, install either the. If it does not exist, create the Plugin folder manually. Install steps for server scheduled scripts Restart FileMaker Web Publishing, and then you can then test a script that contains a plug-in and see if it returns the correct values. Drag the plugin from the MAC (.fmplugin file) or WIN (.fm圆4 file) folder into the FileMaker Server extensions folder.You do not need to do this step unless you plan on using the plugin with scheduled script triggering. On Mac OS X, this is located at /Library/FileMaker Server/Database Server/Extensions folder. Go to Configuration -> Database Server->Server Plug-ins and check the box that says 'Enable FileMaker Server to use plug-ins'(if it is not already checked), and then check the 'enabled' box for this plugin.Ĭlick the 'save' button and wait a few seconds to make sure that the 'enabled' check box stays checked.Note: On Windows you may need to change directories to where the fmsadmin utility is located in order to run this command.īy default this is located at "C:\Program Files\FileMaker\FileMaker Server\Database Server" This step is not necessary if using Powershell Restart the FileMaker Script Engine by opening Terminal (Mac) or CMD (Windows) and type the command: fmsadmin restart fmse -y.On Windows, this is at C:\Program Files\FileMaker\FileMaker Server\Database Server\Extensions. If it does not, then there was an error loading the plugin and you should contact us for help troubleshooting. You should now be able to write schedules that trigger scripts which use the plugin.ģ60Works has created an AutoUpdate helper database which makes setting up AutoUpdate much easier. This file includes pre-configured plugin files which you can place on your server, and an AutoUpdate script for each of our plugins which you can paste into your own solution. You can get the AutoUpdate360Works file hereįollow the instructions included in the file to either host your own Auto Update server or pull the files from ours. Uninstall the plugin by quitting FileMaker Pro or stopping FileMaker Server and removing the plugin file from your Extensions directory. Plugins will run in demo mode until they are registered. While running in Demo mode, the product will run for 2 hours every time you launch FileMaker /įileMaker Server / FileMaker Web Publishing Engine. ![]() ![]() The 2 hour time limit will reset every time you relaunch FileMaker. There is no expiration date whenĭemo mode stops working. There are no feature differences between the Demo version and the licensed version. ![]() Once you have purchased the plugin, you can register it with the license key.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |