Show Table of Contents
3.4. Database Migration for 6.x Instances
Due to data model changes the database schema has also changed between minor versions of JBoss BPM Suite. A set of scripts has been included to ease this migration process; these scripts will generate the new tables and columns necessary, in addition to populating these columns where appropriate.
Important
It is strongly recommended to backup the database before attempting any update, as this will provide a recoverable state should any issues arise during the update process.
- Download the
Red Hat JBoss BPM Suite Supplementary Toolsfrom the Customer Portal. - Shutdown any Red Hat JBoss BPM Suite servers communicating with the database.
- Navigate to the subdirectory corresponding to the type of database used. For instance, if a h2 database is in use (the default), then the scripts in the
h2directory will be used in the subsequent steps. - Examine the contents of each script to be executed. While many of the scripts contain only database changes, there are others that require commands to be executed from a client with an open connection to the database.
- Execute the scripts, in order, corresponding to the following table.
Table 3.1. Database Scripts by Version
Original JBoss BPM Suite Version New JBoss BPM Suite Version Script(s) to execute 6.0 6.2 bpmsuite-6.0-to-6.1.sql,
bpmsuite-6.1-to-6.2.sql6.1 6.2 bpmsuite-6.1-to-6.2.sql6.0 6.1 bpmsuite-6.0-to-6.1.sql - Start the new JBoss BPM Suite server.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.