You are viewing the documentation for Blueriq 15. Documentation for other versions is available in our documentation directory.

Case-Modelling has been in beta stage in the Blueriq 15 major. At the latest minor, all Blueriq 16.0 changes have been merged back to Blueriq 15.13. From this point on Case-Modelling is out of beta and can be used.

Please make sure to upgrade to at least Blueriq 15.13 when using Case-Modelling, possibly in a production environment. Earlier minor versions are not supported.

Configuration

In order to view audit logs in the DCM Maintenance app, some additional configuration is required.

First, enable the audit profile by creating a bootstrap.yml file in the spring.config.additional-location you configured:

bootstrap.yml
spring:
  profiles:
    active: default,audit

Datasource configuration

Add the required datasource properties to the blueriq-dcm-maintenance-app.yml file in the spring.config.additional-location you configured:

Example blueriq-dcm-maintenance-app.yml
blueriq:
  dcm:
    maintenance:
      app:
        audit:
          datasource:
            audit-sql-store: 
				url: <url>
            	username: <username>
            	password: <password>
            	driver-class-name: org.h2.Driver
            	validation-query: SELECT 1
            	testWhileIdle: true
            	timeBetweenEvictionRunsMillis: 5000
spring:
    jpa:
        database-platform: org.hibernate.dialect.H2Dialect
        show-sql: false
        hibernate:
            ddl-auto: validate
        properties:
            hibernate:
                id:
                    new_generator_mappings: true
                use_nationalized_character_data: true

We recommend setting a validation query so that when a database connection is lost due to a network failure for instance, it can be recovered once the network is restored. The validation query is database specific, the query below works with SQL Server (and H2), for Oracle use SELECT 1 FROM DUAL. For more information on configuring datasources, see How to configure BasicDataSource Configuration Parameters.

For additional datasource configuration please see the #DATASOURCE section in the Spring property documentation

JNDI

If you would like to use JNDI to configure your datasource, replace the blueriq.audit.consumer.audit-sql-store section in the blueriq-dcm-maintenance-app.yml described above with the following:

datasource
blueriq:
  audit:
    consumer:
      datasource:
        audit-sql-store:               
			jndi-name: java:jboss/datasources/auditConsumerSqlStoreJndiName

Database drivers

Depending on the underlying database, a specific driver needs to be installed on the application server as described on Configuring JDBC database drivers.

User configuration

Finally, update your users.properties configuration to allow users to view audit logs by assigning them the auditor role.

Didn't find the answer you were looking for? Try the advanced search!