Bug 1259918

Summary: Updating existing database from BPM Suite 6.0.x to 6.1
Product: [Retired] JBoss BPMS Platform 6 Reporter: Amana <ajuricic>
Component: DocumentationAssignee: brms-docs <brms-docs>
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: brms-docs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Build Name: 23049, Migration Guide-6.1 Build Date: 31-07-2015 11:17:09 Topic ID: 42682-742067 [Latest]
Last Closed: 2020-03-27 19:04:54 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:
Embargoed:

Description Amana 2015-09-03 19:20:54 UTC 
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" />