Bug 777784 (SOA-310)

Summary:	Database maintenance scripts
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Jiri Pechanec <jpechane>
Component:	Tooling, Configuration	Assignee:	Douglas Palmer <dpalmer>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2 Beta 1	CC:	mweiler
Target Milestone:	---
Target Release:	CONTINUING
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-310
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-05 18:42:19 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jiri Pechanec 2008-01-10 06:30:16 UTC

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

Comment 1 Mike Brock 2008-01-21 19:27:49 UTC

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.

Comment 2 Julian Coleman 2008-08-28 15:40:23 UTC

Link: Added: This issue related SOA-721

Comment 3 Jervis Liu 2008-09-01 02:15:02 UTC

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.

Comment 6 Jiri Pechanec 2009-02-13 10:46:12 UTC

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

Comment 7 Mark Little 2009-02-13 17:19:44 UTC

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.

Comment 8 Len DiMaggio 2009-02-17 21:28:39 UTC

Link: Added: This issue is a dependency of JBRULES-1973

Comment 9 Len DiMaggio 2009-02-17 21:30:08 UTC

Link: Added: This issue is a dependency of JBPM-2045

Comment 10 Len DiMaggio 2009-02-17 21:33:09 UTC

Link: Added: This issue is a dependency of JBESB-2424

Comment 11 Len DiMaggio 2009-02-17 21:34:52 UTC

Link: Added: This issue is a dependency of JBMESSAGING-1513

Comment 12 Len DiMaggio 2009-02-17 21:35:02 UTC

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

Comment 18 Ken Johnson 2011-12-05 18:42:19 UTC

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.