3.2. Setting up Persistence for Dashbuilder

As Dashbuilder is dependent on the configuration of Business Central, ensure Business Central is configured according to Section 3.1, “Setting up Persistence for Business Central”. BPMS 6 is configured to use a datasource with Java Naming and Directory Interface (JNDI) name java:jboss/datasources/ExampleDS. If you want to make the application work with a database different from H2, for example Oracle, MySQL, Postgres, or MS SQL Server, follow these steps.
  1. Install the database driver and create a new datasource according to the example in EAP 6 Documentation in section 6.7.1. Example PostgreSQL Datasource. Use modular approach to the installation of JDBC driver for easy subsequent configuration.
  2. Create an empty database.
  3. Modify file dashbuilder.war/WEB-INF/jboss-web.xml whose default entry is: 
      	<jboss-web>
    <context-root>/dashbuilder</context-root>
    <resource-ref>
        <res-ref-name>jdbc/dashbuilder</res-ref-name>
        <res-type>javax.sql.DataSource</res-type>
        <jndi-name>java:jboss/datasources/ExampleDS</jndi-name>
    </resource-ref>
  4. Modify also files WEB-INF/jboss-deployment-structure.xml from both the business-central.war and dashbuilder.war applications, and add a dependency under the dependencies section on the JBDC driver module created earlier during datasource creation. The following snippet shows a sample configuration where jdbcDriverModuleName is the name of the JBoss EAP 6 JDBC driver module. 
      <dependencies>
         ...
            <module name="jdbcDriverModuleName" />
            ...
  </dependencies>
Report a bug