2 Replies Latest reply on Jul 26, 2012 8:42 AM by acarpine

    jBPM and Human task schema

    acarpine
    acarpine Jul 26, 2012 4:05 AM

      Dear Community,

      configuring the persistence for the human task (using the service and the webapp) I observed that in one case is used a specific schema (task) while the webapp uses the same schema of the jBPM data model.

       

      Although using two different databases (one for jBPM and another for user tasks) seems a sensible approach is there any good reason for not to use a single db?

      What about the performances?

       

      thanks

        • 1. Re: jBPM and Human task schema
          salaboy21
          salaboy21 Jul 26, 2012 4:19 AM (in response to acarpine)

          Performance is the main reason to keep them decoupled.

          Your Task List will interact against the Task Database instead of affecting the process schemas. So if you have a large amount of users hitting refresh in their task lists the process engine doesn't need to know about. You can configure both persistence mechanism to  use the same DB if you want.

           

          CHeers

          1 of 1 people found this helpful
            • Actions
          • 2. Re: jBPM and Human task schema
            acarpine
            acarpine Jul 26, 2012 8:42 AM (in response to salaboy21)

            Many thanks Mauricio.

            Is it correct said that another good reason to have them separated is to use JTA only for jBPM and the logging/BAM information (jBPM schema)?

            I read something similar in the jBPM guide but I'm not sure...

              • Actions