Supported databases

• PostgreSQL 9.1+ / PostGIS 2.0+
• Oracle 9+
• H2 (in memory or file, not for production)

Requirements

• Supported database (see above)
• Java JRE or JDK 6+
• Java Application Server (e.g. Tomcat 6.0+)
• netCDF4 C library (for netCDF encoding formats)
  • on Debian/Ubuntu systems, sudo aptitude install libnetcdf-dev

PostgreSQL Recommendations

It is essential that PostgreSQL be configured for proper external access and adequate memory. The defaults are not sufficient. This configuration lies outside of the scope of this project, but here are some recommended resources:

• PostgreSQL configuration guide
• pg_hba.conf docs
• pgtune

Also, bear in mind that processing millions of sensor observation can be very resource intensive, so your satisfaction with the SOS will be directly correlated to the performance of your server. Fast disk access, modern processors (quad-core), and 8+ GBs of RAM are recommended.

Set up the database

First, you’ll want to create a database user and a new database for the SOS. Next, enable PostGIS on the new database by running this SQL command:

CREATE EXTENSION postgis;

Deploy the war

Deploy the latest WAR release to your Java application server. If you’re using Tomcat, just copy the war to your Tomcat’s webapps directory.

Complete the install wizard

The new SOS is easily configured using the installation wizard. Open the newly deployed applications homepage in a browser (e.g. http://localhost:8080/i52n-sos and complete the wizard.

On the Datasource configuration page, choose the following options:

• Datasource: (if using PostgreSQL choose PostgreSQL/PostGIS, NOT PostgreSQL/PostGIS Core/Custom Core)
• Transactional Profile: enabled (default)
• Spatial Filtering Profile: enabled (default)
• Actions - Create tables: enabled (default), UNLESS YOU ARE UPGRADING, in which case choose Force updating existing tables.

On the Settings page, fill in the fields with your deployment specific information. The following fields should typically be set:

• Service Provider: All required fields
• Service Identification: All required fields
• Service:
  • SOS URL: Publicly accessible URL of SOS endpoint, e.g. http://yourdomain.org/i52n-sos/sos
  • Cache Feeder Threads: Number of threads to use for cache reloading (more threads = better for cache processing, tune for your hardware, 8 is a good default)

Finally, enter a username and password for the SOS’ admin pages.

Test the application

If all went well, you should now be able to test your application. Its location will vary depending on your settings, but if you’re testing locally a likely location is http://localhost:8080/i52n-sos.

See the test data instructions for information on how to insert and remove test data from the SOS.

Using the test client, make a GetCapabilities request.

See other example requests in the client interface.