Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-4789

Unable to change datasource for Kie Server JBPM Extension

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • jBPM 6.4.0.Final
    • jBPM 6.3.0.Final
    • Persistence
    • None
    • NEW
    • NEW
    • Hide
      fixed as once the server configuration file was created it ignored system properties.

      Workaround for this is to either use different id or remove/edit server config file that is named as server id + .xml extension. Usually in current directory (like WILDFLY_HOME/bin)
      Show
      fixed as once the server configuration file was created it ignored system properties. Workaround for this is to either use different id or remove/edit server config file that is named as server id + .xml extension. Usually in current directory (like WILDFLY_HOME/bin)

      The kie execution server war by default has a datasource configured as ExampleDS for JBPM extension which is default H2 database in Jboss. But when we are trying to modify, any of the below methods does not work,

      1. Changed the persistence.xml configuration under kie-services-jbpm-extention jar JPA/ directory --> Still uses the ExampleDS

      2. Changed the kie server constant CFG_PERSISTANCE_DIALECT by updating system proeperty "org.kie.server.persistence.dialect" --> Still uses the ExampleDS

      3. Changed the source code of the extension to use MySQLDialect and jbpmDS configured with MySQL, then it worked.

        1. Java Process Started with Properties added.PNG
          140 kB
          Balavigneshwaran Manogaran
        2. server.log
          340 kB
          Balavigneshwaran Manogaran
        3. server( Server Started with H2Dialect ).log
          48 kB
          Balavigneshwaran Manogaran

            swiderski.maciej Maciej Swiderski (Inactive)
            balavigneshwaran.manogaran Balavigneshwaran Manogaran (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: