[jboss-jira] [JBoss JIRA] Commented: (JBPM-2) process monitoring and statistics capabilities (BAM)

[Arjan van Bentem (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBPM-2?page=comments#action_12357894 ] 
            
Arjan van Bentem commented on JBPM-2:
-------------------------------------

And *maybe* related if it comes to an implementation: I'd like a way to get the full-blown history of a process instance, for example to get all task instances that have been completed so far. For me, this would also need to support sub-processes, loops and maybe even tokens that somehow have been moved to a specific point by an administrator...

I think that GraphElement#getParents() cannot be used to get the full task history, as (as far as I can tell) that would not know about loops, nor would support sub-processes that have been assigned at runtime (like when a process-state has no sub-process defined in its XML definition, and is somehow selected and set at runtime).

Currently the logs can (probably) be used to build such chain, like by using LoggingSession#findLogsByProcessInstance. Given these details one can manually recreate the task instance objects, et cetera, to display information. If I ever get to that I'll share it...

Arjan.

> process monitoring and statistics capabilities (BAM)
> ----------------------------------------------------
>
>                 Key: JBPM-2
>                 URL: http://jira.jboss.com/jira/browse/JBPM-2
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>          Components: Core Engine
>         Environment: N/A
>            Reporter: Ronald van Kuijk
>            Priority: Blocker
>
> JBoss jBPM should provide information on how processes are or have been running. Some people would call this BAM (Business Activity Monitoring), some call it BI (Business Intelligence) Some info can be found on http://www.javareport.com/article.asp?id=9238 and http://bizintelligencepipeline.com/howto/showArticle.jhtml?articleId=49900689
> 1.  jBPM should store the duration and start date of a state/process in the logs
> 2.  Write some detailed info on wiki
> 3.  Show processinstance and data
> 4.  day/week/month overviews
> 5.  near realtime data per process
> 6.  produce graphs of day/week/month overviews
> Some more ideas i got from a requirements document...
> -  Number of cases processed in through a particular process definition
> -  Number of cases flowing through a particular activity
> -  Longest work item delay by activity
> -  Workitems awaiting a particular task
> -  Workitems in a specific worklist claimed and/or completed by a particular user
> -  Longest end-to-end delay
> -  Mean time to approve by activity by participant
> -  Mean end-to-end completion time.
> as background info, here's what the competition says about BAM:
> http://appian.com/AppianEnt/Analytics/analytics.html
> http://www.webmethods.com/meta/default/folder/0000005936
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/introduction/htm/ebiz_intro_story_piew.asp
> http://www.tibco.com/software/business_optimization/activity_monitoring.jsp?m=c1
> http://www.vitria.com/products/platform/bam.html
> http://looselycoupled.com/glossary/BAM

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira