GeoServer
  • About
  • Blog
  • Download
  • Documentation
  • GeoServer 2.28.x User Manual »
  • Running in a production environment
  • Next
  • Previous|

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 17
    • Running on Java 11
  • Container Considerations
    • Optimize your JVM
    • Use newer Marlin rasterizer
    • Enable CORS
  • Configuration Considerations
    • General Guidance
    • GeoServer Workspace Admin Guidance
    • GeoServer Administrator Guidance
    • System Administrator Guidance
    • Application Server Guidance
    • Security and Service Hardening
    • Session Management
  • 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
    • Clustering
  • Troubleshooting
    • User Interface
    • Web Services
    • Leveraging GeoServer own log
    • Server Status JVM Console
    • Using JDK tools to get stack and memory dumps
    • Configuration
  • Make cluster nodes identifiable from the GUI
Previous: Parameterize catalog settings
Next: Java Considerations

Continue Reading

  • Previous: Parameterize catalog settings
  • Next: Java Considerations

This Page

  • Edit

Known GeoServer issues

  • Jira issue tracker
© Copyright 2025, Open Source Geospatial Foundation. License Creative Commons Attribution. Last updated on May 08, 2025. Created using Sphinx.