This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.
Extending Application Publishing Workflow
You can attach a custom workflow for the Web application publishing process in WSO2 App Manager, with the integration of WSO2 BPS as follows.
Configuring WSO2 Business Process Server
Follow the steps below to configure WSO2 BPS to extend the publishing workflow of a Web app.
- Download WSO2 Business Process Server. Â Â
Enter
2
as the value of the<Offset>
element in theÂ<BPS_HOME>/repository/conf/carbon.xml
file, to set a port offset of 2Â to the default WSO2 BPS port. Â Â ÂThis prevents port conflicts that occur when you start more than one WSO2 products on the same server.Â
If you change the port offset of WSO2 BPS to a value other than 2, or run the App Manager and BPS on different machines (hence to set the hostname to a different value than localhost), you must do the following.
Search and replace the value 9765 (i.e. the default value), in all the (.epr) files inside the
<AppM_HOME>/business-processes/epr/
directory with the new offset value of the WSO2 BPS port.Search and replace port 9445 (i.e. the default value), in the
<
AppM_HOME
>/repository/deployment/server/jaggeryapps/admin-dashboard/site/conf/site.json
file with the new offset value of the WSO2 BPS port accordingly.Change the hard-coded endpoints of default APIs, and the port of the Workflow Callback Service as described in Changing the Default Ports with Offset.
Create a directory named
eprÂ
inside theÂ<BPS_HOME>/repository/conf/
directory.Copy the following files from
<AppM_HOME>/business-processes/epr/
directory to<BPS_HOME>/repository/conf/epr/
directory.PublishApplicationService.epr
PublishAPPCallbackService.epr
Start WSO2 BPS server, and log in to its management console using the following URL: https://<BPS_HOST>:<BPS_PORT>/carbon.
- In the Main menu, click Add under Processes.
- Click Choose File, and select theÂ
<AppM_HOME>/business-processes/publish-application/BPEL/PublishAPPApprovalWorkFlowProcess_1.0.0.zip
file, to upload the business process archive file as follows.
- Click Upload.
- In the Main menu, click Add under Human Tasks.
- Click Choose File, and select theÂ
<AppM_HOME>/business-processes/publish-application/HumanTask/PublishAppApprovalTask-1.0.0.zip
 file, to upload the human task archive file as follows.
- Click Upload.
Configuring WSO2 App Manager
Follow the steps below to configure WSO2 AppM to extend the publishing workflow of a Web app.
Start WSO2 AppM server, and log in to its management console using the following URL: https://<AppM_HOST>:<AppM_PORT>/carbon.
- In the Main menu, click Browse under Resources.
- Navigate to
/_system/governance/appmgt/applicationdata/workflow-extensions.xml
file as shown below.
- Click Edit as Text.
Comment the default
PublishAPPSimpleWorkflowExecutor
, and comment out thePublishAPPWSWorkflowExecutor
 as shown below.<!--publishapp executor="org.wso2.carbon.appmgt.impl.workflow.PublishAPPSimpleWorkflowExecutor"--> <PublishAPP executor="org.wso2.carbon.appmgt.impl.workflow.PublishAPPWSWorkflowExecutor"> <Property name="serviceEndpoint">http://localhost:9765/services/PublishAppApprovalWorkFlowProcess/</Property> <Property name="username">admin</Property> <Property name="password">admin</Property> <Property name="callbackURL">https://localhost:8243/services/WorkflowCallbackService</Property> </PublishAPP>
- 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) in the above configuration.
- Click Save Content.
Trying out the workflow configuration
Follow the steps below to try out the workflow configuration enabled above on publishing a Web application.
Start WSO2 AppM server, and log in to its management console using the following URL: https://<AppM_HOST>:<AppM_PORT>/carbon.
- Create a user with the
internal/creator
role. For instructions on creating a user, see Configuring Users. - Log in to the App Publisher as the creator user created above using the following URL: http://<AppM_HOME>:<AppM_PORT>/publisher
Create a Web Application. For instructions on creating a Web app, see Creating Web Applications.
When you submit the Web app for review after creating it, this action invokes the Web application publishing process and creates a human task instance that holds the execution of the BPEL process until you perform some action on it. Even if you log in as a user with the internal/publisher role, the Approve or Reject buttons will not appear as shown below. This is because, the publisher does not have the control of approving or rejecting the application while they are waiting for admin approval or rejection.
- Create a user with theÂ
internal/admin
 role. For instructions on creating a user, see Configuring Users. - Log in to the WSO2 AppM admin dashboard as the admin user created above using the following URL: https://<AppM_HOME>:<AppM_PORT>/admin-dashboard
- Click Pending Workflows, and then click Published Applications.
- Select Approve on the corresponding Web app in the Approval Tasks list as shown below, and click Complete.
- Create a user with theÂ
internal/publisher
 role. For instructions on creating a user, see Configuring Users. - Log in to the App Publisher as the publisher user created above using the following URL: http://<AppM_HOME>:<AppM_PORT>/publisher
- Now you can click Publish to publish the approved app as shown below.