1. The jBPM web app has some monitoring pages that give the global perspective
of the deployed process and each specific instance. By default you need no role
to see them, i.e. everyone can see them. Assuming access to your database is
protected, you can limit access to those pages using the security mechanisms
defined in the servlet spec.
2. Obtain the LoggingSession from the JbpmSession in v3.0.x or JbpmContext in
v3.1. Use the methods there to obtain the log entries for a whole process
instance or a specific token. The log entries are instances of ProcessLog,
which is an abstract class. Its concrete subclasses (TokenCreateLog, NodeLog,
TaskLog...) give you all the information captured by jBPM about the process
executions.
Alternatively, you can use Hibernate to query the database directly and extract
useful information, such as the average time spent in a task.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3923177#3923177
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3923177
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
