Bug 1259918 - Updating existing database from BPM Suite 6.0.x to 6.1
Updating existing database from BPM Suite 6.0.x to 6.1
Status: NEW
Product: JBoss BPMS Platform 6
Classification: JBoss
Component: Documentation (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: brms-docs@redhat.com
Lukáš Petrovický
Depends On:
  Show dependency treegraph
Reported: 2015-09-03 15:20 EDT by Amana
Modified: 2016-01-08 16:58 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Build Name: 23049, Migration Guide-6.1 Build Date: 31-07-2015 11:17:09 Topic ID: 42682-742067 [Latest]
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1602633 None None None Never

  None (edit)
Description Amana 2015-09-03 15:20:54 EDT
Title: Database Migration

Describe the issue:

We have a lot of customers asking how to update the database data from BPM Suite 6.0.x to 6.1 since they have some active processes/tasks and do not want to create a new database. Also, in BPM Suite 6.1 there are some news tables and columns (i.e. deploymentstore), then the schema needs to be updated.

Suggestions for improvement:

The documentation is missing how to achieve that. Basically, they need to point the new installation (BPM Suite 6.1) to the old database (from BPM Suite 6.0.3) and make sure that "hibernate.hbm2ddl.auto" property is set to "update" value in "business-central.war/WEB-INF/classes/META-INF/persistence.xml" file:

  <property name="hibernate.hbm2ddl.auto" value="update" />

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