Camunda webapp/cockpit 7.19 for jboss use local h2 database

[BerndVarga]

Hi all,

today we detected an issue, that the provided camunda-webapp-ee-jboss-standalone-7.19.8-ee.war use not the datasource which is provided from jboss for process-engine. It use an local setup h2 database.

Entries in the applicationContext.xml:

  <bean id="dataSource" class="org.springframework.jdbc.datasource.TransactionAwareDataSourceProxy">
    <property name="targetDataSource">
      <bean class="com.zaxxer.hikari.HikariDataSource">
        <property name="driverClassName" value="org.h2.Driver" />
        <property name="jdbcUrl" value="jdbc:h2:mem:process-engine;TRACE_LEVEL_FILE=0;DB_CLOSE_ON_EXIT=FALSE" />
        <property name="username" value="sa" />
        <property name="password" value="" />
      </bean>
    </property>
  </bean>

In the previous version does not contains any applicationContext.xml file.
We get the archive from
https://downloads.camunda.cloud/enterprise-release/camunda-bpm/jboss/7.19/7.19.8/camunda-webapp-ee-jboss-standalone-7.19.8-ee.war
which should work for JBoss EAP7.
Thanks for any advice.

BR Bernd Varga

[BerndVarga]

I guess, I have found the issue on our side.
We should use camunda-webapp-jboss instead of camunda-webapp-standalone-jboss artifact.

https://artifacts.camunda.com/ui/native/camunda-bpm/org/camunda/bpm/webapp/camunda-webapp-jboss/7.19.0/