The actual problem is that I don't succeed in deploying processes with the help of the ANT task. The tasks runs but it always deploys the processs to an in-memory database although I have specified the connection details in the build.xml file.

I have to say I am a bit confused because there are jdbc-properties and hibernate-properties. To be sure I set them both

 <property name="jdbc.driver" value="org.hsqldb.jdbcDriver"/>
 <property name="jdbc.url" value="jdbc:hsqldb:hsql://myserver.mydomain.de:1701"/>
 <property name="jdbc.username" value="sa"/>
 <property name="jdbc.password" value=""/>

 <property name="hibernate.dialect" value="org.hibernate.dialect.HSQLDialec"/>
 <property name="hibernate.connection.driver_class" value="org.hsqldb.jdbcDriver"/>
 <property name="hibernate.connection.url" value="jdbc:hsqldb:hsql://myserver.mydomain.de:1701"/>
 <property name="hibernate.connection.username" value="sa"/>
 <property name="hibernate.connection.password" value=""/>
 <property name="hibernate.format_sql" value="true"/>

[jbpm-deploy] INFO: using driver: org.hsqldb.jdbcDriver at URL: jdbc:hsqldb:mem:.

You're my hero for today, Ronald. ;) I was messing around with bugs of third-party software and started to overlook some things already.

Thanks a lot!

Okay, it's me again:

Where and how can I make the HSQLDB server used in the demo setup bind to the actual IP address and not to localhost? The reason: I am trying to deploy remote.

I have done the following for a workaround: I stopped Tomcat and I changed the supplied start-up script to start the HSQLDB from

java -cp hsqldb.jar org.hsqldb.Server -address localhost -port 1701 -dbname.0 jbpmDatabase

java -cp hsqldb.jar org.hsqldb.Server -address 0.0.0.0 -port 1701 -dbname.0 jbpmDatabase

It's absolutely not my day. Starting Tomcat does not bring up a database server anymore. I checked by the help of the HSQLDB Manager. Connecting to localhost worked before. I cannot login to the jBPM Console since it gives me the message "Authentication failed.".

My test installation is based upon the demo setup you get when you use ant demo.setup.tomcat. Normally after running this ant-task you just have to use startup.bat to bring up Tomcat and there you go. When running on the same machine you can also connect to the HSQLDB running on localhost with the Database Manager. However this does not work anymore and I cannot login to the jBPM Console anymore. It just says: "Authentication failed".

Hello Ronald,

finally I managed to get everything working. As I mentioned already, it was not my day. :)

1) When you use the ant task demo.setup.tomcat to create the demo setup the ant task also brings up the hsqldb-server using the supplied batch file after the installation is done. So I was under the impression that starting Tomcat also starts the database but it is just the first time after installation like this. Think this is a difference to the JBoss AS setup.

2) Regarding binding the hsqldb-server to the actual ip address I changed the installation templates of the config files so the changes are promoted all over the setup, especially important for C:\jbpm-4.1\apache-tomcat-6.0.20\conf\server.xml where the JbpmConsoleRealm is declared together with a connection url to the database server. :)

3) Regarding the deployment I also deleted the line

<property name="hibernate.hbm2ddl.auto">create-drop</property>