1) For example, we need to execute the delete statement, where do we set it? In JBPM or Hibernate?
2) Does JBPM require a specific database?
3) How to archive data in JBPM?
4) How to maintain a database in JBPM?
5) How to restart a failed action / task in JBPM? Public and Process type example
6) Is it possible to upgrade from 3.0 to 5.0?
6.1 ) Are they compatible? 6.2 ) How to migrate from 3.0 to 5.0 6.3 ) What are the things/changes to be considered upon migration. 6.4 ) What are the possible impacts of migrating from 3.0 to 5.0 6.5 ) What would be the impact in the existing library of the 3.0?
source to share
Q) how to archive data in JBPM?
A) Archive A collection of historical records or the physical location where they are located https://community.jboss.org/message/622804#622804 According to the link above, the storage procedure is the best option for archiving old data that is no longer needed. or - don't care about old history, just delete / delete. - have BAM reporting to save and then change to another format / location / db to ensure consistent reporting. - apply an enterprise process (for example, I worked in an enterprise using data warehouse techniques) to collect and store reports of all historical data - leave it in place, but be prepared to grow your DB machine eventually! ;-)
JPDL specifies an xml schema and a mechanism for packaging all files associated with a process definition into a process archive. Deploying process archives can be done in three ways: using the process developer tool with an ant task, or programmatically.
Q) How do I restart a failed action / task in JBPM?
A) Tasks are never started automatically, but always manually. If the task was running while the server was down, the transaction should be rolled back and the task will be available again in the task list. If jBPM is running in the same transaction as the calling method (the one that signals in the first case) that will rollback as well. Thus, "transaction management" is fully supported.
Q) Can you upgrade from 3.0 to 5.0? Are they compatible? How to migrate from 3.0 to 5.0 What things / changes should be considered when migrating. What are the possible consequences of moving from 3.0 to 5.0
A) Well yes, you can go from 3.0 to 5.0, the migration process in the context is under development. So, whether it's compatible or not, we can't count on it. After that, the migration steps will also be known, and what things / changes that will be considered will also be known later, as well as its consequences.
Ok for refrence, please follow this link as this quick guide will help you and you will get your doubts / questions answered here.
http://www.schabell.org/2011/10/jbpm-migration-tooling-available-in.html www.schabell.org .
Q) For example, we need to execute the delete statement, where do we set it? In JBPM or Hibernate? Does JBPM require a specific DB? How do I save the database to JBPM?
A) Now the integration of JBPM with Spring still remains, so if we can do that, we can easily execute any database queries in the project, and JBPM is very flexible, we can use any database in our project by making changes to the persistence.xml file, that is, by adding the dialect and the database driver we need, jbpm uses the H2 database by default.
Q) Can we now use two databases in our project?
Q) How to maintain a database in JBPM?
source to share