Following model Jaggery scripts located in the
<BPS_HOME>/wso2/business-process/repository/deployemnt/server/jaggeryapps//bpmn-explorer/controller/ directory retrieve data from the BPMN REST API to display. It sends AdminServices requests to the back-end and retrieves data to render data in the HTML page.
View Jaggery files with respect to each page of the web app are located in the
<BPS_HOME>/wso2/business-process/repository/deployemnt/server/jaggeryapps//bpmn-explorer/template/ directory. They contain information on rendering the HTML body of the information retrieved in the associated Model.
Controller files are used to connect the Jaggery scripts that generate subparts of each page. Controller Jaggery files with respect to each page of the web app are located in the
<BPS_HOME>/wso2/business-process/repository/deployemnt/server/jaggeryapps/bpmn-explorer/controller/ directory. When the server receives a request, it maps it to a particular controller via URL mappings as follows.
Loading the process diagram
wsRequest.js file loads the BPMN process diagram for the corresponding process instance in the BPMN Explorer. This avoids the need to authenticate again when viewing the process diagram. It contains following methods.
You can deploy the BPMN Explorer in an external server other than WSO2 EI. Herein, you need to configure the WSO2 EI server location in the config.json file located in the
<BPS_HOME>/wso2/business-process/repository/deployment/server/jaggeryapps/bpmn-explorer/config/config.json file. Also, you need to configure the tenant domain in this file if you use the tenant mode of the server.