Imixs Workflow Connecting to DB2

[Atifazrin]

Hi all,
I been using workflow engine such as jBPM and Node-red as my daily work, i stumble across Imixs Workflow and been playing around for 2 days , and i got a question on how to connect to DB2 instance as there is not documentation on this recorded. Really appreciate if can get answer on this. Thank you in advance

[rsoika]

Hi @Atifazrin
welcome to the Imixs Community :-)
Imixs-Workflow is database independent. So, the only thing that you need is a JDBC Driver for db2 and a database resource configuration in your application server.
Imixs-Workflow is working with the Jakarta EE Database resource and does not see your real database. So it is a app server issue and you do not need to change your application running Imixs-Workflow.

So depending on your application server you need to configure the data source against your db2 database.

Let us know if you need more information.

===
Ralph

[Atifazrin]

Hi @rsoika ,
Thank you so much for replying and having me into this community :)
To answer your question , yes it would really help on how to do the configuration to connect to my DB2 Instance

[rsoika]

The first question now is: how are you using imixs-workflow? As a library in your app, or do you use one of our out of the box applications?

The section question: Which application server are you using? Wildfly, Payara, ....? - And how do you run your server - do you use a container?

[Atifazrin]

Hi rsoika , sorry for the late reply , we using out of the box application , we just doing some R&D works as to figuring out how does this imixs worflow works , we just using our own local to try and test this workflow ,but our main instance is using DB2

[rsoika]

What you need is to configure the DB2 JDBC Driver into your Wildfly server.
See also this discussion : https://stackoverflow.com/questions/24006413/db2-driver-datasource-setup-on-wildfly-failed-to-load-module-for-driver-com-ib

in its core you need to add the structure for the lib under /docker/configuration/modules
You can see the directory structure here:
https://github.com/imixs/imixs-process-manager/tree/master/docker/configuration/wildfly/modules

And also you need to adapt the setup into your standalone.xml

....
                <!-- imixs-workflow datasource  REPLACE THIS WITH YOUR DB2 Driver - -->
                <datasource jta="true" jndi-name="java:/jdbc/workflow" pool-name="workflow"
                    enabled="true" use-ccm="true">
                    <connection-url>${env.POSTGRES_CONNECTION}</connection-url>
                    <driver-class>org.postgresql.Driver</driver-class>
                    <driver>postgresql</driver>
                    <security>
                        <user-name>${env.POSTGRES_USER}</user-name>
                        <password>${env.POSTGRES_PASSWORD}</password>
                    </security>
                    <validation>
                        <valid-connection-checker
                            class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker" />
                        <!-- any background-validation-millis > 0 will enable background validation.
                        See https://jira.jboss.org/browse/JBAS-4088. -->
                        <background-validation-millis>60000</background-validation-millis>
                        <exception-sorter
                            class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"></exception-sorter>
                    </validation>
                </datasource>
               <dtivers>
      ...................
                    <!-- Postgres Integration - REPLACE THIS WITH YOUR DB2 Driver -->
                    <driver name="postgresql" module="org.postgresql">
                        <driver-class>org.postgresql.Driver</driver-class>
                    </driver>
....

I think you can remove the valid-connection-checker - this is only for production. But you need to replace the driver-class

Did this help you?

[Atifazrin]

yup thank you so much for the explaination , this work perfectly for me

[rsoika]

Maybe you can share you configuration in the standalone.xml file than I will add the DB2 setup into the documentation.