This movie discusses the Client Section of the FileMaker Server Admin Console. When you have the Admin Console open, you can see the list of clients that are currently connected to any of the files hosted on that particular FileMaker Server. The Connection Type Column will tell you what kind of session that is, whether it's a regular FileMaker Pro client, an instant web publishing or custom web publishing session or it might be a script that is running server-side. ODBC and XML connections will not show up here unless that request takes a long time. But usually though their connections open and close too fast for it to show up in this interface. You will see them in the access log, however, because all of the connections show up there. So what you might see appear that might be unusual is this for instance, which is a script that is running server-side. It's called the big loop and all it does is runs a loop in a FileMaker hosted file that counts to one million and it is run actually by one of our schedules; by this one. So if we check these details, we see the access type is script and it is, the client version is listed as server, so we know it's server actually performing that script. At the bottom pane we have some more information about this particular user. So we know it's our server. It's running on Windows and it's a FileMaker script. And this is the file that it's running in. If you click on any of the other guests, we can get some information about what they're doing. This particular client on this IP Address is using FileMaker Pro 10 and it has two files open. In the User Detail we can tell the name of his machine, the MAC Address and some more useful information. From the drop-down at the top, we can send a message to a user and we can also disconnect them. If you try and send a user a message, then that message will show up for about 30 seconds in his session. If we try and send a message to a web user, nothing will happen but you will also not get an error message saying that it didn't happen. So you might get the feeling that you are able to send a message to web clients but in reality, nothing will happen. If you try and disconnect a web user, then they will get a message in their session the next time they perform an action that requires a communication with FileMaker Server, like switching a layout or changing records. This is an instant web publishing session through the hosted file, the FileMaker Sample File. If we go to our console and disconnect this particular user, it's this one. We can tell by the bottom it's Firefox running on OS X. If we now go to that particular session and require something that will require communication from FileMaker Server, like switching layouts, we will get an error saying that it's a bad request because FileMaker Server has already disconnected our session. The FileMaker Server Configuration Panel also has a Client's Tab and a database server. What you can set here is the maximum number of clients that you will let connect, up to a maximum allowed by your license, which is 250 for the regular FileMaker Server and 999 for Server Advanced. There are two connection pools available to FileMaker Server. One is for FileMaker Pro and ODBC, JDBC users together, which is the one that we're looking at and then there's a second pool for connections through the web publishing engine, meaning custom web publishing through XSLT, instant web publishing, PHP and XML publishing. And you will find that one under web publishing. Noting again that the limit for custom web publishing only comes into play when you enable database sessions in the Server Admin Console. If you use custom web publishing without database sessions, you can have as many web clients as your hardware can service. So why would anyone not set these available connections to the max? Well, for performance and stability reasons. The higher you set these values, the more memory FileMaker Server will try and grab and the higher you will need to set the cache. More about cache in another movie. Best practice is then to set the values here to just slightly higher than you will actually need. Note that you can not configure how many of the 50 ODBC and JDBC connections you make available. That's an all or nothing setting by enabling ODBC and JDBC. The JDBC sessions come out of the total pool that's also available for FileMaker Pro. Towards the bottom of this first pane there's a setting to automatically disconnect clients that have not been active for a while. And you can specify what interval qualifies for that. This setting only applies to users connected through a privilege set that has the matching bit set in the FileMaker file. So if you go to a FileMaker file and we go have a look in the privilege sets, then users will only get disconnected if their privilege set had this particular one toggled on, the one that says disconnect users from FileMaker Server when idle. So the setting on FileMaker Server will only be applicable to users that have the privilege set with this particular setting on. This particular setting is off by default so if you want to make use of it, you will have to enable it manually. Two other things that can be configured from this Client's Tab. You can allow FileMaker clients to automatically download updates. Now, note that this is updates for plug-ins and plug-in license files only. There's a separate movie on this whole topic for more detail. And the other setting is in the second pane where you can make FileMaker Server information available in a directory service. We also have a separate movie on this. For now, just know that this has nothing to do with giving users access to your files, to your solution. This is merely for publishing information about FileMaker Server so that users can find FileMaker Server. Again, this has nothing to do with allowing people to enter your files. And that's it for the Client section. Remember that all of the changes you make here will be applied immediately. You don't need to restart the FileMaker Server services or daemons to get them working.