Hide Forgot
Affects: Documentation (Ref Guide, User Guide, etc.) Date of First Response: 2008-08-20 15:30:39 Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/210809 project_key: SOA '8.2. Database upgrades' section of JBPM Users Guide[1] is out-dated because it explains about using upgrade.scripts. But when you upgrade from jBPM v3.1.x to v3.2.x, you need to follow a section about upgrading database schema in JBPM_3.2.x_x.zip/jbpm-jpdl-3.2.x/release.notes.html instead of [1]. [1] http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.2.2/html-single/JBPM_Users_Guide/index.html#databaseupgrades
Please see the SOA-P productization notes and create a linked issue in the jBPM JIRA space.
Link: Added: This issue related JBPM-1689
Raised another JIRA in the jBPM project and crossed link it.
Affects: Added: [Documentation (Ref Guide, User Guide, etc.)]
To clarify task: the SOA JBPM doc only includes a 3.1 -> 3.2 upgrade script & needs to also include the 3.1 -> 3.2 script (and notes) as well ?
The whole section of '8.2. Database upgrades' is out-dated and it needs to be replaced by the one in the notes.
I need a bit more guidance here. The file release.notes.html basically just has 2 pages of SQL for the schema update. Users have to copy/paste the commands into a SQL client to upgrade? JBPM-1689 has this set to resolved in 3.3... which just replaces this section with: For database upgrades, please refer to the release.notes.html in the root of your installation directory.
> The file release.notes.html basically just has 2 pages of SQL for the schema update. Users have to copy/paste the commands into a SQL client to upgrade? Yes. > For database upgrades, please refer to the release.notes.html in the root of your installation directory. I think this sentence is enough for this fix but you should add the installation directory is <soa-home>/jbpm-jpdl in SOA-P.
Link: Added: This issue is a dependency of SOA-1172
The new jBPM docs direct the user to the jBPM release notes for db upgrade instructions, but the jBPM 3.3.1 release notes in CR2 (jbpm-jpdl/release.notes.html) no longer include database upgrade instructions. Unless someone has a better idea, I'm going to copy the migration instructions for 3.1.x -> 3.2.x and 3.2.3 -> 3.3.0.GA from the release.notes.html from the CR1 package into the SOA jBPM docs. It will be quick and dirty but it will be there.
SOA jBPM guide has been updated as per my previous comment
There is no 3.3.0 and 3.2.3 in SOA Platform. '7.2.1. Changes from 3.2.3 to 3.3.0.GA 'should be renamed to 'Changes from 3.2.2 to 3.2.5'
Moreover there is an automatic mechanism in jbpm-service.xml to automatically upgrade db if CP1 is run on GA created db <mbean code="org.jboss.internal.soa.esb.dependencies.DatabaseInitializer" name="jboss.esb:service=JBPMDatabaseUpgrader"> <attribute name="Datasource">java:/JbpmDS</attribute> <attribute name="ExistsSql">select PARENTLOCKMODE_ from JBPM_NODE</attribute> <attribute name="SqlFiles"> jbpm-sql/jbpm.jpdl.hsqldb.update322.sql </attribute> <depends>jboss.esb:service=JBPMDatabaseInitializer</depends> <attribute name="UseEOL">true</attribute> </mbean>
So... in this section we can just tell them that it occurs automatically, and point out where the update scripts live in-case they want to check them (if they have customized their database etc).
Link: Added: This issue related SOA-1196
Content of section updated as: The jBPM ESB service that is provided in the JBoss Enterprise SOA Platform handles database upgrades automatically from any earlier version of JBoss Enterprise SOA Platform. If you have made any changes to the jBPM database schema or wish to use a jBPM database which was not created by the JBoss Enterprise SOA Platform, then the upgrade process cannot be guaranteed to work. You should contact Red Hat JBoss support for advice for your specific circumstances.
Verified in CR4