Asynchronous Web Service
This web service variant is used to execute long-running workflows. Instead of getting immediate results from a pipeline with a Web Service call, the only thing that is given back after the call in the unique ID of the executing workflow. With that unique ID you can query the status of the workflow. You can specify additional variables to report back during the querying of the status of the asynchronously running workflow.
Check the Asynchronous Web Service metadata type for more information on how to configure the async web service.
Here is the lifecycle:
Executing an asynchronous web service is done by calling method
hop/asyncRun with the main parameter being the name of the asynchronous web service. (
service=<name of metadata object>) The response will be a JSON document which includes the ID of the workflow. Any other parameters will be considered to be variables or parameters of the workflow and are set in the underlying workflow.
You can choose the workflow run configuration to use for the execution with the
runConfig parameter. Please note that the more advanced features, like tracking of the progress of a running pipeline, are only available on a Local workflow engine.
You can also POST content to the web service which can be set as a variable in the executing workflow. See the "Content variable" option below. In the following example we execute service
dataload with parameter
MAX set to 50M. The content of JSON file
document.json is posted to the service. The result of the call is stored in file
curl -v \
--user cluster:cluster \
--request POST \
-o async-run.json \
-H "Content-Type: application/json" \
--data-binary '@document.json' \
You can call method
hop/asyncStatus with as arguments the service name and ID of the executing workflow:
The variables that are specified in the web service will be included in the JSON output of the service.
You can also include the execution status of one or more pipelines. You can mark a pipeline action using the action:
Enable Async Logging. You’ll be asked the name of the web service to report to.
Using the output of the previous command you can execute the following command to query the status of the workflow from a command line:
ID=$(cat async-run.json | sed 's/^.*"id":"//g' | sed 's/"}$//g') && \
curl --user cluster:cluster \
--request GET \
-o - \
The ID of the executing asynchronous web service is the same as the "container ID" of the executing workflow. This means you can query the workflow itself as well with the
hop/getWorkflowStatus service. The output of that service can be given in HTML (default), XML (parameter
&xml=Y) or JSON (parameter
&json=Y). The web service will also include the log channel ID of the workflow so that you can match it with the execution ID listed in the execution information location of your choice.
See also: Get Workflow Status.
The name of the asynchronous web service. This is the name that is passed into the
Enables or disabled this Asynchronous Web Service
Filename on the server
This is the filename on the server. Make sure that the workflow you want to execute is available on the server.
List the variables that are being reported back when the asynchronous status service is queried
The name of the variable which will contain the content body of the service call