Skip to end of metadata
Go to start of metadata

This section explains how to attach a custom workflow to the API subscription operation in the API Manager. First, see Workflow Extensions for information on different types of workflows executors.

Attaching a custom workflow to API subscription enables you to add throttling tiers to an API that consumers cannot choose at the time of subscribing. Only admins can set these tiers to APIs. When a consumer subscribes to an API, he/she has to subscribe to an application in order to get access to the API. However, when API subscription workflow is enabled, when the consumer subscribes to an application, it initially is in the On Hold state, and he/she can not use the API, using its production or sandbox keys, until their subscription is approved. 

Before you begin, if you have changed the API Manager's default user and role, make sure you do the following changes:

  • Point the database that has the API Manager user permissions to BPS.
  • Share any LDAPs, if exist.
  • Unzip the <API-M>/business-processes/subscription-creation/HumanTask/SubscriptionsApprovalTask-1.0.0.zip file, update the role as follows in the SubscriptionsApprovalTask.ht file, and ZIP the SubscriptionsApprovalTask-1.0.0 folder.

    <htd:argument name="role">

Configuring the Business Process Server

  1. Download WSO2 Business Process Server.  
  2. Set an offset of 2 to the default BPS port in <BPS_HOME>/repository/conf/carbon.xml file. This prevents port conflicts that occur when you start more than one WSO2 product on the same server. Also see Changing the Default Ports with Offset. 


    Tip: If you change the BPS port offset to a value other than 2 or run the API Manager and BPS on different machines (therefore, want to set the hostname to a different value than localhost), you do the following:

    • Search and replace the value 9765 in all the files (.epr) inside the <API-M_HOME>/business-processes folder with the new port (9763 + port offset.)

  3. Open the  <BPS_HOME>/repository/conf/humantask.xml  file and  <BPS_HOME>/repository/conf/b4p-coordination-config.xml  file and set the  TaskCoordinationEnabled  property to true.

  4. Copy the following from <API-M_HOME>/business-processes/epr to <BPS_HOME>/repository/conf/epr folder. If the <BPS_HOME>/repository/conf/epr folder isn't there, please create it.

    Make sure to give the correct credentials in the  <BPS_HOME>/repository/conf/epr  files.

    • SubscriptionService.epr
    • SubscriptionCallbackService.epr
  5. Start the BPS server and sign in to its management console (https://<Server Host>:9443+<port offset>/carbon).  

  6. Select Add under the Processes menu and upload the <API-M_HOME>/business-processes/subscription-creation/BPEL/SubscriptionApprovalWorkFlowProcess_1.0.0.zip file to BPS. This is the business process archive file.
  7. Select Add under the Human Tasks menu and upload the <API-M_HOME>/business-processes/subscription-creation/HumanTask/SubscriptionsApprovalTask-1.0.0.zip file to BPS. This is the human task archived file.

Configuring the API Manager

Open the <API-M_HOME>/repository/deployment/server/jaggeryapps/admin/site/conf/site.json file 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 API subscription workflow.

  1. Sign in to API Manager Management Console (https://<Server Host>:9443/carbon) and select Browse under Resources.

  2. Go to the /_system/governance/apimgt/applicationdata/workflow-extensions.xml resource, disable 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).  

        <SubscriptionCreation executor="org.wso2.carbon.apimgt.impl.workflow.SubscriptionCreationWSWorkflowExecutor">
             <Property name="serviceEndpoint">http://localhost:9765/services/SubscriptionApprovalWorkFlowProcess/</Property>
             <Property name="username">admin</Property>
             <Property name="password">admin</Property>
             <Property name="callbackURL">https://localhost:8243/services/WorkflowCallbackService</Property>

    Note  that all workflow process services of the BPS run on port 9765 because you changed its default port (9763) with an offset of 2.

    The application creation WS Workflow Executor is now engaged.

  3. Go to the API Store Web interface and subscribe to an API.
    It invokes the API subscription process and creates a Human Task instance that holds the execution of the BPEL until some action is performed on it.
  4. Note the message that appears if the BPEL is invoked correctly, saying that the request is successfully submitted. 

  5. Sign in to the Admin Portal (https://<Server Host>:9443/admin), list all the tasks for API subscription and approve the task. It resumes the BPEL process and completes the API subscription.

  6. Go back to the API Store and see that the user is now subscribed to the API.

    Whenever a user tries to subscribe to an API, 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">

     Elements of the above configuration are described below:

    Name of the API to which subscription is requested.
    Version of the API the user subscribes to.
    Context in which the requested API is to be accessed.
    Provider of the API.
    Name of the user requesting subscription.
    Name of the application through which the user subscribes to the API.
    Throttling tiers specified for the application.
    workflowExternalRefThe unique reference against which a workflow is tracked. This needs to be sent back from the workflow engine to the API Manager at the time of workflow completion.

    The URL to which the Workflow completion request is sent to by the workflow engine, at the time of workflow completion. This property is configured under the callBackURL property in the workflow-extensions.xml file.

  • No labels