Versions Compared

Old Version 1

changes.mady.by.user Timo Schrijvers

Saved on

compared with

New Version 2

changes.mady.by.user Timo Schrijvers

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Since Audit Consumer 4.2 the audit consumer supports a multi-tenant event store. Enabling multi-tenancy means that properties for listening for to audit events messages and and storing these audit event messages to a database can be configured for each tenant. For the sql datastore audit event store only the properties properties url, username, password and JNDI are multi-tenant. JNDI is only used required when a JNDI setup is used.  Below Below are examples of how to configure a multi-tenant setup for the audit consumer. 

...

Code Block
languageyml
titleConfiguration YAML
# Audit SQLevent datasourcestore
blueriq:
  audit:
	consumer:
      datasource:
        audit-sql-store:
	      driver-class-name: <driver-class>
          validation-query: <validation-query>
          testWhileIdle: true
          timeBetweenEvictionRunsMillis: 5000
	    	tenants:
		    Apple:
           	  url: <url>
        	  username: <username>
        	  password: <password>
		    Google:
        	  url: <url>
        	  username: <username>
        	  password: <password>
# RabbitMQ
blueriq:
  audit:
    consumer:
      rabbitmq:
		tenants:
          Apple
  	        host: ---
            port: ---
            virtualHost: ---
     	    username: ---
            password: ---
            ssl:
              enabled: ---
            queueNames: ---
            errorExchange: --- 
          Google:
  	        host: ---
            port: ---
            virtualHost: ---
     	    username: ---
            password: ---
            ssl:
              enabled: ---
            queueNames: ---
            errorExchange: ---

...