Workflow web services build on top of the existing Cúram web services support. In particular the workflow engine requires a Business Process Object (BPO) modeled as a Document Oriented Web Service (see the Cúram Inbound Web Services chapter of the Cúram Modeling Reference Guide for details).
The web service BPO is just a front end to the workflow enactment API (curam.util.workflow.impl.EnactmentService). This being the case only one such BPO is required per application. An appropriate BPO is already provided in the Cúram application: Logical View::MetaModel::Curam::Facades::
Workflow::WebService::WorkflowProcessEnactment.
To use workflow web services the BPO named Logical View::MetaModel::Curam::Facades::
Workflow::WebService::WorkflowProcessEnactment must be assigned a server component of stereotype webservice.
Cúram web services can be customized in other ways for example making them secure using WS-Security as described in the Secure Web Services chapter of the Cúram Modelling Reference Guide. All customizations for workflow web services must be made to this BPO.