Skip to end of metadata
Go to start of metadata

The BPMN Quick Start guide explains how to set up and start the WSO2 BPS and model a BPMN process. The guide has the following sections.

Setting up and starting BPS

WSO2 BPS setup is very simple. While more details of the installation can be found in the Installation Guide section, this guide provides a basic summary to get you started fast.

  1. Ensure that the following are installed in your environment.
    • JDK 7 or 8.
    • JAVA_HOME environment variable is set to <JDK_HOME>. For example, JAVA_HOME=c:\Program Files\java\jdk1.7.0_71
  2. Download the BPS binary distribution from http://wso2.com/products/business-process-server/.
  3. Extract the zip file to a folder which will be referred to as <PRODUCT_HOME> throughout the rest of this guide.
  4. Open a command prompt (or a shell in Linux) and go to the <PRODUCT_HOME>\bin directory.
  5. Start the BPS server by executing wso2server.sh (or wso2server.bat in Windows).
  6. The operation log keeps running until the server starts, which usually takes several seconds. Wait until the server fully boots up and displays a message similar to "WSO2 Carbon started in n seconds."

Modeling a BPMN process

  1. Download and setup the WSO2 Business Process Server tooling plug-in with Eclipse

  2. Under the Help menu, click Install New Software. In the resulting panel, click the Add button to add a repository and fill in the following fields:

    Fill in the following repository details for BPMN.
  3. Click OK to add the plugin. Once this is done, click Finish and restart Eclipse.
  4. Once Eclipse restarts, navigate to File > New > Other. From the window that appears select Activiti > Activiti Project and click Next
  5. Provide a suitable Project Name and click Finish

  6. Right-click on your project and navigate to New > Other.

  7. From the window that appears, select Activiti > Activiti Diagram.

  8. Select the project in the viewer and enter a File name.

    Tip: The following example expands on creating a business process scenario, The manager invokes an order approval process where it is possible to set the product ID. Additionally, an employee from a good division can set the quantity and the unit price of the product. The quantity and the unit price are used to calculate the total cost. If the total cost is above 100,000, the order will have to be approved by an employee from the orderApproval Group before the order mail is dispatched. Alternatively, if the cost is below 100,000, the order mail is dispatched without approval. In this example, the process is named “OrderApproval”.

  9. Click Finish. You are presented with a canvas as shown below to model your BPMN package.

    The palette is positioned on the right side of the screen. You can drag and drop models from the palette onto the canvas and do your modelling.
  10. To implement the OrderApproval, drag and drop a Start Event element, two User Task elements, a Mail Task element and a Terminate Event element on the canvas.
  11. Link up the flow according to the business logic. 

    Tip: According to the business logic in this example, the Start Event should trigger the Fill Order Form User Task. So connect the Start Event to the Fill Order Form User Task.

  12. In the Connection tab, select Sequence Flow. Connect the Start Event to the Fill Order Form User Task.

    Tip: It is useful to understand the condition logic for this sequence. Here, if the total cost calculated from the quantity and unit price is above 100,000 a user task has to be executed or the mail task comes into play. In order to add this condition statement, click on the Fill Order Form User Task and you will be able to see few tooltips hovering around the Fill Order Form User Task on the canvas. The diamond shape with a cross in the middle implies an Exclusive Gateway.

  13. Select the Fill Order Form User Task by clicking on it and click on the Exclusive Gateway tooltip on the right of the tool.
  14. Once you click the Exclusive Gateway, a bigger diamond with a cross in the middle should appear on the canvas next to the Fill Order Form User Task. The Fill Order Form User Task will point to it. 
  15. The rest of the flow is fairly straightforward. Use the Sequence Flow to connect the tools and the final diagram will be similar to what is shown below.

    After the diagram has been constructed, you must configure the properties of each element to fulfil the business logic.
  16. Click on the Start Event element and set the following properties in the general tab.

    • Id: fillOrderDetails

    • Name: Enter Order Details

  17. To get the order details, you must create a form to get the product ID from the manager who invokes the process. Click on the Form tab in the properties of the Start Event.
  18. Click on the New button and use the new window as shown below to create a productID field.

    Ensure that you enter the following details.
    • Id: productID

    • Name: Product Id

    • Type: string

    • Variable: productID

  19. Click OK. Once you have filled the form, the table in the form tab should look similar to the following.

    Now that the configurations for the start event have been set, you can configure the Fill Order Form User Task, which is a claimable task by the goods division, where an employee of the goods division will be able to claim and complete the form. 
  20. Click on the Fill Order Form User Task. In the Properties tab, assign an Id and Name, similarly to how you assigned a Id and Name to the start event. You can use the following values.
    • Id: fillOrderForm

    • Name: Fill Order Form

  21. Click on the Main Config tab in the Properties pane. Since there is no specific user who the task is to be assigned and anyone from the goods division can claim the task and execute it, set the Candidate Group to goodsDivision. This is will allow any employee under the goods division to claim and complete the task.
  22. Create the form that the employee needs to fill. To do this, click on the Form tab in the Properties pane. Add the following fields in a similar manner to how you added form attributes for the start event.

    NameProduct IDQuantityUnit Price

    Once the above fields are added to the form, the table in your Form tab should look similar to the following.

  23. Now that you have configured your Fill Order Form User Task, you can identify the two flows. There can be a default flow and a conditional flow.

    1. To assign the default flow, set an appropriate ID for the flow, which is the Sequence Flow element from the exclusive gateway to mail task. Click on this flow.
    2. Set the Id value as shown below.
  24. Similarly, assign an ID to the Sequence Flow from the exclusive gateway to the Approve Order User Task.
    • Id: approveOrder
  25. To set orderProduct as the default flow, do the following.
    1. Click on the exclusive gateway. 
    2. Click the General tab in the Properties pane and select orderProduct in the dropdown to assign it.
  26. To assign the Conditional flow, click on the approveOrder Sequence Flow element, navigate to the Main Config tab. In the condition field, define the condition as ${(quantity*unitPrice) > 100000}. This is for calculating the total cost and checking if it exceeds 100,000. If it does, it will take the conditional flow.

    You have now configured the conditional flow. If the total cost exceeds 100,000, the flow is directed to the Approve Order User Task.
  27. To configure the Approve Order User Task, do the following. 

    1. Click on the Approve Order User Task. 

    2. In the General tab, assign an appropriate ID and Name. 

    3. In the Main Config tab, you must set the Candidate Group as the “orderApproval” group, as according to the scenario, anyone from the order approval group can claim the task and complete the task. 

    4. To allow the approver to view the order details, you must create a form to display the Product ID, Quantity and Unit Price. To do this, navigate to the Form tab in the Properties pane and create the fields as show in the diagram below.

      Note: The fields are only readable.


  28. Now you have configured the properties for the Approve Order User Task. To accommodate a scenario for the orderApproval group rejecting an order, you must add an end event to this User Task. Therefore this process can terminate at Approve Order User Task.
  29. To configure the Mail Task, do the following. 
    1. Click on the Order Product Mail Task. In the Properties pane, select the General tab.
      • Id: mtOrderProduct

      • Name: Order Product

    2. Select the Main Config tab, and fill the respective fields (i.e., To, From, Subject). 
    3. In the non-HTML field, enter “Order ${quantity} of ${productID} at the rate of ${unitPrice}”. The variable will be used to create the mail body.
    4. Follow the instructions on the Working with the Email Task page to configure the server for the Mail Task. 
    The model is now complete as the necessary logic has been applied.
  30. To create the Business Archive File (.bar), do the following.

    1. On the Explorer, found in the upper left of your screen, navigate to Package Explorer

    2. Right click on the package and select “Create deployment artifacts”.

    3. Navigate to the location of the source. You will find the .bar file inside the deployment folder.

  • No labels