Skip to main content

How to see the execution flow of BPMN in WSO2 BPS

The latest version of WSO2 BPS 3.5.1, does not provide a mechanism to see the execution flow of BPS process. you can understand the flow enabling debug logs of acitivi engine.

Go to <BPS_HOME>/repository/conf/log4j.properties and add the following

log4j.logger.org.activiti=DEBUG
log4j.logger.org.activiti.engine.impl.db=INFO
log4j.logger.org.activiti.engine.impl.persistence=INFO
log4j.logger.org.activiti.engine.impl.cfg.standalone=INFO
log4j.logger.org.activiti.engine.impl.interceptor.LogInterceptor=INFO
log4j.logger.org.activiti.engine.impl.history.DefaultHistoryManager=INFO
log4j.logger.org.activiti.engine.impl.jobexecutor.AcquireJobsRunnable=INFO
view raw log4j_config_2 hosted with ❤ by GitHub
But it provides the current state of execution flow with the instance view of WSO2 BPS

login to WSO2 BPS
Go to Main->Manage -> Instances ->BPMN


WSO2 BPS
http://wso2.com/products/business-process-server/

WSO2 BPS documentation
https://docs.wso2.com/display/BPS351/WSO2+Business+Process+Server+Documentation

Comments

I just want to thank you for sharing your information and your site or blog this is simple but nice Information I’ve ever seen i like it i learn something today. BPMN

Popular posts from this blog

How to generate random unique number in SOAP UI request

eg 1: ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} eg 2: ${=java.util.UUID.randomUUID()} ${=java.util.UUID.randomUUID()} ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf ${=System.currentTimeMillis() + ((int)(Math.random()*10000))} - See more at: http://tryitnw.blogspot.com/2014/03/generating-random-unique-number-in-soap.html#sthash.m2S4tUFu.dpuf

Tips on using environment variables in WSO2 Integration Cloud

Environment variables allow you to change an application's internal configuration without changing its source code. Let’s say you want to deploy the same application in development, testing  and production environments. Then database related configs and some other internal configurations may change from one environment to another. If we can define these configurations as an environment variables we can easily set those without changing the source code of that application. When you deploy your application in WSO2 Integration Cloud, it lets you define environment variables via the UI. Whenever you change the values of environment variables, you just need to redeploy the application for the changes to take effect. Predefined environment variables Key Concepts - Environment Variables   provides you some predefined set of environment variables which will be useful when deploying applications in WSO2 Integration Cloud. Sample on how to use environment variables ...

Generate a file using the request payload and send to a backend via WSO2 ESB

Let's say WSO2 ESB receives an request with a payload, and we need to create a file using that payload content and send that file to a endpoint. Here's the required proxy cofiguration. This sequence builds the message as a multipart/form-data and send it to the endpoint. If you want to customise MultipartFormDataFormatter, write your own class extending MultipartFormDataFormatter. Configure it in WSO2_ESB/repository/conf/axis2/axis2.xml file as follows. This org.wso2.custom.CustomMultipartFormDataFormatter sets the file name as filename.xml, Content-Type as text/xml and payload as the content of the file