Running in a production environment

GeoServer is geared towards many different uses, from a simple test server to the enterprise-level data server. While many optimizations for GeoServer are set by default, here are some extra considerations to keep in mind when running GeoServer in a production environment.

• Java Considerations
  • Use supported JRE
  • Running on Java 11
  • Installing Unlimited Strength Jurisdiction Policy Files
  • Outdated: install native JAI and ImageIO extensions
• Container Considerations
  • Optimize your JVM
  • Enable the Marlin rasterizer
  • Enable CORS
• Configuration Considerations
  • Use production logging
  • Set a service strategy
  • Personalize your server
  • Configure service limits
  • Set security
  • Cache your data
  • Disable the GeoServer web administration interface
  • Disable the Auto-complete on web administration interface login
  • X-Frame-Options Policy
  • OWS ServiceException XML mimeType
  • External Entities Resolution
• Data Considerations
  • Use an external data directory
  • Use a spatial database
  • Pick the best performing coverage formats
• Linux init scripts
  • Debian/Ubuntu
  • Suse
  • Starting GeoServer in Tomcat
• Other Considerations
  • Host your application separately
  • Proxy your server
  • Publish your server’s capabilities documents
  • Set up clustering
• Troubleshooting
  • Checking WFS requests
  • Leveraging GeoServer own log
  • Logging service requests
  • Using JDK tools to get stack and memory dumps
  • XStream
• Make cluster nodes identifiable from the GUI