Playing with Odata
The implementation of OData at the core of how FileMaker Server returns and updates data is critical to understand in today’s interconnected world. Knowing not only that OData exists and is available, but also how it works, gives you another practical tool when interacting with your FileMaker solutions.
Because OData supports all CRUD operations and does so without the same requirements as the Data API, such as requiring a layout, it becomes essential knowledge whether you are using a server, working in a serverless environment, building a microservice, or exploring other ways of interconnecting FileMaker.
For many hesitant adopters, this can mean learning a new technology, possibly purchasing new tools, and investing time to become familiar with how everything works. In this video, I take my existing knowledge of the foundational technology embedded within FileMaker and use it to create a very simple, easy to use solution for experimenting with OData.
As we work through the topics in this video, you will learn more than how to experiment with OData. You will also gain insight into how to explore and implement other critical web technologies as well.
Comments
SAN cert vs mkcert using docker
Having troubling getting the webviewer to behave. Any thoughts, Matt.
mkcert to create the SAN
This may be an issue of FileMaker server needing all things to align correctly. When you use mkcert, you'll create a cert with the same domain that you'll be identifying your local machine as using a DNS entry.
-- Matt Petrowsky - ISO FileMaker Magazine Editor
A server with hostname could not be found
Somehow, the file does, inside our lan not find ourserver.com
but Dig ourserver.com gives rightly IP10.0.1xx.xx
also pasting https://ourserver.com/fmi/odata/v4/ works just fine in any browser.
Hints?
Inside the LAN vs the Internet
If you're not running your own DNS, where you can control what ip ourserver.com returns, then you'll have problems. If you're testing with a domain that is a legit DNS entry managed somewhere on the internet, then it should work. If you're wanting to test within a LAN, then you need to make sure whatever domain you use is something you're able to resolve.
Using dig you can get the results from various servers.
In dig results you'll see a SERVER section. This tells you the DNS server responding back. You can specifically query a given server by using the @ symbol. For example dig @1.1.1.1 google.com is querying the cloudflare servers for the google domain.
I believe (sometimes) with modern operating systems you may have issues with the /etc/hosts file. You may need to run a local DNS server. I remember at one point not being able to use the hosts file for something I was doing. The 10.0.1xx.xx network is reserved for LANs so I can only assume that using a .com to stay within a LAN won't work for you if DNS is reporting a public ip and not one from the local net. AI responses advise that browsers also use heavy caching. Maybe you need to use one of these?
mac OS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Windows
ipconfig /flushdns
-- Matt Petrowsky - ISO FileMaker Magazine Editor