WPS server for the RIESGOS project
3.0K
This is the dockerhub branch of the gfz-riesgos-wps-repository project which is automatically build and uploaded to Docker Hub if there is a new commit.
You need to have docker installed on the host system and pull all needed images used by the processes you want to configure.
For the GFZ services of the RIESGOS project following images are available:
docker pull gfzriesgos/quakeledger:latest
docker pull gfzriesgos/shakyground:latest
docker pull gfzriesgos/assetmaster:latest
docker pull gfzriesgos/modelprop:latest
docker pull gfzriesgos/flooddamage:latest
docker pull gfzriesgos/deus:latest
Start the RIESGOS WPS docker image with:
docker run -p8080:8080 -v /var/run/docker.sock:/var/run/docker.sock gfzriesgos/riesgos-wps
Following services can then be accessed at localhost port 8080:
The WPS itself:
http://localhost:8080/wps/WebProcessingService?Request=GetCapabilities&Service=WPS
WPS administration console with login wps/wps:
http://localhost:8080/wps
WPS JS client:
http://localhost:8080/wps-js-client/
Tomcat manager with login admin/admin:
http://localhost:8080/manager
GeoServer instance with login admin/geoserver:
http://localhost:8080/geoserver
You can add a process to the WPS by adding a configuration file to
/usr/share/riesgos/json-configurations within the docker container.
Therefore you can use the docker cp command:
docker cp myprocess.json CONTAINER-ID:/usr/share/riesgos/json-configurations
To add and enable the GFZ services you need to copy the configuration files
shipped with
this repository
located at
src/main/resources/org/n52/gfz/riesgos/configuration
to /usr/share/riesgos/json-configurations within the docker container.
It is also possible to use a volume for this directory so that the configuration files are persistent between containers creations (for example when updating the RIESGOS-WPS docker image):
docker volume create riesgos-json-config
# add additional volume parameter when starting the container
# (see above section for the whole command)
docker run ... -v riesgos-json-config:/usr/share/riesgos/json-configurations ...
Do not forget to change the default passwords once the server is running productively. This includes changing the default login for:
/usr/local/tomcat/conf/tomcat-users.xml within the container and restarting it)When changing the GeoServer password you also need to enter the same password within the GeoServer generator configurations located at the WPS admin console at: http://localhost:8080/wps/generators.
To persist those passwords and configurations of the WPS you can also use volumes for following directories/files:
/usr/local/tomcat/webapps/wps/WEB-INF/classes/db/data/usr/local/tomcat/webapps/geoserver/data/security/usergroup/default/users.xml/usr/local/tomcat/conf/tomcat-users.xmlIf you want to use your own version of the gfz-command-line-tool-repository
just mount your .jar file to
/usr/local/tomcat/webapps/wps/WEB-INF/lib/gfz-riesgos-wps.jar
with an additional volume parameter:
-v /path/to/gfz-riesgos-wps.jar:/usr/local/tomcat/webapps/wps/WEB-INF/lib/gfz-riesgos-wps.jar
You can change the log levels of the different components/classes within the administration web console of the WPS server located at http://localhost:8080/wps/log.
To set for example the log level for the process executions you can add the
value org.n52.gfz.riesgos.algorithm.impl to the "Loggers" configuration.
After changing the configuration of the log levels you need to restart
the docker container to enable the changes.
Content type
Image
Digest
sha256:56b2afc27…
Size
1.1 GB
Last updated
almost 3 years ago
docker pull gfzriesgos/riesgos-wps