[esb-issues] [JBoss JIRA] Commented: (JBESB-2235) Upgrade jBPM to version 3.3.0

[ https://jira.jboss.org/jira/browse/JBESB-2235?page=com.atlassian.jira.plu... ] Daniel Bevenius commented on JBESB-2235: ---------------------------------------- Upgrade steps: Download http://www.jboss.org/downloading/?projectId=jbossjbpm&url=http://down... and install into a directory. 1. Copy jars Copy lib/jbpm-jpdl.jar and lib/jbpm-identity.jar to product/services/jbpm/lib/ext 2. Copy hibernate config Copy config/hibernate.cfg.hsqldb.xml to product/services/jbpm/src/main/resource/hibernate.cfg.xml a) Change the Datasource name to: <property name="hibernate.connection.datasource">java:/JbpmDS</property> b) Uncomment the JTA transaction properties section: <!-- JTA transaction properties (begin) === ==== JTA transaction properties (end) --> <property name="hibernate.transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property> <property name="hibernate.transaction.manager_lookup_class">org.hibernate.transaction.JBossTransactionManagerLookup</property> c) Add the following property: <property name="jta.UserTransaction">UserTransaction</property> 3. Copy the .sql files Copy database/*.sql product/services/jbpm/src/main/resources/jbpm-sql Running 'ant dist' from the product folder and starting the server will generate the following error: 08:45:48,684 INFO [DatabaseInitializer] Initializing java:/JbpmDS from listed sql files 08:45:48,690 WARN [ServiceController] Problem starting service jboss.esb:service=JBPMDatabaseInitializer org.h2.jdbc.JdbcSQLException: Table JBPM_ACTION not found; SQL statement: alter table JBPM_ACTION drop constraint FK_ACTION_EVENT [42102-68] at org.h2.message.Message.getSQLException(Message.java:91) at org.h2.message.Message.getSQLException(Message.java:95) at org.h2.message.Message.getSQLException(Message.java:73) at org.h2.command.Parser.readTableOrView(Parser.java:4024) at org.h2.command.Parser.readTableOrView(Parser.java:4004) at org.h2.command.Parser.parseAlterTable(Parser.java:4049) at org.h2.command.Parser.parseAlter(Parser.java:3621) Now, we are using H2(Hypersonic 2) and not hypersonic which is specified in jbpm-service.xml: <attribute name="SqlFiles"> jbpm-sql/jbpm.jpdl.hsqldb.sql, I modified jbpm.jpdl.hsqldb.sql file by removing the first set of 'alter table' statements but kept the 'drop table' statements. Still, upon startup it complained about three missing tables. Note that this complaint is not when creating tables but when running the import.sql script. The tables that are missing are JBPM_ID_GROUP, JBPM_ID_MEMBERSHIP, JBPM_ID_USER which are all related to identity. Perhaps somethings has changed here and these are no longer needed. For now I've created a jbpm.jpdl.h2.sql and updated jbpm-service.xml to use it. Plus I added the above mentioned tables. I'll attach this file to the jira. 4. Deploying jbpm-console.war: java.lang.ClassNotFoundException: org.jbpm.web.ProcessUploadServlet org.jbpm.web.ProcessUploadServlet was previously located in jbpm-jpdl.jar but is now in jsf-console.war. This servlet is used by our quickstarts to deploy processes. So, I tried deploying jsf-console.war to jbossesb-server get the following error: 07:51:29,593 INFO [TomcatDeployer] deploy, ctxPath=/jbpm-console, warUrl=.../tmp/deploy/tmp14086jsf-console-exp.war/ 07:51:29,596 WARN [TomcatDeployer] message-destination-ref 'jms/JobQueue' ignoring message-destination-link 'JobQueue' because it has a jndi-name in jboss-web.xml 07:51:29,690 WARN [ServiceController] Problem starting service jboss.web.deployment:war=jsf-console.war,id=1918282371 org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.naming.NamingException: ejb-local-ref: 'ejb/TimerEntityBean', with web.xml ejb-link: 'TimerEntityBean' failed to resolve to an ejb with a LocalHome) at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:384) at org.jboss.web.WebModule.startModule(WebModule.java:83) Looks like this webapp requires an ejb, and ejb support is not available by default in the jbossesb-server. Going to look into what can be done get this working. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira