Using the Windows Package

In order to quickly get started with the training you can follow the steps below:

  1. Download and unzip the training package into a local folder avoiding spaces in the path (for safety reasons).
  2. Double click on postgis_start.bat to start PostGIS, then wait for a few seconds. A DOS CMD window should pop up and remains open pointing out that PostGIS is running well (“PostgreSQL is starting” should be visible).
  3. Double click on tomcat_start_1.bat, this will start an instance of GeoServer. A DOS CMD window should pop up and remains open highlighting that GeoServer is working well; wait until the logging inside the CMD Windows is done then point your browser to this link which will open up the GeoServer user interface.

Warning

If Tomcat or PostgreSQL fail to start check the logs and make sure that the required ports on your computer (5434, 8083, 8009, 80) are not busy. Make sure that Skype is not running as sometimes it silently occupies ports which we need for GeoServer.

Training Content

Here below the contents of the training package are described.

  1. README.txt

    Contains legal notes.

  2. data

Contains all the data used for the demo, the GeoServer plugins as well as the GeoWebCache data directory.
  1. geoserver_data

    The GeoServer data dir.

  2. setenv.bat

    Used by most of the script to setup the environment, to change the Java version and the GeoServer data dir. This file can be edited appropriately.

  3. jdk

    The embedded Java Virtual Machine.

  4. postgres

    The standalone PostgreSQL-9.2 + PostGIS-2.0 installation folder (contains the ‘data’ directory with the databases).

  5. pgAdmin.bat

    Starts the PostgreSQL PgAdmin III admin interface.

  6. postgis_setup.bat

    Optional script to recreate the Postgres database (makes use of setenv.bat).

  7. postgis_start.bat

    Starts the postgres server (makes use of setenv.bat).

  8. postgis_stop.bat

    Stops the postgres server (makes use of setenv.bat).

  9. tomcat-7.0.72

    Contains three differents instances of tomcat.

  10. tomcat_start_1.bat

    Starts the first tomcat instance (makes use of setenv.bat).

    Used by the main Geoserver and the Map application.

  11. tomcat_start_2.bat

    Starts the second tomcat instance (makes use of setenv.bat).

    Used by the another Geoserver for clustering.

  12. tomcat_start_3.bat

    Starts the third tomcat instance (makes use of setenv.bat).

    Used by activemqBroker for clustering.

  13. tomcat_stop_1.bat

    Stops the first tomcat instance (makes use of setenv.bat).

  14. tomcat_stop_2.bat

    Stops the second tomcat instance (makes use of setenv.bat).

  15. tomcat_stop_3.bat

    Stops the third tomcat instance (makes use of setenv.bat).

  16. udig

    Contains the udig standalone installation.

  17. udig.bat

    Starts uDig.

  18. Additional tools needed in different training sections:
    Apache2.2
    apache-jmeter-2.9
    gdal
    ldap
    libjpeg-turbo
    npp
    Python26

As you can see this package contains all that you need to have a fully functional environment to run GeoServer and GIS tools on your datasets.

Important

postgis_setup should never be used. If postgres database fails to work, then the postgres directory inside the training must be manually removed and then postgis_setup must be launched.

Verify Everything Works Correctly

  1. Start the tomcat_start_1.bat file, open the browser and go to the GeoServer administration page
  • The GeoServer administration page should load.

Note

On low spec hosts GeoServer can take up to 5 minutes to start up.

  1. Click on “Layer Preview”, search for Boulder and, for example, open the layergroup “BoulderCityLimits” with OpenLayers:
  • An interactive map of the current layer should open in a new tab.
  1. Start the pgAdmin.bat file (in case of error check the version of the Microsoft Visual C++ Redistributable installed on your machine) then create a new connection with the following parameters:
  • Host: localhost
  • Port: 5434
  • Username: postgres
  • Password: postgres
  1. Open the new connection.
  • A list of databases should open.