Bug 777998 (SOA-525)

Summary: Extend /jboss-as/tools/schema to generate DB config scripts for management console
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Len DiMaggio <ldimaggi>
Component: ToolingAssignee: Default User <jbpapp-maint>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.2 CP01   
Target Milestone: ---   
Target Release: 4.2 TP02   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-525
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-09-30 10:26:18 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:
Bug Depends On: 777997    
Bug Blocks:    

Description Len DiMaggio 2008-04-25 16:25:13 UTC 
Date of First Response: 2008-04-28 18:48:42
project_key: SOA

In GA and CP01 the management console DB (for DBs other than HSQLSB) is configured outside of the DB schema tool. Can we extend the DB schema tool to and remove the task described in the getting started guide:


2.1.1.1. Monitoring/Management Console Configuration

By default, the monitoring/management console uses hsqldb as a back-end database. It has also been tested with Oracle and MySQL, but could be extended to use any other JDBC/hibernate-supported database.

In the management-esb directory there is a db.properties file. In order to change the database from hsqldb to mysql or oracle, edit this file and change the db property to mysql or oracle.

Next, change the /tools/management-esb/src/main/resources//management-ds.xml file so that the settings match the datasource for your database.

JBoss ships with hsqldb.jar in the server//lib directory. In order to use a different database as a back-end, please also the JDBC driver into the server//lib directory of your application server.

For MySQL, it may be necessary to create the database "statistics" before deploying if you have not edited the management-ds.xml file.

Please refer to tools/console/MANAGEMENT-README.txt for further information.
Comment 1 Len DiMaggio 2008-04-25 16:25:20 UTC 
Link: Added: This issue depends SOA-524
Comment 2 tcunning 2008-04-28 22:46:23 UTC 
Link: Added: This issue is a dependency of SOA-526
Comment 3 tcunning 2008-04-28 22:46:52 UTC 
Link: Removed: This issue is a dependency of SOA-526
Comment 4 tcunning 2008-04-28 22:47:05 UTC 
Link: Added: This issue duplicates SOA-526
Comment 5 tcunning 2008-04-28 22:48:42 UTC 
This should be covered in SOA-526.