In this movie we will talk specifically about FileMaker Server Advanced. Let's recap what sets FileMaker Server Advanced apart from the regular FileMaker Server. Well, first the user limit for FileMaker Pro clients is set to 999 instead of 250. Secondly, FileMaker Server Advanced gives you instant web publishing extra. And it also gives you the ability to use FileMaker data through an ODBC or JDBC connection; 50 sessions worth of that. And remember that typical ODBC JDBC sessions were very short. We mentioned in the movie on multiple machine deployment that there are different scenarios where the web server and or the web publishing engine can be on different machines. The installation process for FileMaker Server Advanced is exactly the same as that for regular FileMaker Server except that now you can choose to enable instant web publishing and ODBC. The choice whether or not to deploy across multiple machines may be more relevant for FileMaker Server Advanced than for regular FileMaker Server depending on the load that you're expecting. Let's recap the choices that you can make and why you would have to make them. The core component is the FileMaker database engine. FileMaker Pro clients, potentially 999 of them, admin users through the Admin Console and ODBC JDBC users connect to that directly. Remember that ODBC JDBC is a FileMaker Server Advanced only feature. Then there's the web publishing. That encompasses the web server and the web publishing engine so that traffic flows like this. That goes for custom web publishing but also for instant web publishing which is, as we know, a FileMaker Server Advanced only feature. So your choices are to put it all one machine, which may not be a good idea if you really expect a thousand normal FileMaker users plus a bunch of web users and a hefty load of ODBC and JDBC connections. A better choice in that scenario would be to break out the database engine on its own machine and let the second machine take care of the web clients. In most scenarios with a heavy load, this scenario will give you the best performance. If your web server will be busy with a lot of non-FileMaker tasks, then you can consider isolating the web server on its own machine. So what if you purchase regular FileMaker Server and then decide you need FileMaker Server Advanced? Well, upgrading is easy. All you need to do is to upgrade the license key. You do not need to reinstall FileMaker Server. And to upgrade the license key you go to General Settings and here at the bottom click the Change License Key. This is, by the way, also a good place to check what kind of FileMaker Server you're looking at. Once you've plugged in the new license key, you can now enable instant web publishing and ODBC and JDBC. Depending on your expected user load, you may need to change the deployments over multiple machines if you install everything on one machine. For that you go to the Overview Screen and click here to start the deployment wizard. In that wizard you'll get an overview of the different deployments you can choose from. We've currently installed everything on one machine but we could also choose now to go to two machines, two machine alternative or a three machine deployment. Regular two machine deployment is where the database engine goes on one machine and all the web stuff goes on the second machine. That is the web server and the web publishing engine. A two machine alternative is where you have the database engine on one machine together with the web publishing engine. A second machine only holds the web server. And the three machine deployment is where the database engine goes on machine one, the web publishing on machine two and the web server is machine three. As long as the current machine remains the master machine, meaning the machine that will have the core FileMaker Server database engine, you will not have to reinstall. If you want to demote the current machine to a worker machine to run the web publishing engine or the web server, then you will have to uninstall FileMaker Server.