We’ll be using the Keycloak Administrator Console to do this, so let’s get logged in and get things set up. So one thing I will try, instead of restarting the entire server, is to simply restart the Admin Server.So far in our Keycloak series we have been setting up the infrastructure for our server to run on, but now that’s done we can actually configure Keycloak to act as our authentication server for FileMaker. Like with many things in the technology world, by simply restarting it you can sometimes fix something that has gone awry. But when you try to open up the Admin Console, nothing happens. You know the database server is still running, because people are using the databases and you can still see the server when you click “open remote” on your client version of FileMaker Pro. For one reason or another, sometimes the Admin Server can stop working. One thing I use this for on occasion is to restart the Admin Server. Remember what I said about great power? You should definitely play around with this on a test server before you use it on a production server. This would shut down the database server, and immediately disconnect all the clients. So, for example, if you wanted to force a restart of the whole database server, you would type " fmsadmin restart server -f -force." The options, or parameters, that you specify at the end of the command give you more control over what you want to do. It basically breaks down what your command should look like, and what OPTIONS you can specify for each command.
0 kommentar(er)
