Search the Community
Showing results for tags 'web server'.
Found 4 results
Updated script triggering plug-in for FileMaker Pro 17 adds script triggering via a URL. Alphen aan den Rijn, the Netherlands, April 23, 2019–Troi today announced the immediate availability of Troi Activator Plug-in 5.0 for FileMaker Pro 17. What is Troi Activator Plug-in? Troi Activator Plug-in is a very powerful tool for triggering scripts remotely. All from within FileMaker you can: trigger a FileMaker script on a different computer (remotely) trigger a FileMaker script over internet use the built-in security to prevent unauthorized triggering send a number (e.g. a record ID) and a long text with the trigger start and stop listening for remote trigger messages with one script step communicate with databases in different FileMaker versions or even runtimes Except from remote triggering you can also use the Activator Plug-in for: triggering a script on a specified date and time scheduling events which trigger any script you want running a script from any FileMaker calculation, for example a tooltip calculation validating fields on exiting a record with a custom script suited to your specific needs What is new in version 5.0? Troi Activator Plug-in 5.0 is compatible with FileMaker 17 and has the following new functionality: Tested and made compatible with FileMaker Pro 17.0.4. Added script triggering via a URL (using the GET HTTP method) on macOS and Windows. You can now trigger a script with a URL like this: http://www.example.com:54242/triggerscript.html?yourText=someText You can also specify an (optional) password in the URL and add whether you want to wait for a response. In the triggered script you can specify the response text with the new Actr_SetHTTPResponse function or Set HTTP Response script step. The Activator Web Server functionality, including the Image Upload Server functionality, is now also available on Windows. (Windows) Added code signing to the plug-in for Windows. (On macOS code signing was already added in version 4.5). The plug-in now indicates if an external script step is compatible with a product. The step is shown in grey if it is incompatible for that product (for example for iOS) in the script editing pane (center) and the script steps pane (right). (macOS) Prepared the plug-in for notarization: the plug-in can now be added to a runtime, to create a hardened FileMaker runtime app which can be notarized by Apple. Notarization gives users more confidence, as the runtime has been checked by Apple for malicious components. Version 5.0 also has the following changes and improvements: IMPORTANT (macOS only) The minimum supported FileMaker version is now FileMaker Pro 14. Also the minimum supported Mac OS version is now OS X 10.9 (Mavericks). You can keep using v4.5.1 for older versions of FileMaker Pro or Mac OS X. (macOS) The plug-in no longer has the 32-bit code included. Updated the EasyInstallTroiPlugins.fmp12 file, it can show additional error information from Get(LastExternalErrorDetail) when it is available. The EasyInstallTroiPlugins.fmp12 file can also run a test registration script for a plug-in after you have installed it on FileMaker Server. Updated the example files for FileMaker Pro Advanced 17 and made small corrections to the user guide. Pricing & Availability A fully functional demo version of Troi Activator Plug-in 5.0 is available on the Activator Plug-in page. Licenses cost US$ 89 per user. Details on developer licenses and multi-user discounts can be found on the Activator Plug-in page. You can order licenses from our shop. Upgrade information Version 5.0 needs a new registration. The upgrade is free for users who bought a license for Troi Activator Plug-in on or after September 4, 2017. Eligible users will be sent a new registration. Contact us if you have not received yours after April 26, 2019. Upgrades from licenses bought before September 4, 2017 are available from US$ 49 per user. Upgrade prices for other licenses can be found in the shop. You can order upgrades there.
Hope my experience can help some searching soul out there. I got there in the end. Recently, we upgraded our FMS 12 setup to 13. In the process we had to switch off Server.app's Websites function which we used to serve our php web pages through https with certificates from an external authority (Comodo). I moved our existing php files to the httpsRoot subfolder, which is where they should go. As expected, the URL in the browser was still confirmed as starting with 'https'. But the https connection now came up as untrusted by our own (and our customers'!!) browsers and our expensive green padlock had gone. The FMS 13 Getting Started Guide just says to refer to 'your web server's documentation' for installing a certificate. That is easily said, after FMS13 disabled the Server.app's with all of its convenient features! Just as others describe elsewhere in this forum, I was taken by total suprise when FMS 13 fully took over Apple's and our standard web server setup. What was the easiest way to get the certificates back? I was hoping a slight edit of some configuration file could do the trick, since the certificates were still present on the machine and I could see them in Keychain. Over 48 hours of trial and error followed, in which I tried editing the various Apache commands in FMS's http-ssl.conf file to get them to point to the existing certificates in the /etc/certificates directory. This just resulted in the web server not starting unless I reverted to the original version of the .conf file. I looked at the CERTIFICATE and CERTIFICATE IMPORT fmsadmin commands which can be issued through Terminal. They are described in the final section of the FMS Server Help documentation. It would have been really nice had the 'Getting Started Guide' mentioned their existence, since they are your ONLY workable course of action! Ocean West's post elsewhere in this forum section provides a good step by step description of the process. However, he installs a new key/certificate pair instead of trying to get one to work which is already on your server machine. It did point me in the correct direction though. I tried exporting the key/certificate files from Keychain, converting them to the requered .pem format through Terminal commands that I found. I renamed the key file as serverKey.pem, moved it to the CStore directory, and issued the CERTIFICATE IMPORT fmsadmin command providing exported .crt file as the required certificate. This raised an error stating that key and certificate did not match, and dashed my hopes. It would seem that the serverKey.pem file which you can create with the CERTIFICATE CREATE command is FMS-encrypted, and FMS will correspondingly encrypt the .crt file during import. This probably means that unencrypted files of your own are a no go, and you are stuck with using the CERTIFICATE fmsadmin command set only with a freshly generated/ordered key/certificate pair. Which is ok if you have not already bought a certificate, but our situation is that we just want the old web server setup back so we could continue where we left off. No expenditure, no waiting on external validation - which I remember was time-consuming because we had to file business documents and wait for a phone call to verify our identity. This is beacuse our customers require that we have the safer and pricier Extended Validation version. I decided to log on to our CA, Comodo, and noticed that we could replace our certificate based on a new .csr file. This brought the solution, which was so uncomplicated that Filemaker should just have documented it! Here it is: 1. Use the CERTIFICATE CREATE command first, entering your domain name. 2. Upload the text from resulting serverKey.pem file to your CA. 3. When the certificate file arrives by email, use CERTIFICATE IMPORT + the .crt file's path. Pointing to its folder as Ocean West did, did not work for us. 4. Restart your server machine, ensuring that you have first properly closed all databases and shut down the Database Server. The folks at Comodo were really helpful, not only by providing a free replacement service, but also by springing into immediate action when I raised an urgent ticket well before the official 48-hour leadtime had passed.
Hello Everybody, I'm in the process of purchasing FM Server and setting up custom web publishing via PHP or XML. As I understand there are three engines that can be on three different machines: 1. The database server (which I am about to purchase), 2.) the web publishing Engine and 3.) the web server. I am hosting our website via godaddy, so would it be possible to have the database stored on the server while I use godaddy as Web server? Even after reading the FM Server and PHP publishing manual I'm still pretty unclear of how the setup would work. Can my ( to be purchased) server function as all three engines? Thanks in advance, Andy
I just purchased Filemaker Server 11 on a hosted mac mini server running OSX 10.6.8. I am using MAMP to support my sites (there are only 3 sites hosted with minimal traffic), and everything is working well. I have my databases hosted using FMS 11 and everything is working fine. However, when I try to Enable Web Publishing, I get the same error; Unconfiguring web server... Return code = 0 Testing Web Server... Return code = false I was under the impression that I could update the launchd.plist file to redirect FMS to my custom apache install. This appears not to be the case. Has anyone ever gotten FMS 11 Web Server to run on a machine with MAMP installed? What were the steps taken?