Adding a User Signup Workflow
This section explains how to attach a custom workflow to the user signup operation in the API Manager. First, see Workflow Extensions for information on different types of workflow executors.
Configuring the API Manager
Open the
<API-M_HOME>/repository/deployment/server/jaggeryapps/admin/site/conf/site.jsonfile and configure "workFlowServerURL"under "workflows"to point to the BPS server (e.g."workFlowServerURL": "https://localhost:9445/services/")
Engaging the WS Workflow Executor in the API Manager
First, enable the user signup workflow.
Log in to APIM management console (
https://<Server Host>:9443/carbon) and select Browse under Resources.
Go to
/_system/governance/apimgt/applicationdata/workflow-extensions.xmlresource, d isable the Simple Workflow Executor and enable WS Workflow Executor. Also specify the service endpoint where the workflow engine is hosted and the credentials required to access the said service via basic authentication (i.e., username/password based authentication).<WorkFlowExtensions> ... <UserSignUp executor="org.wso2.carbon.apimgt.impl.workflow.UserSignUpWSWorkflowExecutor"> <Property name="serviceEndpoint">http://localhost:9765/services/UserSignupProcess/</Property> <Property name="username">admin</Property> <Property name="password">admin</Property> <Property name="callbackURL">https://localhost:8243/services/WorkflowCallbackService</Property> </UserSignUp> ... </WorkFlowExtensions>Go to the API Store Web interface and sign up.
It invokes the signup process and creates a Human Task instance that holds the execution of the BPEL until some action is performed on it.Note the message that appears if the BPEL is invoked correctly, saying that the request is successfully submitted.
Log in to the Admin Portal (
https://<Server Host>:9443/admin) and approve the user signup task. It resumes the BPEL process and completes the signup process.Go back to the API Store and see that the user is now registered.
Whenever a user tries to sign up to the API Store, a request of the following format is sent to the workflow endpoint:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wor="http://workflow.subscription.apimgt.carbon.wso2.org"> <soapenv:Header /> <soapenv:Body> <wor:registerUser xmlns:wor="http://workflow.registeruser.apimgt.carbon.wso2.org"> <wor:userName>sampleuser</wor:userName> <wor:tenantDomain>foo.com</wor:tenantDomain> <wor:workflowExternalRef>c0aad878-278c-4439-8d7e-712ee71d3f1c</wor:workflowExternalRef> <wor:callbackURL>https://localhost:8243/services/WorkflowCallbackService</wor:callBackURL> </wor:registerUser> </soapenv:Body> </soapenv:Envelope>Elements of the above configuration are described below: