Upgrade¶
This section describes how to perform an upgrade to GeoServer Enterprise 2022.3.
Before you start¶
Minor updates may be performed in place:
GeoCat Recommends backing up your
GEOSERVER_DATA_DIR, and the configurationconf/Catalina/localhost/geoserver.xmlfile.
For major updates or migrating from an earlier version of GeoServer:
GeoCat Recommends backing up your
GEOSERVER_DATA_DIR, and the configurationconf/Catalina/localhost/geoserver.xmlfile.We do not recommend upgrading on a production server. Instead perform a new installation and transfer your data and settings to the new machine.
References:
Minor Update (Windows)¶
This is an essential update GeoServer Enterprise 2022.2-1.
Release |
GeoServer |
Updates |
Standard |
Premium |
|---|---|---|---|---|
GeoServer Enterprise 2022.0 |
2.21.0 |
2022 |
2025 |
2027 |
GeoServer Enterprise 2022.1 |
2.21.2 |
2022 |
2025 |
2027 |
GeoServer Enterprise 2022.2 |
2.21.3 |
2022 |
2025 |
2027 |
GeoServer Enterprise 2022.2-1 |
2.21.4 |
2022 |
2025 |
2027 |
GeoServer Enterprise 2022.3 |
2.22.2 |
2022 |
2025 |
2027 |
Minor upgrades can be performed in place and consist of a new web archive:
Login to nexus.geocat.net and browse to the enterprise folder:
Navigate to the latest geoserver release and select the
geoserver-standardzip archive.
Unzip this file containing:
windows- sample configuration filesGPLandLICENSE.txtopen source license informationgeoserver.war- geoserver enterprise web application used below
Stop the Tomcat service:
Open the Tomcat Program folder by using the Start menu to select .
Open the
webappsfolder, and delete the existing:geoserver/foldergeoserver.warweb archive
Copy the
geoserver.warfile to the to tomcatwebappsfolder.Start the Tomcat service.
Tomcat will deploy
geosever.warweb application, creating geoserver folder for the running application.In your web browser, navigate to localhost:8080/geoserver to verify that GeoServer Enterprise is correctly working.
Minor Update (Linux)¶
This is an essential update GeoServer Enterprise 2022.2-1.
Release |
GeoServer |
Updates |
Standard |
Premium |
|---|---|---|---|---|
GeoServer Enterprise 2022.0 |
2.21.0 |
2022 |
2025 |
2027 |
GeoServer Enterprise 2022.1 |
2.21.2 |
2022 |
2025 |
2027 |
GeoServer Enterprise 2022.2 |
2.21.3 |
2022 |
2025 |
2027 |
GeoServer Enterprise 2022.2-1 |
2.21.4 |
2022 |
2025 |
2027 |
GeoServer Enterprise 2022.3 |
2.22.2 |
2022 |
2025 |
2027 |
Minor upgrades can be performed in place and consist of a new web archive:
Login to nexus.geocat.net and browse to the enterprise folder:
Navigate to the latest geoserver release and select the
geoserver-standardzip archive.
Unzip this file containing:
windows- sample configuration filesGPLandLICENSE.txtopen source license informationgeoserver.war- geoserver enterprise web application used below
Stop the Tomcat service:
sudo service tomcat9 stopNavigate to the
[Tomcat_folder]/webappsfolder (often/var/lib/tomcat9/webappsor/opt/tomcat/latest/webapps.)Remove the previous web application:
rm geoserver.war rm -r geoserver
Copy the
geoserver.warfile to the to tomcatwebappsfolder.Start the Tomcat service:
sudo service tomcat9 startTomcat will deploy
geosever.warweb application, creating geoserver folder for the running application.In your web browser, navigate to localhost:8080/geoserver to verify that GeoServer Enterprise is correctly working.
GeoServer Enterprise Upgrade¶
Release |
GeoServer |
Updates |
Standard |
Premium |
|---|---|---|---|---|
GeoServer Enterprise 2022 |
2.21 |
2022 |
2025 |
2027 |
GeoServer Enterprise 2021 |
2.20 |
2021 |
2024 |
2026 |
GeoServer Enterprise 2020.5 |
2.18 |
2020 |
2023 |
2025 |
GeoServer Enterprise 2.14 |
2.14 |
2019 |
2022 |
2024 |
GeoServer Enterprise 2.13 |
2.13 |
2018 |
2021 |
2023 |
GeoServer Enterprise Standard is provided ready to use with popular extensions preinstalled.
GeoServer Enterprise Premium is provided as a preconfigured web archive with the extensions you have requested. If you have chosen to remove an extension please work with our staff on the my.geocat.net support portal to determine if any modifications to your data directory are required during the upgrade process.
Follow install instructions to setup a new environment:
This is a good opportunity to update to:
Tomcat 9
Java 11
Make a backup of your existing
GEOSERVER_DATA_DIRECTORYprior to use.This release changes from Log4j 1.2
propertieslogging profiles to Log4j 2xmllogging profiles.When the application first starts up the built-in logging profiles are replaced with new Log4j 2
xmlfiles.Only if you made custom logging profile:
Your existing Log4j 1.2
propertieslogging profiles remain unchanged and can be used with Log4j 2.If you edited any of the built-in log4j 1.2
propertieslogging profiles your changes will be overwritten during the migration to Log4j 2xmlfiles (and the previous content saved to abakbackup file).To recover a customized logging configuration rename the
bakbackup to a new file withpropertiesextension.
Migrating from GeoServer Distribution¶
It is straight forward to migrate from the GeoServer Community Distribution to GeoServer Enterprise.
Migration guidance for specific versions of GeoServer are noted below, along with timeframe for community updates and GeoCat support information.
Version |
Guidance |
Updates |
Standard |
Premium |
|---|---|---|---|---|
GeoServer 2.21 |
February 2023 |
2025 |
2027 |
|
GeoServer 2.20 |
September 2022 |
2024 |
2026 |
|
GeoServer 2.19 |
February 2022 |
2024 |
2026 |
|
GeoServer 2.18 |
August 2021 |
2023 |
2025 |
|
GeoServer 2.17 |
End of ArcSDE support |
February 2021 |
2023 |
2025 |
GeoServer 2.16 |
August 2020|br| September 2019 |
2022 |
2024 |
|
GeoServer 2.15 |
Java 8 LTS minimum |
February 2020 |
2022 |
2024 |
GeoServer 2.14 |
REST API geometry bindings changed, recommend re-testing automation scripts. |
July 2019 |
2021 |
2023 |
GeoServer 2.13 |
December 2018 |
2021 |
2023 |
|
GeoServer 2.12 |
REST API ported to spring-framework, recommend re-testing automation scripts. |
August 2018 |
2020 |
2022 |
GeoServer 2.11 |
February 2018 |
2020 |
2022 |
|
GeoServer 2.10 |
August 2017 |
2019 |
2021 |
|
GeoServer 2.9 |
Java 8 required |
January 2017 |
2019 |
2021 |
GeoServer 2.8 |
End of Java 7 Support |
August 2016 |
2018 |
2020 |
To migrate from GeoServer distribution to GeoServer Enterprise:
Locate your
GEOSERVER_DATA_DIR:Binary:
data_dirWAR:
webapps/geoserver/dataWindows:
C:\ProgramData\GeoServer\DataWindows:
C:\Program Files\GeoServer\data_dirLinux:
/usr/share/geoserver
Make a backup of your data directory:
cd /usr/share zip -r data.zip geoserver
Check for any configuration settings recorded in:
Windows:
bin/setenv.batLinux:
bin/setenv.shLinux:
/etc/default/tomcat7service, using a``JAVA_OPTS`` environmental variableWindows Service: Apache Tomcat 9.0 Tomcat Properties, where Java Options are located on the Java tab.
During upgrade any custom settings noted here can be applied to your new system following: Set Java startup options.
Check if
conf/web.xmlhas enabled Cross-Origin Resource Sharing (CORS):<filter> <filter-name>CorsFilter</filter-name> <filter-class>org.apache.catalina.filters.CorsFilter</filter-class> </filter> <filter-mapping> <filter-name>CorsFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>
To enable CORS for your new system: Cross-Origin Resource Sharing (CORS).
Follow the GeoSever Enterprise installation instructions:
Transfer your backup (the file :data.zip above) for use when setting up the
GEOSERVER_DATA_DIR.The file will be unpacked into the recommended location:
Linux:
/var/opt/geoserver/dataWindows:
C:\ProgramDataGeoServer\Data
This
GEOSERVER_DATA_DIRconfiguration will be updated in place as GeoServer starts up.
Migrating from Boundless Suite¶
As a reseller of the now discontinued Boundless Suite we would like to offer migration guidance to GeoServer Enterprise.
Planning a migrating to GeoServer Enterprise Premium should be conducted with the assistance of staff on the my.geocat.net support portal to ensure your pre-configured web archive as the extensions you require.
Version |
GeoServer |
Environment |
Date |
|---|---|---|---|
Boundless Suite 1.2.0 |
GeoServer 2.15 |
Java 8 / Java 11 / Tomcat 9 |
2019 |
Boundless Suite 1.1.1 |
GeoServer 2.13 |
Java 8 / Tomcat 8.5 |
2018 |
Boundless Suite 1.0.0 |
GeoServer 2.12 |
Java 8 / Tomcat 8.5 |
2018 |
Boundless Suite 4.10 |
GeoServer 2.11 |
Java 8 / Tomcat 8.0 |
2017 |
OpenGeo Suite 4.9 |
GeoServer 2.9 |
Java 8 / Tomcat 8.0 |
2016 |
OpenGeo Suite 4.8 |
GeoServer 2.8 |
Java 7 / Tomcat 7 |
2016 |
OpenGeo Suite 4.7 |
GeoServer 2.7 |
Java 7 / Tomcat 7 |
2015 |
linux package |
migration guidance |
|---|---|
|
Use of geocat bridge, improved GeoServer style editor |
|
not-available |
|
Latest GeoServer Enterprise documentation |
|
GeoServer Enterprise Standard |
|
download standalone geowebacache |
|
Recommend GeoNetwork Enterprise Map viewer |
|
Recommend QGIS WPS Client plugin |
|
Recommend tomcat provided by your linux distribution |
|
Recommend postgresql and postgis provided by your linux distribution |
|
GeoServer Enterprise Premium |
|---|---|
|
Unavailable |
|
|
|
|
|
GeoServer Enterprise Premium |
|
GeoServer Enterprise Premium |
|
GeoServer Enterprise Premium |
|
|
|
|
|
|
|
GeoServer Enterprise Premium |
|
|
|
|
|
|
|
GeoServer Enterprise Premium |
|
GeoServer Enterprise Premium |
|
GeoServer Enterprise Premium |
|
GeoServer Enterprise Premium |
|
GeoServer Enterprise Premium |
|
Unavailable |
|
|
|
GeoServer Enterprise Premium |
|
GeoServer Enterprise Premium |
Keep in mind that some components such as jdbcconfig and jdbcstore fall outside of GeoCat Enterprise service-level agreement.
We do not recommend upgrading on a production server. Instead perform a migration to new GeoServer Enterprise installation and transfer your data and settings to the new machine.
OpenGeo Suite was distributed as a series of packages resulting in a non-standard Tomcat environment making upgrading in-place impractical.
To migrate from Boundless Suite:
Locate your
GEOSERVER_DATA_DIR:Windows:
C:\ProgramData\Boundless\geoserver\data\DataWindows:
C:\ProgramData\Boundless\OpenGeo\geoserverLinux:
/var/opt/boundless/geoserver/dataLinux:
/var/lib/opengeo/geoserver
Make a backup of your data directory:
cd /var/lib/opengeo zip -r data.zip geoserver
Check for any configuration settings recorded in:
/etc/default/tomcat7service, locateOPENGEO_OPTS:OPENGEO_OPTS="-Djava.awt.headless=true -Xms256m -Xmx768m -Xrs -XX:PerfDataSamplingInterval=500 -Dorg.geotools.referencing.forceXY=true
During upgrade any custom settings noted here can be applied to your new system following: Set Java startup options.
Check if
conf/web.xmlhas enabled Cross-Origin Resource Sharing (CORS):<filter> <filter-name>CorsFilter</filter-name> <filter-class>org.apache.catalina.filters.CorsFilter</filter-class> </filter> <filter-mapping> <filter-name>CorsFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>
To enable CORS for your new system: Cross-Origin Resource Sharing (CORS).
Follow the GeoSever Enterprise installation instructions:
Transfer your backup (the file :data.zip above) for use when setting up the
GEOSERVER_DATA_DIR.The file will be unpacked into the recommended location:
Linux:
/var/opt/geoserver/dataWindows:
C:\ProgramDataGeoServer\Data
This
GEOSERVER_DATA_DIRconfiguration will be updated in place as GeoServer starts up.Migrate PostgreSQL / PostGIS database.
If you made use of Boundless Suite PostGIS database, migrate to the new system following the PostGIS Dump/Restore” instructions.