|Re: Business Process Monitoring - Event based [message #1081631 is a reply to message #1081613]
||Wed, 07 August 2013 09:34
| Kunal Suri
Registered: April 2013
Kunal Suri wrote on Wed, 07 August 2013 09:07|
We have been experimenting with the QueryService (pull model) for monitoring of the data coming form the Process.
This type of monitoring is more sort of a reporting monitoring as scans the Audit trail and tells about the status and various metrics of the Activities like when were they started, which state are they in etc.
I followed the wiki page of Stardust Java API's to get these values. 
This discussion is a continuation of the Business Process Monitoring thread  but I want to know some more technical details and thus started this thread.
The drawback of the Pull monitoring technique is that we need to run the Audit trail and then retrieve the data, but now we need to consider other constraints and monitor a process or activity on that bases:
1. The SLA for a process completion is 45 sec. and it is taking more that this time?
2. The Activity should be completed in 60 millisec but its taking more?
We need to have a program that sends alerts on such problematic situation?
I am not sure of the Working With Activity Event Handlers  could solve this problem?
Also, I tried to see the IWorklistMonitor (Package org.eclipse.stardust.engine.core.spi.monitoring) but I feel it only for activities that need a manual intervention. What about Application Activities ?
For example, a Process has an application activity and it uses a web service WSDL and the web service is down thus the activity would not be completed and should send a alert to the monitoring program, so that the technical staff could look into it?
Thanks for your time!
Also, something about a ProcessExecutionMonitor was mentioned in the thread  but I am not able to find any reference document on it?
So, if we get events when a Application or Manual Activity starts and completes using a Java API it will help us to monitor our activities better.
|Re: Business Process Monitoring - Event based [message #1115496 is a reply to message #1097973]
||Tue, 24 September 2013 03:16
| Andreas Mueller
Registered: October 2011
you can register implementations of IProcessExecutionMonitor, IWorklistMonitor, IRuntimeEnvironmentMonitor or IPartitionMonitor via META-INF/services contract. Just place a file with fully qualified class name of one of above Monitor interfaces into META-INF/services. The file itself should contain the fully qualified name of the class that implements the corresponding monitor.
e.g. file name org.eclipse.stardust.engine.core.spi.monitoring.IProcessExecutionMonitor with content org.eclipse.stardust.custom.MyProcessExecutionMonitor.
If for example a process instance is started, the callback method void processStarted(IProcessInstance process); of MyProcessExecutionMonitor is called. So you can react on this event and do whatever you need to do.
There are several other events such as process instance completion, process instance abortion, model deployment, model deletion, any worklist changes of activity instances, etc. I hope that helps to get started.
Powered by FUDForum
. Page generated in 0.07376 seconds