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

Before you upgrade make sure to read the General Upgrade instructions as well as the Upgrade instructions for previous versions.

The changes are color coded. Orange elements have been changed, Green elements have been added and Red elements have been removed compared to the 16.x release.

Table of contents

DCM Maintenance App configuration

The configuration for the DCM Maintenance App has been changed due to the addition of support for multi-tenancy.

The following properties have been moved:

Properties with the prefix blueriq.dcm.maintenance.app.dlq.listener are moved to the blueriq.dcm.maintenance.app.dlq prefix. The part .listener has been removed.

Properties with the prefix blueriq.dcm.maintenance.app.case-engine.listener are moved to the blueriq.dcm.maintenance.app.case-engine prefix. The part .listener has been removed.

Properties with the prefix blueriq.dcm.maintenance.app.retry are moved to the blueriq.dcm.maintenance.app.dlq.retry prefix. They have been moved to the .dlq section.

Settings RabbitMQ and MongoDB in the maintance app

It is now required to set all RabbitMQ and MongoDB properties in the configuration. If not all properties are set, an error will occur which will let the application fail to start.

Runtime JDBC datasources multitenancy 

The configuration for the multi-tenant JDCB datasources has been changed.

The following properties are no longer tenant specific and should be configured only once per component:

All properties with the prefix blueriq.datasource.comments-sql-store.tenants.<tenant>.driverClassName should be replaced by one occurrence of blueriq.datasource.comments-sql-store.driverClassName.

All properties with the prefix blueriq.datasource.process-sql-store.tenants.<tenant>.driverClassName should be replaced by one occurrence of blueriq.datasource.process-sql-store.driverClassName.

All properties with the prefix blueriq.datasource.trace-sql-store.tenants.<tenant>.driverClassName should be replaced by one occurrence of blueriq.datasource.trace-sql-store.driverClassName.

CDS multitenancy

The configuration for the multi-tenant setup for the CDS has been changed. Multitenancy is moved outside the component and the driverClassName is no longer configurable per tenant.

old
blueriq:
  customerdata:
    multi-tenancy:
      enabled: true
      allowed-tenants: <tenant-name-A>,<tenant-name-B>
 	  # datasources
      tenants: 
        <tenant-name-A>: 
          url: <url>
          username: <username>
          password: <password>
          driver-class-name: <driver>
        <tenant-name-B>: 
          url: <url>
          username: <username>
          password: <password>
          driver-class-name: <driver>
new
blueriq:
  multi-tenancy:
    enabled: true
    allowed-tenants: <tenant-name-A>,<tenant-name-B> 
  customerdata:
 	datasource:
      <datasource-name>:
   	    driver-class-name: <driver> 
        tenants: 
          <tenant-name-A>: 
            url: <url>
            username: <username>
            password: <password>
          <tenant-name-B>: 
            url: <url>
            username: <username>
            password: <password>

DCM Lists Mongodb configuration properties & Multitenancy properties

 MongoDB

The prefix of the mongodb configuration properties in the dcm lists have changed. 

Properties with the prefix spring.data.mongodb are moved to blueriq.dcm.lists.mongodb. 

Multitenancy

The configuration for the multi-tenant setup for the DCM lists has been changed. Multitenancy is moved outside the component.

dcm lists old
blueriq:
  dcm:
    lists:
      multi-tenancy:
        enabled: true
        allowed-tenants:
          - <tenant-name-A>
          - <tenant-name-B>
        tenants:
          <tenant-name-A>:
            mongodb:
              host: <host>
              port: <port> 
              database: <databaseName>
            rabbitmq:
              host: <host>
              port: <port>
              virtualHost: <virtualHost>
              username: <user>
              password: <password>
              ssl:
                enabled: <boolean>
              queueNames: <queueName>
          <tenant-name-B>:
            mongodb:
              host: <host>
              port: <port>
              database: <databaseName>
            rabbitmq:
              host: <host>
              port: <port>
              virtualHost: <virtualHost>
              username: <user>
              password: <password>
              ssl:
                enabled: <boolean>
              queueNames: <queueName>


dcm lists new
blueriq:
  multi-tenancy:
    enabled: true
    allowed-tenants:
      - <tenant-name-A>
      - <tenant-name-B>
  dcm:
    lists:
      mongodb:
        tenants:
          <tenant-name-A>:
            host: <host>
            port: <port>
            database: <databaseName>
          <tenant-name-B>:
            host: <host>
            port: <port>
            database: <databaseName>
      event:
        consumer:
          rabbitmq:
            tenants:
              <tenant-name-A>:
                host: <host>
                port: <port>
                virtualHost: <virtualHost>
                username: <user>
                password: <password>
                ssl:
                  enabled: <boolean>
                queueNames: <queueName>
              <tenant-name-B>:
                host: <host>
                port: <port>
                virtualHost: <virtualHost>
                username: <user>
                password: <password>
                ssl:
                  enabled: <boolean>
                queueNames: <queueName>

Audit Component Reliance on Profile attributes

The configuration for the Audit Component has been changed. A number of properties have been removed as they are no longer needed because the information needed will be gathered internally.

The following properties have been removed: 

  • blueriq.audit.domain.processNameAttribute
  • blueriq.audit.domain.caseIdAttribute
  • blueriq.audit.domain.taskIdAttribute
  • blueriq.audit.domain.taskNameAttribute

Auditlog viewer has been removed from the DCM-Maintenance-APP

The audit-log is stored in the Database by the audit-viewer component (Case-Engine setup only). It could be viewed from the DCM-Maintenance-APP before, this has been removed in Blueriq 16.9. The following configuration is not longer relevant and can be removed:

bootstrap.yml
# default profile is always enabled, so you probably don't need to have a bootstrap.yml file at all.
spring:
  profiles:
    active: audit


blueriq-dcm-maintenance-app.yml
blueriq:
  dcm:
    maintenance:
      app:
        audit:
		  *
spring:
  jpa:
    *


Known issues

For an overview of known issue please refer to: Known issues.

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