Our long journey through advanced GeoServer configuration has now come to an end. In this chapter, we considered the benefits of implementing a cluster of GeoServer instances and looked at a new extension available to manage it. We also looked at a special case where we have to configure Windows servers in a specific way so that they are able to share a data directory from the network.

Following on from clustering, we examined different approaches to optimize the configuration; we looked at using native JAI libraries, specifying options for JVM, disabling unnecessary services, and managing the flow of requests handled by the server, in particular.

Finally, we looked at how we can implement scripts that can watch and monitor our instances of GeoServer, automatically restarting when failures are detected, checking to ensure the Tomcat service is up and running, but also ensuring it is responding to HTTP web requests. We then saw how to set the Watchdog scripts to run at specific intervals...