Administration on Boundless Server Enterprise

This document contains information about various tasks specific to Boundless Server Enterprise. For more details, please see the System administration section.

Controlling the PostgreSQL service

PostgreSQL should be set up using AWS Aurora. See Getting started with PostGIS to learn more about working PostgreSQL.

Working with GeoServer

Redis and the GeoServer Data Directory

Redis is an in-memory data structure store, used as a database, cache, and message broker. Boundless Server Enterprise (BSE) uses Redis for Geoserver to maintain all of its configurations and Geoserver resources. BSE does not cache any resources but instead fetches configuration from the Redis on each request. This renders BSE stateless and scalable.

The Resource Store within Redis stores the binary contents of everything that would be normally in the Data Directory, and still uses the relative folder structure of the data directory. The contents of the Resource Store can be viewed via REST at geoserver/rest/resource.

Geoserver instances in a BSE deployment also have a Geoserver Data Directory, which is a unique folder on each instance within BSE. It is still the default lookup path when adding a store using the Web UI, but is otherwise largely unused by BSE. Each Geoserver Data Directory is inaccessible to all other instances within BSE. The Geoserver Data Directory still has a potential application if it is configured to as shared folder, refer to creating a shared folder reference for more information.

Modify resources with REST

Within BSE, resources are any item that does not represent catalog or configuration data. BSE uses a Redis resource store to handle all resources. Typical resources include styles and icons.

To see a list of available resources direct your request to geoserver/rest/resource. Listed resources can be accessed and modified by appending /{PATH_TO_RESOURCE}.

For example the following creates a new style resource in the /styles directory:

curl -u admin:geoserver -X PUT --data "@new_point.xml" http://geoserver/rest/resource/styles/new_point.xml

Where new_point.xml contains the following content:



Using REST differentiates requests made against metadata with operation=metadata. See the REST documentation below for more information.

For a full list of REST resource operations refer to the Geoserver Resource REST API documentation.

How to add startup parameters for GeoServer

BSE configuration is done so using Spring Configuration and Environment Variables. To learn about ways to configure parameters for Geoserver refer to the instructions here Application Configuration


You can view existing Java options (system-properties) and environment variables (system-environment) on the GeoServer Detailed Status Page at geoserver/rest/about/status.