Package: wps-remote
[![Build Status](https://travis-ci.org/geoserver/wps-remote.svg?branch=master)](https://travis-ci.org/geoserver/wps-remote)
[![Coverage Status](https://coveralls.io/repos/github/geoserver/wps-remote/badge.svg?branch=master)](https://coveralls.io/github/geoserver/wps-remote?branch=master)RemoteWPS[RemoteWPS] is an open source software written in Python part of the GeoServer (http://geoserver.org)
project that allows users to publish their executables as GeoServer WPS Processes through the XMPP protocol.RemoteWPS is meant to be used along with the GeoServer “wps-remote” plugin for the WPS
(https://github.com/geoserver/geoserver/tree/master/src/community/wps-remote).Being a community-driven project, RemoteWPS is developed, tested, and supported by a diverse group of
individuals and organizations from around the world.## LicenseRemoteWPS licensed under the [GPL](http://www.gnu.org/licenses/old-licenses/gpl-2.0.html).## UsingYou can install the “wps-remote” Python package by using the PyPi distributionpip install wps-remote==2.14.1Please refer to the [user guide](http://docs.geoserver.org/latest/en/user/community/remote-wps/index.html) for detailed
information on how to install and use RemoteWPS.## API Reference Dochttp://docs.geoserver.org/latest/en/user/community/remote-wps/install_python.html#annex-a-remote-wps-python-wrapper-reference## BugsThrough GeoServer JIRA.GeoServer uses [JIRA](https://osgeo-org.atlassian.net/projects/GEOS), hosted by
[Atlassian](https://www.atlassian.com/), for issue tracking.## Mailing ListsThrough GeoServer Mailing Lists.The [mailing list page](http://geoserver.org/comm/) on the GeoServer web site provides
access to the various mailing list, as well as some indication of the [code of conduct](http://geoserver.org/comm/userlist-guidelines.html) when posting to the lists## ContributingThrough GeoServer Process.Please read [the contribution guidelines](https://github.com/geoserver/geoserver/blob/master/CONTRIBUTING.md) before contributing pull requests to the GeoServer project.## More InformationVisit the [website](http://geoserver.org/) or read the [docs](http://docs.geoserver.org/).Change Log2.14.1 [2018-09-14 11:48:37] (aligned with GeoServer Remote WPS Plugin - 2.14.x)Fixes: inputs and outputs mime-types declaration on service.configCleanup: removing non source code stuffResilience: resource_monitoring now skips non-python/readable processes without dyingResilience: processbot identifies relative paths for executable commands2.12.0 [2017-07-03 12:13:10] (aligned with GeoServer Remote WPS Plugin - 2.12.x)Fix for: Inputs application/json mapping errorFix for: Inputs application/vnd.geo+json supportFix for: Date input / output parsingFix for: JSON ID errorImproved robustness of wps agentAllowed “-” in string input parametersFix for: Catch resource clean exceptionFix for: Input / output parameters are not sorted according to the process definition2.11.2 [2017-02-16 10:12:23]SFTP/FTP pluggable uploaders supportMinor refactoring and code cleanup2.9.3 [2016-03-31 17:24:47]Added “processbot” XMPP connection checksAdded “servicebot” check “processbot” status error and send error message impersonating the underlying processAdded “NetCDF Output” example on service.config2.9.2 [2016-03-17 17:33:19]Added “process_blacklist” property to “service.config” fileAdded “proc_is_running(self, proc_names)” to “ResourceMonitor(threading.Thread)” background thread2.9.1 [2016-03-16 11:09:56]Added “GetLoadAverageMessage” XMPP message for resource monitoringAdded “ResourceMonitor(threading.Thread)” background thread collecting resource consuption dataOn GeoServer side the “remoteConfig.properties” file on GEOSERVER_DATA must be updated with the properties
xmpp_cpu_perc_threshold = 80.0
xmpp_mem_perc_threshold = 80.0