Creating a Custom History Backend

[Rob_LM]

A further part of our Camunda evaluation involves looking at how we can send process engine events into our own auditing systems. Having perused the documentation, creating a custom history backend would seem the way to go. The documentation leaves us a little wanting in this respect and we have the following questions:

1. Is our CustomHistoryHandler implemented as a plug-in, in the same respect that the example CustomerHistoryLevel example is? If not, how is this implemented and configured?

2. What configuration files do we need to modify, particularly any in addition to those associated with a plug-in.

3. Are there any examples in this respect?

We are using the “out-of-the-box” Camunda Tomcat installation.

Any help and guidance is gratefully received.

Kind regards,

Rob

[thorben]

Hi @Rob_LM,

@Rob_LM

Is our CustomHistoryHandler implemented as a plug-in, in the same respect that the example CustomerHistoryLevel example is? If not, how is this implemented and configured?

A history handler can be registered with a process engine via a process engine plugin, the same way you would do it with a history level.

@Rob_LM

What configuration files do we need to modify, particularly any in addition to those associated with a plug-in.

Please see Process Engine Plugins | docs.camunda.org.

@Rob_LM

Are there any examples in this respect?

None that I am aware of.

Cheers,
Thorben