Hide Forgot
Date of First Response: 2009-02-13 08:05:38 project_key: SOA There are significant changes in the database structure between GA and CP version. The Oracle changes are 1) A lot of varchar2(4000) columns were replace with clob 2) There is new field PARENTLOCKMODE_ in JBPM_NODE table There should be either now changes or migration scripts has to be provided for all databases
Link: Added: This issue related JBPM-2018
Link: Added: This issue related JBPM-2017
Link: Added: This issue related JBPM-1755
Added links to related issues that contain detailed information on 1) and 2) > There should be either now changes or migration scripts has to be provided for all databases The build can produce update scripts if there is a valid db connection to a legacy 3.2.2 schema. We only do this for databases that we can actually do QA for http://www.jboss.org/community/docs/DOC-12860 https://svn.jboss.org/repos/jbpm/jbpm3/tags/jbpm-3.2.5.SP1/modules/db/scripts/antrun-jbpmschema.xml We cannot claim support for databases that are not covered my this matrix. Support for all SOA platform Tier1 databases is subject of JBPM-1451, which has a dependency on JBPM-1408
We cannot release until the migration scripts are presen If the build cannot produce the scripts can they be hand crafted?
Generating the update scripts should be easy for mysql, postgresql and sybase. You point your connection properties in profiles.xml to an existing jbpm322 schema and build the db module. For databases that you don't have an existing jbpm322 schema, the update scripts cannot be generated. In which case you probably don't need an update script because you don't have the jbpm322 schema to test it against. As a consequence I'd say you cannot claim support for a database for which you don't have an existing schema. RH IT should be able to give you the connection properties for the jbpm322 schemas The maven build executes this ant target <target name="update-schema" depends="setup-schema" description="Generate jBPM Database Update Scripts"> <jbpmschema output="${scriptsdir}/jbpm.jpdl.mysql.update322.sql" config="hibernate.cfg.mysql.xml" properties="mysql.properties" action="update" delimiter=";"/> <jbpmschema output="${scriptsdir}/jbpm.jpdl.postgresql.update322.sql" config="hibernate.cfg.postgresql.xml" properties="postgresql.properties" action="update" delimiter=";"/> <jbpmschema output="${scriptsdir}/jbpm.jpdl.sybase.update322.sql" config="hibernate.cfg.sybase.xml" properties="sybase.properties" action="update" delimiter=";"/> </target>
Link: Added: This issue depends JBQA-2077
As per JBPM-2056 and JBPM-1755, the only change between the 3.2.2 and 3.2.5SP schema is now the addition of a PARENTLOCKMODE_ column to the JBPM_NODE table. This addition needs to be catered for with upgrade scripts. This addition also needs to be documented in the release notes, for users who create/update the database schema manually.
Do not forget varchar2(4000)/clob replacement. These are incpomaptible datatypes from Hibernate POV so it has to be also handled carefully. The scripts should 1) Alter the tables to use clob 2) Ensure that the data already present are converted to new datatype
With the changes to the 3.2.5 SP schema, the only changes are: all DB's: addition of PARENTLOCKMODE_ column to the JBPM_NODE table Ingres: change of columns from `date with null' to `timestamp with time zone with null' Sybase: change of EXCEPTION_ column from `varchar(4000)' to `text' Note that Ingres is not a supported database and that the Sybase change has already been compatibilty tested.
Fixed with revision 2692 (4.3 branch of: build-tools/builders/jbpm/jbpm.esb/jbpm-service.xml build-tools/builders/jbpm/jbpm.esb/jbpm-sql/jbpm.jpdl.db2.update322.sql build-tools/builders/jbpm/jbpm.esb/jbpm-sql/jbpm.jpdl.derby.update322.sql build-tools/builders/jbpm/jbpm.esb/jbpm-sql/jbpm.jpdl.firebird.update322.sql build-tools/builders/jbpm/jbpm.esb/jbpm-sql/jbpm.jpdl.hsqldb.update322.sql build-tools/builders/jbpm/jbpm.esb/jbpm-sql/jbpm.jpdl.ingres.update322.sql build-tools/builders/jbpm/jbpm.esb/jbpm-sql/jbpm.jpdl.interbase.update322.sql build-tools/builders/jbpm/jbpm.esb/jbpm-sql/jbpm.jpdl.mckoi.update322.sql build-tools/builders/jbpm/jbpm.esb/jbpm-sql/jbpm.jpdl.mssql.update322.sql build-tools/builders/jbpm/jbpm.esb/jbpm-sql/jbpm.jpdl.mysql.update322.sql build-tools/builders/jbpm/jbpm.esb/jbpm-sql/jbpm.jpdl.oracle.update322.sql build-tools/builders/jbpm/jbpm.esb/jbpm-sql/jbpm.jpdl.postgresql.update322.sql build-tools/builders/jbpm/jbpm.esb/jbpm-sql/jbpm.jpdl.sapdb.update322.sql build-tools/builders/jbpm/jbpm.esb/jbpm-sql/jbpm.jpdl.sybase.update322.sql Commit message: Add upgrade database scripts and *service.xml files to fix JIRA SOA-1176. and with revision 2694 (4.3 branch) of: build-tools/builders/jbpm/build.xml Commit message: Install upgrade database scripts and *service.xml files to fix JIRA SOA-1176.
Verified in CR3
It has been decided not to add the additional PARENTLOCKMODE_ column to the JBPM_NODE table in CP01. See also JBPM-2121
Link: Added: This issue is related to JBPM-2121
Link: Added: This issue related SOA-1209
Link: Added: This issue related SOA-1177
Fixed with revision 2867 (4.3 branch) of: build-tools/builders/jbpm Commit message: SOA-1176 Revert revision 2692 and remove database scripts and *service.xml files. and with revision 2868 (4.3 branch) of: build-tools/builders/jbpm/build.xml Commit message: SOA-1176 Revert revision 2694 and remove installation of upgrade database scripts and *service.xml files
Link: Added: This issue is related to JBPM-2119
Verified in CR7