{"id":257,"date":"2024-01-17T02:39:26","date_gmt":"2024-01-17T02:39:26","guid":{"rendered":"https:\/\/www.ccsgeo.com\/?p=257"},"modified":"2024-02-17T16:41:23","modified_gmt":"2024-02-17T16:41:23","slug":"deploying-an-open-source-gis-stack-part-3-installing-geoserver","status":"publish","type":"post","link":"https:\/\/www.ccsgeo.com\/index.php\/2024\/01\/17\/deploying-an-open-source-gis-stack-part-3-installing-geoserver\/","title":{"rendered":"Deploying an Open Source GIS Stack (Part 3: Installing Geoserver)"},"content":{"rendered":"\n
\n

Geoserver Layer Preview<\/p>\n<\/blockquote>\n\n\n\n

In Part 2<\/a> of our series on deploying an Open Source GIS Stack, we went through how to install PostgreSQL with PostGIS in order to create a repository for our geographic data. Now, we need a way to serve out that data to our (theoretical) clients. In this blog, I am going to walk through the process of installing Geoserver and configuring access from client machines. In Part 3.5, I will go through how to add our PostgreSQL database as a data source and how to access our published data from QGIS. <\/p>\n\n\n\n

Installation <\/h2>\n\n\n\n

First, download the Linux binary from the Geoserver website: <\/p>\n\n\n\n

https:\/\/geoserver.org\/download\/<\/a><\/p>\n\n\n\n

I chose to download the 2.24.1 version to my local machine and then use the scp command to copy the .zip file over to my \/home directory on my Linux machine. <\/p>\n\n\n\n

Next, we need to ensure that we have the correct Java Runtime Environment. I used the command from the following documentation to install JRE: <\/p>\n\n\n\n

https:\/\/cloudinfrastructureservices.co.uk\/how-to-install-geoserver-server-on-ubuntu-20-04-tutorial-step-by-step\/<\/a><\/p>\n\n\n\n

$apt install default-jdk -y<\/strong><\/p>\n\n\n\n

When I check the Java version with java –version <\/strong>I get: <\/p>\n\n\n\n

\"Java<\/figure>\n\n\n\n

As suggested in the installation docs for Geoserver<\/a>, I used the mkdir command to create a new folder in the \/usr\/share directory: <\/p>\n\n\n\n

\/usr\/share\/$ mkdir geoserver<\/strong><\/p>\n\n\n\n

Then, use the cp command to copy the .zip file to this directory and unzip it with: <\/p>\n\n\n\n

$unzip geoserver-2.24.1-bin.zip<\/p>\n\n\n\n

Set an environment variable to point to the Geoserver installation folder: <\/p>\n\n\n\n

$echo “export GEOSERVER_HOME=\/usr\/share\/geoserver” >> ~\/.profile. ~\/.profile<\/strong><\/p>\n\n\n\n

If you need to, you can confirm that the environment variable is set correctly using the printenv command: <\/p>\n\n\n\n

\"Geoserver<\/figure>\n\n\n\n

*NOTE: If you do not set the environment variable correctly, at startup Geoserver will attempt to access the data directory in an incorrect location which will prevent it from starting properly: <\/p>\n\n\n\n

Incorrect: <\/p>\n\n\n\n

\"Geoserver<\/figure>\n\n\n\n

Correct: <\/p>\n\n\n\n

\"Geoserver<\/figure>\n\n\n\n

Finally, ensure your user owns the directory structure you created: <\/p>\n\n\n\n

$sudo chown -R USER_NAME \/usr\/share\/geoserver\/<\/strong><\/p>\n\n\n\n

<\/p>\n\n\n\n

Configuration <\/h2>\n\n\n\n

Now that we have everything installed, we still need to be able to access Geoserver from the client machine. In order to do this, we need to modify the web.xml file in \/usr\/share\/geoserver\/webapps\/geoserver\/WEB-INF to enable cross origin requests (CORS). You can use cd to access the location above and access the file with nano: <\/p>\n\n\n\n

\/usr\/share\/geoserver\/webapps\/geoserver\/WEB-INF$ sudo nano web.xml<\/strong><\/p>\n\n\n\n

Scroll down to the CORS section and uncomment out the section for CORS in Jetty so that it looks like this: <\/p>\n\n\n\n

\"Uncomment<\/figure>\n\n\n\n

As noted in the comment, there is another section further down that must also be uncommented: <\/p>\n\n\n\n

\"Additional<\/figure>\n\n\n\n

*NOTE: Make sure you have your comment syntax right. If there is a problem with the syntax in this file, Geoserver will not start. <\/p>\n\n\n\n

Now, we should be able to start up Geoserver. From the usr\/share\/geoserver\/bin directory, we can: <\/p>\n\n\n\n

usr\/share\/geoserver\/bin$ sh startup.sh<\/strong><\/p>\n\n\n\n

You should now be able to reach Geoserver in a web browser from your client machine at: <\/p>\n\n\n\n

<ip address of server>:8080\/geoserver <\/p>\n\n\n\n

As I configured the machine where I installed Geoserver with a domain name<\/a>, I can reach Geoserver at gisgeoserver1.ccsgeo.local: <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

You can also login using the default credentials: admin\/geoserver. <\/p>\n\n\n\n

Success! <\/p>\n\n\n\n

Startup Configuration <\/h2>\n\n\n\n

If you are like me, you may be calling the startup.sh command from an ssh connection to the machine where Geoserver is installed. This means that once you close the command prompt where you called startup.sh, the program will stop. To get around this and ensure Geoserver is always running, we need to configure a Systemd service file. Use cd to navigate to \/usr\/lib\/systemd\/system and use nano to create a new file in this location: <\/p>\n\n\n\n

\/usr\/lib\/systemd\/system$ nano geoserver.service<\/strong><\/p>\n\n\n\n

Add the following lines: <\/p>\n\n\n\n

[Unit]
Description=GeoServer Service
After=network.target<\/strong><\/p>\n\n\n\n

[Service]
Type=simple<\/strong><\/p>\n\n\n\n

User=username
Group=username<\/strong><\/p>\n\n\n\n

Environment=”GEOSERVER_HOME=\/usr\/share\/geoserver”<\/strong><\/p>\n\n\n\n

ExecStart=\/usr\/share\/geoserver\/bin\/startup.sh
ExecStop=\/usr\/share\/geoserver\/bin\/shutdown.sh<\/strong><\/p>\n\n\n\n

[Install]
WantedBy=multi-user.target<\/strong><\/p>\n\n\n\n

Save and close the file. Now: <\/p>\n\n\n\n

$systemctl daemon-reload<\/strong><\/p>\n\n\n\n

And set it up to always start at server reload: <\/p>\n\n\n\n

$systemctl enable –now geoserver<\/strong><\/p>\n\n\n\n

You can always check the status by running: <\/p>\n\n\n\n

$systemctl status geoserver<\/strong><\/p>\n\n\n\n

Confirm that Geoserver is running and you should be good to go! <\/p>\n\n\n\n

<\/p>\n\n\n\n

Conclusion <\/h2>\n\n\n\n

In this blog, we walked through how to install Geoserver and configure it for access from client machines. Stay tuned for Part 3.5 where I will walk through connecting our PostgreSQL database to Geoserver and publish layers that we can access from client applications.<\/p>\n\n\n\n

Resources: <\/p>\n\n\n\n

https:\/\/medium.com\/random-gis-talks\/installing-geoserver-binary%EF%B8%8F-on-ubuntu-18-04-using-terminal-ff9429ab47fa<\/a><\/p>\n\n\n\n

https:\/\/docs.geoserver.org\/maintain\/en\/user\/installation\/linux.html<\/a><\/p>\n\n\n\n

https:\/\/cloudinfrastructureservices.co.uk\/how-to-install-geoserver-server-on-ubuntu-20-04-tutorial-step-by-step\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Geoserver Layer Preview In Part 2 of our series on deploying an Open Source GIS Stack, we went through how to install PostgreSQL with PostGIS in order to create a repository for our geographic data. Now, we need a way to serve out that data to our (theoretical) clients. In this blog, I am going […]<\/p>\n","protected":false},"author":2,"featured_media":278,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_crdt_document":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[13,7,6,12],"tags":[],"class_list":["post-257","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-foss","category-technology","category-web","category-workflow"],"_links":{"self":[{"href":"https:\/\/www.ccsgeo.com\/index.php\/wp-json\/wp\/v2\/posts\/257","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ccsgeo.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ccsgeo.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ccsgeo.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ccsgeo.com\/index.php\/wp-json\/wp\/v2\/comments?post=257"}],"version-history":[{"count":15,"href":"https:\/\/www.ccsgeo.com\/index.php\/wp-json\/wp\/v2\/posts\/257\/revisions"}],"predecessor-version":[{"id":316,"href":"https:\/\/www.ccsgeo.com\/index.php\/wp-json\/wp\/v2\/posts\/257\/revisions\/316"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ccsgeo.com\/index.php\/wp-json\/wp\/v2\/media\/278"}],"wp:attachment":[{"href":"https:\/\/www.ccsgeo.com\/index.php\/wp-json\/wp\/v2\/media?parent=257"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ccsgeo.com\/index.php\/wp-json\/wp\/v2\/categories?post=257"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ccsgeo.com\/index.php\/wp-json\/wp\/v2\/tags?post=257"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}