Hide Forgot
Date of First Response: 2008-01-21 14:27:49 project_key: SOA Part of the delivery should be scripts that will perform upkeep of the database. They should provide two main functions - export/import to the file (XML?) and clean database. All for old jBPM processes, stale jUDDI records etc. The operation should be based on the typically record timestamp. This feature is important beacuse 1) The customer typically requires such tool to provide maintanance and profylactics for the database 2) It is common policy that customer loses warranty when he does unauthorized (unqualified) changes in the database - such scripts will handle the situation
This is a tricky requirement, that I don't think can make it into GA. We're going to need to consult with owners of the code to determine all the proper procedures. This requirement has been added too late in the game. I am retargeting this request for post-GA.
Link: Added: This issue related SOA-721
Chester Wu is working on this jira. As he still has problem with his permission right (he can not assign jiras to himself), I assign this under my name temporarily.
I must agree that this procedure is not sufficient 1) There are environments where it is simply not concivable to stop the operations just for the backup 2) We need not only to clean/backup database but also remove the old/unused records, like - JMS messages not delivered for 14 days - jBPM processes and history older than 30 days - Messages from message store older than 5 days, etc. Otherwise we end up with umlimited growth of database tables and related operation slowdown
Create related issues in all of the projects that use databases and link them in here. This is not something that we can do without the semantic information on what can really be removed and what can't, which the project engineers have.
Link: Added: This issue is a dependency of JBRULES-1973
Link: Added: This issue is a dependency of JBPM-2045
Link: Added: This issue is a dependency of JBESB-2424
Link: Added: This issue is a dependency of JBMESSAGING-1513
DBs that we have to account for Rules DB (Drools project) jBPM DB (jBPM project) UDDI DB (ESB project) ESB management console DB (ESB project) ESB message store DB (ESB project) JMS DB (JBM project) See linked JIRAs
Release Notes Text: Added: Closing per defect triage 5-Dec-2011. Out of date or no plan to fix. If this impacts active users, reopen as necessary.