Human Task Artifact Deployment

Human Task Deployment

Each Human Task artifact is a zipped file with all relevant deployment artifacts. It should contain the task deployment descriptor, one or more human task definitions (.ht files), WSDL and JSPs files for rendering task input and output. The task deployment descriptor is a file named htconfig.xml (see the next paragraph for its description).

During deployment, the task engine loads all documents from the deployment descriptor. Loading documents allow it to reference tasks, service and schema definitions using fully qualified names, and import based on namespaces instead of locations.

Two ways to deploy a task in WSO2 Business Process Server

  1. Using the WSO2 Business Process Server Web Management Console

    Login to BPS Management Console by providing your credentials (default:- user:admin pass:admin). Go to Add menu item under the Human Tasks section of the left pane of the Management Console.

    Add Human Task

    Browse and select the zipped Human Task archive. You can upload multiple task artifacts in a single upload using the + button and selecting artifacts one after another.

    Add Human Task


  2. Manually copying the zipped task artifact file

    To deploy manually, just copy the zipped task definition file containing your artifacts, to the BPS_HOME/repository/deployment/server/humantasks directory. In this case, you need to be aware of the structure of the zipped task configuration. The deployment descriptor (i.e. htconfig.xml file) should be in the root of the zip.

Listing HumanTask Artifacts

Once you have uploaded a human task artifact, it will be listed under the human task package listing page. Go to Manage > HumanTasks > List from the management console. (Refer the image below:)

List Human Task packages

UpDeploying a HumanTask Artifact

You can un-deloy a Human Task artifact using the Undeploy link in the package details page. You can navigate to the package details by clicking on the package name on the the package listing page.

NOTE: Once you un deploy a human task package, all the task instances related to that package will be sent to Obsolete state.

List Human Task packages