![]() Something like "/Users/cs/desktop/test.txt" on Mac and "C:\Programs\Data\test.txt" on Windows. Like if you have automated tools to monitor a dozen servers, you can of course have that software replace all those plugin files with a new version and restart the servers to have them load the new version.MBS( "Text.WriteTextFile" /* Writes a text file with the given text. This may help a lot to log what happens in a script.įinally you can automate the whole thing by installation of plugin via either FileMaker or shell scripts. With our Trace function you have a way to log plugin calls and you can add your own log entries with calls to our Log function like: When you write server scripts, it is very easy to have errors and not knowing about it. 10:58:00.334 fmsased Parameter 0 FunctionName: "Platform" 10:58:00.334 fmsased MBS Plugin call #3 with 1 parameter. 10:58:00.333 fmsased Parameter 0 FunctionName: "Version" 10:58:00.333 fmsased MBS Plugin call #2 with 1 parameter. 10:58:00.333 fmsased Parameter 0 FunctionName: "Trace" 10:58:00.333 fmsased MBS Plugin call #1 with 1 parameter. 10:58:00.332 fmsased Script "Return version" in file "Tests". Set Variable Īnd run it again, we see the log entries in the StdErrServerScripting.log file: When we add a Trace function call to the first script: If you see question marks, the plugin is not running. This helps to distinguish between running locally in FileMaker Pro and in one of the server components. You can run this and it should show the plugin version and where it is running. # Show Version on Server in file Tests (Christians-Mac.local) # Return version in file Tests (Christians-Mac.local)Įxit Script We added a test script to return the plugin version on the FileMaker Server: Those stderr files also shows our trace output to log plugin calls. MBS Plugin version 12.0.0.09 for Mac 64-bit loaded for ServerScripting 19.4. MBS Plugin version 12.0.0.09 for Mac 64-bit loaded for Data API 19.4. MBS Plugin version 12.0.0.09 for Mac 64-bit loaded for Web Direct 19.4. The fiels may show lines like this reporting the plugin version and platform: Where MBS Plugin redirects stderr to files, so you can read this separated (and not all in one stderr file). StdErrServerScripting.log StdErrDataAPI.log StdErrWeb.log To verify you can go to the Logs folder, where you should see new files: ![]() For Data API and Web Direct the plugin is not listed and already turned on. It may be enough to stop it, wait ten seconds till everything is done and then start it again.Īfter the restart we can login to the admin console and toggle on the MBS plugin for server scripting. But the problem is that FileMaker doesn't notice yet that there is a new plugin. ![]() Now we can turn on the switches for plugins. The first folder is for server scripting (scheduled and PSoS), the second folder is for WebDirect and the third one for Data API. ![]() ![]() opt/FileMaker/FileMaker Server/Web Publishing/publishing-engine/wip/Plugins opt/FileMaker/FileMaker Server/Web Publishing/publishing-engine/cwpc/Plugins opt/FileMaker/FileMaker Server/Database Server/Extensions Library/FileMaker Server/Web Publishing/publishing-engine/wip/PluginsĬ:\Program Files\FileMaker\FileMaker Server\Database Server\ExtensionsĬ:\Program Files\FileMaker\FileMaker Server\Web Publishing\publishing-engine\cwpc\PluginsĬ:\Program Files\FileMaker\FileMaker Server\Web Publishing\publishing-engine\wip\Plugins Library/FileMaker Server/Web Publishing/publishing-engine/cwpc/Plugins Library/FileMaker Server/Database Server/Extensions Let's start with a freshly installed FileMaker Server:Įverything is off and we copy the MBS.fmplugin file on macOS to this folder: Today we like to show you how to manually install the MBS FileMaker Plugin on a FileMaker Server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |