Bug 778831 (SOA-1279) - Docs contain multiple instructions on how to change the database
Summary: Docs contain multiple instructions on how to change the database
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1279
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Documentation
Version: 4.3 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 CP02
Assignee: Dana Mison
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-08 10:12 UTC by Martin Weiler
Modified: 2009-08-27 19:52 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-27 19:52:05 UTC
Type: Feature Request


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 778968 0 high CLOSED QE - 4.3.CP02 Administrators Guide 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-1279 0 None None None Never

Internal Links: 778968

Description Martin Weiler 2009-04-08 10:12:14 UTC
Date of First Response: 2009-06-18 01:09:34
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/283987
project_key: SOA

Instructions on how to change the default database can be found at multiple locations in the SOA-P docs:
- Getting Started Guide, Chapter 2.1.1. Changing the Database used by the platform
- Administration Guide, Chapter 1.4. Switching Databases

There should just be a single set of instructions to avoid confusion. If the information makes sense in both docs, one should just contain a link to ensure the information stays in sync.

Comment 1 Dana Mison 2009-06-18 05:09:34 UTC
both of these sections refer to using the schema tool now.

The "database configuration" & "switching databases" sections of the administration guide have been merged.

Comment 2 Dana Mison 2009-07-07 09:44:04 UTC
Link: Added: This issue is related to SOA-1396


Comment 3 Len DiMaggio 2009-08-27 19:52:05 UTC
Verified resolved in the docs in the 4.3 CP02 CR2 build.


Note You need to log in before you can comment on or make changes to this bug.