Bug 793025 (JBEPP-105)

Summary: Document db schema changes properly
Product: [JBoss] JBoss Enterprise Portal Platform 4 Reporter: Martin Weiler <mweiler>
Component: docs-Reference_GuideAssignee: Prabhat Jha <prabhat.jha>
Status: CLOSED NEXTRELEASE QA Contact: ecs-bugs
Severity: high Docs Contact:
Priority: high    
Version: 4.3.0.GA_CP1CC: epp-bugs
Target Milestone: ---   
Target Release: 4.3.0.GA_CP2   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEPP-105
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-08-11 00:00:08 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:

Description Martin Weiler 2009-08-06 09:06:35 UTC 
Date of First Response: 2009-08-10 19:59:54
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/291300
project_key: JBEPP

Chapter 4 of the Reference Guide states:

"Enterprise Portal Platform 4.3 compatibility with JBoss Portal 2.6 is very high. The main differences are the use of JSR-286 features to replace JBoss Portal specific features. The database schema hasn't changed."

This is incorrect, due to the jBPM upgrade, the JBPM* tables have changed, and the following columns have been added:

TABLE NAME COLUMN NAME
JBPM_MODULEINSTANCE VERSION_
JBPM_NODE DESCRIPTION_
JBPM_NODE ISASYNCEXCL_
JBPM_NODE SCRIPT_
JBPM_NODE SUBPROCNAME_
JBPM_POOLEDACTOR VERSION_
JBPM_PROCESSDEFINITION CLASS_
JBPM_PROCESSDEFINITION DESCRIPTION_
JBPM_PROCESSINSTANCE KEY_
JBPM_SWIMLANEINSTANCE VERSION_
JBPM_TASK CONDITION_
JBPM_TASK PRIORITY_
JBPM_TASKINSTANCE PROCINST_
JBPM_TASKINSTANCE VERSION_
JBPM_TOKEN LOCK_
JBPM_TOKENVARIABLEMAP VERSION_
JBPM_TRANSITION CONDITION_
JBPM_TRANSITION DESCRIPTION_
JBPM_VARIABLEINSTANCE VERSION_

Also, the JBP_INSTANCE.SER_STATE and JBP_INSTANCE_PER_USER.SER_STATE column lengths are different (file instance/domain.hbm.xml):
http://fisheye.jboss.org/browse/Portal/branches/JBoss_Portal_Branch_2_7/core/src/resources/portal-core-sar/conf/hibernate/instance/domain.hbm.xml?r1=10060&r2=11464
Comment 1 Prabhat Jha 2009-08-10 23:59:54 UTC 
This is done. If you can, please verify CP02 reference guide at http://anonsvn.jboss.org/repos/portal/docs/enterprise/tags/Enterprise_Portal_Platform_4_3_GA_CP02/output/Reference_Guide.pdf
Comment 2 Martin Weiler 2009-08-11 10:28:40 UTC 
Thanks, Prabhat, very good explanation of the changes! Two minor suggestions:

1. The Note states: 

If you haven't used any workflow mechanism in JBoss Portal 2.6 and if the database user
has the rights to alter/create tables in the running database, all the following changes will
be automatically be done.

IMO, this should be changed to something like:

If the database user has the rights to alter/create tables in the running database, all the following changes will
be automatically done. The JBPM* tables are only used when the workflow services are activated.

2. For the very picky, I'd change 'JBpm' to 'jBPM'
Comment 3 Prabhat Jha 2009-08-11 19:18:32 UTC 
Your suggestions have been taken into account.
Comment 4 Thomas Heute 2009-08-11 20:08:27 UTC 
My initial comment about usage of jBPM was due to the fact that if you had timers you still need to move them to the new table, it won't happen automatically. But I guess the new wording is fine too.

Sorry for JBpm :)