You are viewing the documentation for Blueriq 14. Documentation for other versions is available in our documentation directory.
Configuration
In order to enable this component, the following profile has to be enabled: external-flow. The below example illustrates how the bootstrap.properties file should look like:
bootstrap.properties
spring.profiles.active=native,...,external-flow
The file application-external-flow.properties must be available and should be configured as follows:
| Subject | Property | Default | Explanation | Property file | Additional information |
|---|---|---|---|---|---|
| External Flow Component | blueriq.external-flow.store-type | memory | The data store type, having two possible values: memory and redis. memory is the default one. |
| |
| blueriq.external-flow.redis-store.database | 0 | The Database index used by the connection factory. |
| ||
| blueriq.external-flow.redis-store.host | localhost | The REQUIRED DNS name or IP address of the Redis server. |
| ||
| blueriq.external-flow.redis-store.port | 6379 | The REQUIRED port on which to connect to Redis. |
| ||
| blueriq.external-flow.redis-store.ssl | false | Whether to enable SSL support |
| ||
| blueriq.external-flow.redis-store.password | The password used to connect to Redis, can be left empty if no password is required. |
| |||
| blueriq.external-flow.redis-store.timeout | 2000 | Timeoud (ms) for connect and read operations |
| ||
| blueriq.external-flow.redis-store.client-name | Client name to be set on connections. Can be left empty. |
| |||
| Redis pool configuration | blueriq.external-flow.redis-store.jedis.pool.maxIdle | 8 | Maximum number of "idle" connections in the pool. Use a negative value to indicate an unlimited number of idle connections. |
| |
| blueriq.external-flow.redis-store.jedis.pool.minIdle | 0 | Target for the minimum number of idle connections to maintain in the pool. This setting only has an effect if it is positive. |
| ||
| blueriq.external-flow.redis-store.jedis.pool.maxActive | 8 | Maximum number of connections that can be allocated by the pool at a given time. Use a negative value for no limit. |
| ||
| blueriq.external-flow.redis-store.jedis.pool.maxWait | -1 | Maximum amount of time a connection allocation should block before throwing an exception when the pool is exhausted. Use a negative value to block indefinitely. |
| ||
| blueriq.external-flow.redis-store.jedis.pool.timeBetweenEvictionRuns | Time between runs of the idle object evictor thread. When positive, the idle object evictor thread starts, otherwise no idle object eviction is performed. Can be left empty. |
|
Example configuration file :
application-external-flow.properties
# The data store type, having two possible values: memory and redis. memory is the default one. blueriq.external-flow.store-type=redis # The Database index used by the connection factory. blueriq.external-flow.redis-store.database=0 # The REQUIRED DNS name or IP address of the Redis server. blueriq.external-flow.redis-store.host= # The password used to connect to Redis, can be left empty if no password is required. blueriq.external-flow.redis-store.password= # The REQUIRED port on which to connect to Redis. blueriq.external-flow.redis-store.port= ### Pool configuration ### # Maximum number of "idle" connections in the pool. # Use a negative value to indicate an unlimited number of idle connections. blueriq.external-flow.redis-store.pool.maxIdle=8 # Target for the minimum number of idle connections to maintain in the pool. # This setting only has an effect if it is positive. blueriq.external-flow.redis-store.pool.minIdle=0 # Maximum number of connections that can be allocated by the pool at a given time. # Use a negative value for no limit. blueriq.external-flow.redis-store.pool.maxActive=8 # Maximum amount of time a connection allocation should block before throwing an exception when the pool is exhausted. # Use a negative value to block indefinitely. blueriq.external-flow.redis-store.pool.maxWait=-1
If the data store type is not specified, the memory store will be used.
Please note that using a memory store type will make it impossible for you to start an external flow that resides on a different Runtime.
The other
Please note that using a memory store type will make it impossible for you to start an external flow that resides on a different Runtime.
The other
blueriq.external-flow.redis-store* properties will be ignored in this case.If redis data store is used and the properties for configuring the host and/or the port are missing, the Runtime will not start.
Overview
Content Tools