.. _data_wpsjdbc: WPS JDBC ======== The WPS JDBC extension is a WPS status storage for asynchronous requests. Main advantages are: * Asynchronous request status sharing among multiple GeoServer nodes * Ability to retain the status of completed requests even after the GeoServer(s) have been restarted. .. _wpsjdbc_install: Installing the WPS JDBC extension --------------------------------- #. From the :website:`website download ` page, locate your release, and download: :download_extension:`wps-jdbc` Verify that the version number in the filename corresponds to the version of GeoServer you are running (for example |release| above). #. Extract the contents of the archive into the :file:`WEB-INF/lib` directory in GeoServer. Make sure you do not create any sub-directories during the extraction process. #. Restart GeoServer. Configuring the WPS JDBC properties ----------------------------------- #. Create a file named `jdbcstatusstore.props` into the `GEOSERVER_DATA_DIR` root #. Update the sample content below accordingly to your connection parameters .. code-block:: user=postgres port=5432 password=****** passwd=****** host=localhost database=gsstore driver=org.postgresql.Driver dbtype=postgis #. Restart GeoServer Share the WPS Execution Directory among the cluster nodes --------------------------------------------------------- Typically the WPS JDBC plugin is useful when setting up a GeoServer cluster. The plugin allows sharing of the execution status among the nodes of the cluster. Nevertheless, this won't be sufficient. You will need to share the Execution folder too, in order to allow the different instances to correctly retrieve the executions results. #. Create a shared folder that all the nodes can reach somehow, e.g. by using `nfs` #. From the GeoServer Admin dashboard, go to the `WPS` menu and edit the Resource Storage Directory accordingly .. figure:: images/wps-resource-storage-directory.png :align: center *WPS JDBC shared Resource Storage Directory*