I’m curious about this too. I downloaded the standalone webapplication (camunda-webapp-tomcat-standalone-7.9.0.war) and deployed it to our pre-existing tomcat 8.0.2 server.
I’m wondering what is the rest URL for this standalone webapplication version of camunda? I’m getting 404s for the documented url of /engine-rest/engine/default.
After looking at the standalone war’s web.xml I tried hitting the /api/engine/default url but that doesn’t seem to get me much. I receive some json NotFoundExceptions returned with a message that a “resource could not be found for relative /default/task” at that url.
I also installed the engine-rest package war that sgru and rodneivete mentioned but I’m not sure how to configure it to connect to the embedded engine in the standalone war.
The default process engine is available out of the box by accessing /engine-rest/engine/default/{rest-methods} or simply /engine-rest/{rest-methods}.
I was able to receive some simple json back when I performed a HTTP GET to
/api/engine/engine. The response to that GET contained the word “default” to indicate the name of the process engine. Should I be doing something different to access REST in the standalone war WAR distribution?
Basically rest usage described in the mentioned docs is only for share engine and doesn’t work for standalone webapplication.
In case of standalone web app you can try to use the camunda webapps rest api, so try to access: camunda/api/engine/engine/default
I checked with my colleagues.
Unfortunately the deploy button from the Modeler cannot be configured with the webapps rest api.
Because you will need to configure a session and this is not possible.
The deployment from the Modeler can be setup only with Rest API without authentication.