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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

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:

application-external-flow.properties
# 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 port or the host are missing, the runtime will not start.


How authorization works

When anexternal flow is executed on a different runtime than the one that the current project is open, there needs to be a way in order for the roles of the currently logged in user to be validated on the target runtime where the external flow resides to.


  • No labels