Hi Isuru, On Thu, Jul 30, 2015 at 11:57 AM, Isuru Wijesinghe <[email protected]> wrote:
> Hi all, > > I already developed back-end component of $subject as my fast track > training project and now I have planned to extend this with the front-end > part (console UI component). Below I briefly describe the project > description and features available there. > > *Description* > > Execution data on process instances has to be captured for analyzing the > behavior of processes. In order to facilitate this, execution data of BPMN > process instances has to be published to WSO2 DAS. Once published, such > data can be analyzed and presented from DAS. > > This data publishing component can run independent of the process runtime > and access instance data using the activiti engine Java API. > > *Back-end component* > > Two streams are provided for publishing the the events of completed BPMN > process and task Instances to the DAS.. > > process.instance.stream: process_instance_id, start_activiti_id, > start_user_id, start_time, end_time, duration > > task.instance.stream: task_instance_id, process_instance_id, start_time, > complete_time, assignee, duration. > > *Front-end component* > > In the UI, user can configure the thrift url, user name and password. In > addition to that it provides the configuration to select set of attributes > which belongs to the both process and task instances to create two steams > for publishing the attributes as events to DAS. > > Here it has predefined set of check boxes with attribute names and user > can able to select attributes. Once they selected some attributes to > initialize the two streams those are automatically disabled from the UI > Here why do we need to disable them? Shouldn't user be able to change them later? (On a related note, if you want to disable such things, disabling it from UI only is not enough because backend service can be invoked from other clients as well.) I saw in a different email to dev@ from you, saying your next plan is to support multiple versions of these stream definitions. So, with that I believe you can get rid of this attribute disabling thing too. Thanks, Bhathiya > and stored in the configuration registry as properties. From the back-end > side read those properties and create streams to publish data as events to > DAS. > > for More Details about the back-end component click here > <https://docs.google.com/document/d/1uwRm5bhC3ShJ1fh-7Nqkq31UFQI-U4-x22bLK2XYRCM/edit#> > . > -- > Isuru Wijesinghe > *Software Engineer* > Mobile: 0710933706 > [email protected] > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Bhathiya Jayasekara* *Senior Software Engineer,* *WSO2 inc., http://wso2.com <http://wso2.com>* *Phone: +94715478185* *LinkedIn: http://www.linkedin.com/in/bhathiyaj <http://www.linkedin.com/in/bhathiyaj>* *Twitter: https://twitter.com/bhathiyax <https://twitter.com/bhathiyax>* *Blog: http://movingaheadblog.blogspot.com <http://movingaheadblog.blogspot.com/>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
