eljefejb

I did get the fmp:// scheme to work using the Open URL script step. Wasn't even aware of that one. I thought Insert from URL was the only way to use cURL. Turned out not to be the behavior I was after, though. The Data API is just the ticket. Took a bit to get the hang of, but it works! Thank you for your help!

Hi comment, The URL call looks like it would do what I want, but I can't seem to make it go. I keep getting Error 5: "Command is invalid (for example, a Set Field script step does not have a calculation specified)" My script step looks like: Insert from URL [With dialog: Off ; Target: $result ; "fmp://my.server.name/HelloTest?script=SayHello" ; Do not automatically encode URL ] I started with my intended final use, and kept simplifying things when it didn't work. I have made a simple file (HelloTest) that uses the Guest account, to eliminate possible hangups with login, etc. I made sure to add the "fmurlscript" extended privilege. The "SayHello" script just shows a custom dialog. I tried using the IP address instead of DNS name of the server, with and without the script parameter, etc. Still only getting Error Code 5. I found a Google result that said Error 5 used to be a problem with the Insert from URL script step, but that it was fixed in FMS 21.1.1. I am running FMS 21.1.1.40, so that shouldn't be a problem. Also, I have several other places where I use Insert from URL to call an API, and they work just fine. Maybe it's the "fmp://" protocol? FMPro is not installed on the server, so maybe that protocol isn't registered and causing it to barf. But it should work when trying to debug locally . . . 🤷‍♂️

Hello, I'm creating a "mailer" file to send HTML emails from FileMaker without the need for a third-party plugin. The idea is that whenever another FM app needs to send an email, it can just ball up some JSON and call the "Send Mail" script from the central mailer file with the JSON as the script parameter. I've read that if the same credential set exists for the logged-in user in both files, opening the secondary file will be transparent. However, if not, the user is presented with a login dialog. Since the "Open File" script step is not supported on WebDirect, I can't just detect if the file is open (via the DatabaseNames function) and have the script log in. Using PSOS still shows the dialog. Is there any way to run a script from another FM file without the user seeing a login dialog and without needing to duplicate user accounts in the second file?

Today I moved a file from FMS16 (macOS) to FMS21 (Ubuntu). I first closed the file on the old server, then used scp to move it to the new server. Then I moved it into the FMS databases folder and did sudo chown fmserver:fmsadmin on the file before opening it using the admin console. When I accessed the file via WebDirect, it all looked good, except that the latest 10 records or so were not present. If I access the original file on the old server, everything is fine. Any ideas?

I am also seeing that field borders won't appear in the generated PDF. Lines and boxes drawn as separate objects will, but not field borders. Anyone else seeing the same?

Migrated a file to FMS 21.1.1.40 yesterday, and one of our users alerted me that printing in WebDirect was only generating a blank page without text. I found that this is because the layout uses Helvetica font, which is not installed by Ubuntu (server is on 22.04LTS). It looks like the server should have a substitute: $ fc-match Helvetica NimbusSans-Regular.otf: "Nimbus Sans" "Regular" Is it FileMaker Server that isn't doing something right, maybe?

Success! If you inspect the file icons on the WebDirect launch page using the browser tools, it looks like you'd have to monkey with Java code in order to override anything. However, realizing that you can get to a file at the URL "/fmi/webd/DBNAME", I thought FM must be simply issuing an HTTP request in their Java, and wondered if a simple Apache redirect might do it. Turns out, it works! Here's what I did -- Old server: Mac Mini running macOS Sierra (10.12.6), FileMaker Server 16 New server: Ubuntu 22 server, FileMaker Server 21.1.1.40 On the old server, edit the file /Library/FileMaker Server/HTTPServer/conf/httpd.conf and at the end of the file add: #Redirect to new server <Location "/fmi/webd/myFMDB"> Redirect "https://newserver/fmi/webd/myFMDB?homeurl=https://oldserver/fmi/webd" </Location> The "homeurl" parameter in the redirect URL makes it so that the user will come back to the original WebD launch page when they close the file on the new server. Other than the URL in the browser, the user shouldn't notice a difference. And if you wanted to do a fancier redirect with URL rewriting, you could do a pass-thru of the original URL. In order to get the "homeurl" feature to work, you have to edit a file on the new server. Edit the file /opt/FileMaker/FileMaker Server/Web Publishing/conf/jwpc_prefs.xml and update these values: <parameter name="homeurlenabled">yes</parameter> <parameter name="customhomeurl">https://oldserver</parameter> Enter only the domain for the "customhomeurl" parameter! This tripped me up for a while. I had entered "https://oldserver/fmi/webd", but it wouldn't work. Gotta read all the notes! See this page from Claris. Now that that's done (don't forget to restart WPE on the new server with "fmsadmin restart wpe") you can bounce Apache on the old server. Use this to avoid disrupting currently connected users: sudo /Library/FileMaker\ Server/HTTPServer/bin/httpdctl graceful Your redirect should now be working! One other thing that tripped me up - if your FM file has spaces in the name, don't use the %20 code in your Location tag in the Apache conf. Just do: <Location "/fmi/webd/My File With Spaces"> Hope this helps somebody!

When I saw FMS complain about needing JDK 17, I assumed that meant a minimum version of 17, so I installed OpenJDK 23.0.2. Just completed an install of FMS 21.1.40 (macOS) and the admin console still complains about JDE 17. Do you really have to have version 17, and ONLY version 17? What's the reason for that? Seems kind of silly...

Hello, We use the default WebDirect Launch Center page for our apps. (FMS 16) I'm wondering if there might be a way to override the destination of individual items. I'm working on updating/migrating to a new server, and would like to do it one file at a time, as I'm able to, without the users having to do anything different. For example, users go to the WebD page on ServerA, click the icon for File1, and have the browser actually go to ServerB/fmi/webd/NewFile. Is this possible, aside from creating a custom home page (which would throw off the users)?

Are you using the FileMaker default SSL cert, by any chance?

I downloaded the most recent installer package (21.0.2.202) and ran the installer. Everything worked nicely. Running `ps -A | grep fm` showed lines for "fmshelper", "fmsib", "fmserverd", and "fmsased". Apache was also running. To see if it would come back up after a power glitch, I did a `sudo reboot now`. The FM server did not come back up. I thought I must need to manually set them up using `systemctl enable`, but the system seems unable to find the services. If I try `fmsadmin start server`, the command returns `Error: 10007 (Requested object does not exist)`. Any ideas? The FileMaker installation documentation simply ends after telling you to run `ps -A` to verify that the installer worked.

Wow, no posts in this category yet. Surprising. I've been playing with installing FMS24 on Ubuntu 22.04.3. I first tried an upgrade on top of the existing FMS23 install, because our IT guy said we should learn if we could. The install seemed to go fine. The admin console launched and things seemed fine. I saw something about rebooting to make the settings persist, so I did that, but FMS did not come back up with the system. I then tried doing a `sudo apt remove filemaker-server` and a fresh install, but experience the same behavior after reboot. I don't see any instructions about making FMS start on boot, so I thought the installer was taking care of all that. Am I missing something? I should mention that the server is on an internal network with no access to the Internet.

Cool. I thought I had heard/seen something about Server 2023 only being compatible back to 19.4... Looks like I'll still have to get a newer Mac in order to run Pro, though. Doh! Thanks!

Can Server 2023 open FMP16 files without first needing to open and resave those files in an in-between version of FMP, like 19?

Ah, I think I understand, now! Thank you for the enlightenment!