Auditing is the ability of the engine to let the user configure the collection and the retrieval of events relative to the runtime process execution. We introduced auditing and BAM in Chapter 4, Operation Management, and now, we are going to see how to leverage the engine services to implement auditing at various levels.

When persistence is enabled, ready-to-use preconfigured AuditService (implemented by JPAAuditLogService) can be borrowed from RuntimeEngine; it returns process, node, and variable runtime audit data (see the class diagram) from the three standard jBPM auditing database tables (ProcessInstanceLog, NodeInstanceLog, and VariableInstanceLog). The audit service stamps each log entry with an OwnerID attribute, which matches the unique identifier of its RuntimeManager.

AuditLogService auditservice=engine.getAuditLogService();
List<ProcessInstanceLog> pizzadeliveryLogs= auditservice.findActiveProcessInstances("pizzadelivery");

This AuditService usage approach...