1 Reply Latest reply on Mar 24, 2014 2:31 AM by Maciej Swiderski

    Can I create more tables in JBPM database and associate them with History logging?

    Ritu SJ Newbie

      Hi salaboy21, swiderski.maciej and others,

      It seems we may need more information to be saved in the jBPM database. We are planning to use correlation key for identification of instance data based on our job.

      Can i create and associate more tables in jBPM database for selective History logging? We have to use this information to inform our server about the Asynchronous operations etc going on through Engine. So basically some data which is not jBPM specific but our process specific.

      Also, how long can i retain History? Can i do pruning based on a timeline?

       

      Thanks,

      Ritu

        • 1. Re: Can I create more tables in JBPM database and associate them with History logging?
          Maciej Swiderski Master

          you can freely extend logging capabilities by adding your own process event listener that will be registered on ksession and task lifecycle listener for task operations. These listeners then can log as many information as needed to custom tables (remember to define entities in persistence.xml so they will be seen for the entity manager.

           

          When it comes to clean up of history log, currently it is up to you to clean it up and to decide when to do so. jBPM does not provide API for such operations, mainly due to extensibility available here - we cannot ensure all is cleaned up if it was extended.

           

          HTH

          1 of 1 people found this helpful