Bug 778738 (SOA-1196)

Summary: The SOA documentation contains no directions or advice for upgrading
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Dana Mison <dmison>
Component: DocumentationAssignee: Dana Mison <dmison>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.2 CP03, 4.3 CP01   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1196
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 778739 (view as bug list) Environment:
Last Closed: 2010-02-08 20:06:24 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 Dana Mison 2009-02-27 03:25:17 UTC 
Affects: Documentation (Ref Guide, User Guide, etc.)
Date of First Response: 2009-02-26 22:44:30
project_key: SOA

The included documentation contains no instructions or advice to guide someone upgrading from one version of the SOA Platform to another. 

This probably should be included in the Getting Started Guide
Comment 3 Len DiMaggio 2009-03-03 14:25:16 UTC 
I think that the relevant issue here is for 4.3 GA customers that built their DBs manually. They will need to be told about the DB schema changes in CP01 - how will these customers get these changes into their DBs? Will they invoke the DB upgrade scripts manually?

Re-opening and assigning to Darrin.
Comment 4 Len DiMaggio 2009-03-03 14:27:19 UTC 
Changed fix version to CP01.
Comment 5 Dana Mison 2009-03-06 07:04:45 UTC 
My bad I thought that one of the jBPM schema changes was between the versions from GA & CP01 and so would need to be applied at upgrade for the standard install.  Not critical then but some upgrade guidelines should be provided.

 - included in the getting started guide & referenced from the release notes.  
 - mention that if they are using a pre-existing database they need to refer to the documentation for the specific component to ensure that it is the correct version and what changes they would need to apply
Comment 6 Len DiMaggio 2009-03-09 01:34:58 UTC 
Link: Added: This issue is related to SOA-693
Comment 9 Dana Mison 2010-01-27 02:06:54 UTC 
added as a migration issue:

The JBoss Enterprise SOA Platform creates new databases for its components to use. Attempting to use databases from earlier or community versions of the components may not work and is not supported.

If the use of existing databases is needed, then contact Red Hat JBoss Support for advice.