| Summary: | ESB management console DB scripts only support HSQLDB | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Len DiMaggio <ldimaggi> |
| Component: | Documentation, JBossESB | Assignee: | Joshua Wulf <jwulf> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2 IR6 | CC: | jwulf, lcarlon |
| Target Milestone: | --- | ||
| Target Release: | 4.2 CR1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-89 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-01-23 20:41:18 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Len DiMaggio
2007-11-02 18:01:46 UTC
Link: Added: This issue is a dependency of JBQA-1090 What to do about this? HSQLDB is not supported in SOA platform. Is this an exception? Any way around this? What are we going to message in our release notes / documentation about this? It will affect our support staff. Affects: Added: [Documentation (Ref Guide, User Guide, etc.)] From the Management Console README: "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 management-esb/src/main/resources/<db>/management-ds.xml file so that the settings match the datasource for your database. JBoss ships with hsqldb.jar in the server/<instance>/lib directory. In order to use a different database as a back-end, please also the JDBC driver into the server/<instance>/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." It should be sufficient to refer to this file (MANAGEMENT-README.txt) in the Release Notes. Josh, can you add this to the Release Notes for CR1? Affects: Removed: [Documentation (Ref Guide, User Guide, etc.)] Added: [Documentation (Ref Guide, User Guide, etc.), Release Notes] Verified in the RC1 release notes. |