– **1604 through 16018**: The web server (Apache or IIS) sends web requests and receives responses Also note that PHP code talks to the Web Publishing Engine through its XML interface. It provides FileMaker’s web publishing capabilities, including Instant Web Publishing, and Custom Web Publishing with XML and XSLT. This component can be installed on the same machine as the database server, or the same machine as the web server, or on its own machine. >Note: The Server Admin Console is loaded form a web page, but *it runs on your computer*, not the server. – **16001**: The Server Admin Console configures the database server – **16000**: Your web browser and the Web Publishing Engine fetch server configuration information – **2399**: ODBC and JDBC clients (like Microsoft Excel) fetch data – **5353**: FileMaker Pro clients discover “local hosts” – **5003**: FileMaker Pro clients and the Web Publishing Engine retrieve data On Mac OS X, this is the fmserverd and fmshelper daemons. On windows, it’s the FileMaker Server and FileMaker Server Helper services. It’s the thing that actually serves your databases. This is the heart of your FileMaker setup. Without further ado, here are all the relevant parts, complete with firewally port information. He’ll skip right to the details below and get things working in no time flat. If you have a Drew (or Drucilla) too, just print out this article and give it to him. I had a Drew who took care of all the network configuration. > Note: When I worked at a real company, I never really had to worry about all this. Configure your firewall so that server side components can listen to their clients on the ports listed below. – **You have one network firewall running between the server computer(s) and the client computer(s).** In this case, you’re only concerned with components on the client side of things that talk to components on the server side. Any time a component on one computer listens to a component on another computer, you need to open up the right port on the first computer. – **You have a firewall running on each computer.** If this is the case, pay attention to which components are running on different computers. Open the port numbers on your list in the firewall.Ĭhances are good your firewall setup falls into one of two categories: Note which port numbers the *listening* component uses.Ĥ. Look to see if any component on your list listens to a component on the other side of a firewall. Figure out which of your components are separated by a firewall.ģ. Identify which of the components listed below are present on your network.Ģ. In order for things to work smoothly, you need to open the right ports in your firewall. On the bright side, you probably don’t have *all* these pieces, and you almost certainly don’t have a firewall between each of the parts you *do* have. This picture shows all the parts your FileMaker setup might include, along with the important lines of communication and critical port numbers. for reviewing and correcting this diagram. >Note: Thanks to Eric Jacobson at FileMaker, Inc. * () (courtesy of Informatique Direct Impact inc.) You can also download a high-quality PDF version of the diagram: Then, when you’re done, scroll back up here and carry on with the article.Ī picture’s worth a thousand words, so before we get into the details, here’s a birds-eye view of the FileMaker Server landscape: >Note: Before we dive in, if you’re wondering what all this Firewall stuff does, exactly (what *is* a port number, after all?), there’s a quick introduction to firewalls at the end of this article. This article attempts to explain in full detail exactly how each participant in the FileMaker ecosystem communicates, so you can jump right past these problems and get to developing awesome databases. Improper firewall configuration can lead to all kinds of problems, some obvious (I can’t connect to my server) and some not-so-obvious (the Server Admin Console opens, and then hangs). One consequence of all the changes is that things may not work properly without reconfiguring your *firewall(s)*. FileMaker Server 9 represents a pretty significant redesign of the FileMaker Server product line.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |