Skip to content
This repository has been archived by the owner on May 23, 2024. It is now read-only.

JobId and default user credentials in 52 North 4.0 Beta Version #280

Open
gabrilator opened this issue Jul 25, 2019 · 5 comments
Open

JobId and default user credentials in 52 North 4.0 Beta Version #280

gabrilator opened this issue Jul 25, 2019 · 5 comments

Comments

@gabrilator
Copy link

Hi,
I installed the 52 N server 4.0 Beta Version in order to be able to use the new methods provided in WPS 2.0 such as getStatus, but I can't log into the server (I guess this is needed in order to check the current JobIds).

Could anybody provide me some insights on this ?

Thank you!

@bpross-52n
Copy link
Member

Hi,
the default credentials for the WPS are wps:wps. But you will not be able to see any JobIDs after login. You get a JobID after sending an execute-request. However, in our new WPS framework (javaPS) we list the jobIDs in the Capabilities document, see here: http://geoprocessing.demo.52north.org:8080/javaps/service?request=GetCapabilities&service=WPS

@gabrilator
Copy link
Author

gabrilator commented Jul 25, 2019

Thank you bpross-52n, I didn't know about javaPS!
So then, would you recommend that I disregard 52N 4.0 Beta and just jump to javaPS?

Cheers!

@gabrilator
Copy link
Author

Currently, when I send an execute request, I'm not seeing the JobId back. I'm just seeing a blank response and then I do see the result of the execution of my algorithm. Where should I be able to see it?

Thank you!

@bpross-52n
Copy link
Member

You probably executed synchronously. To execute asynchronously (and to be able to get status updates), set the attribute "mode" to "async" in your request. Below is an example.

As for the question WPS 4.0 vs. javaPS: Main differences:

  • WPS 4.0 has an admin-UI, javaPS not (yet)
  • WPS 4.0 supports the WPS standards 1 and 2, javaPS only 2
  • WPS 4.0 comes with processes, javaPS is shipped without any processes
  • WPS 4.0 uses xmlbeans, javaPS supports streaming XML readers/writers

In general, WPS 4.0 is a grown project with many features, but also legacy code. javaPS was build completely from scratch. It is pretty bare-bone atm., but new features will be added step by step. We are using javaPS in all of our current projects

<?xml version="1.0" encoding="UTF-8"?>
<wps:Execute
  xmlns:wps="http://www.opengis.net/wps/2.0"
  xmlns:ows="http://www.opengis.net/ows/2.0"
  xmlns:xlink="http://www.w3.org/1999/xlink"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.opengis.net/wps/2.0 http://schemas.opengis.net/wps/2.0/wps.xsd"
  service="WPS" version="2.0.0" response="document" mode="async">
  <ows:Identifier>org.n52.wps.server.algorithm.SimpleBufferAlgorithm</ows:Identifier>
  <wps:Input id="data">
    <wps:Reference xlink:href="http://geoprocessing.demo.52north.org:8080/geoserver/wfs?SERVICE=WFS&amp;VERSION=1.0.0&amp;REQUEST=GetFeature&amp;TYPENAME=topp:tasmania_roads&amp;SRS=EPSG:4326&amp;OUTPUTFORMAT=GML3" schema="http://schemas.opengis.net/gml/3.1.1/base/feature.xsd" />
  </wps:Input>
  <wps:Input id="width">
    <wps:Data>
      <wps:LiteralValue>0.05</wps:LiteralValue>
    </wps:Data>
  </wps:Input>
  <!-- Uses default output format -->
  <wps:Output id="result" transmission="value"/>
</wps:Execute>​

@gabrilator
Copy link
Author

Thank you, it was that! It worked :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants