Information Technology Reference
In-Depth Information
URL
Functionality
/rest/task/{task-id}/content
This URL retrieves the contents of a task (its task inputs, outputs, and errors).
/rest/task/{task-id}/content/{content-
id}
This URL retrieves a specific content of one specific task.
This URL clears the audit information of the task database.
/rest/task/bam/history/clear
/rest/runtime/{deployment-id}/process/
history/clear
This URL clears the audit information of the process database.
/rest/runtime/{deployment-id}/process/
history/instances
This URL retrieves historical information of all completed and running process
instances.
/rest/runtime/{deployment-id}/history/
instance/{process-instance-id}
This URL retrieves all historical info about one specific process instance.
/rest/runtime/{deployment-id}/history/
instance/{process-instance-id}/node
This URL retrieves all historical info about nodes of one specific process in-
stance.
/rest/runtime/{deployment-id}/history/
instance/{process-instance-id}/variable
This URL retrieves all historical info about variables of one specific process in-
stance.
/rest/deployment
This URL show all the deployments that are available.
/rest/deployment/{deployment-id}/deploy
This URL updates a deployment.
/rest/deployment/{deployment-id}/unde-
ploy
This URL removes a deployment.
/rest/deployments
This URL shows all the deployments that are available.
The most important URL exposed is probably the "execute" URL:
/rest/runtime/
{deployment-id}/execute
. Through this URL, using the command pattern, every
single function in the KIE session and the task service can be implemented using the same
API. This is the one used by the implementation at the
kie-services-client
de-
pendency to expose the
RemoteRuntimeEngine
class. The following code snippet
shows how to build a REST remote runtime engine:
