Bug 1259918 - Updating existing database from BPM Suite 6.0.x to 6.1
Summary: Updating existing database from BPM Suite 6.0.x to 6.1
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Documentation
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: brms-docs@redhat.com
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-03 19:20 UTC by Amana
Modified: 2020-03-27 19:04 UTC (History)
1 user (show)

Fixed In Version:
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
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1602633 0 None None None Never

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" />
Note You need to log in before you can comment on or make changes to this bug.