#
## AristaFlow configuration for the Runtime Registry
#
# To be able to overwrite the configuration you need to copy this file to 'Runtime.properties'.
# Adapt it for your needs. The file will survive any update installation whereas any file with a
# 'dist'-ending may be updated!
#
# 'docs/configuration.html' is a complete documentation of the configuration of all services,
# components and plugins. Please use this as a reference for the configuration of the runtime
# registry and how to override activity attributes as well as activity configurations.
# The documentation of the configuration of activities can be found in the activity repository.
#  

### Logging of Execution Environments
## The logger provided to execution environments depends on the executable component name of the
## corresponding activity; all instances of activities with the same EC name get the same logger.
## The log files are created within a directory having the name of the EC below a configured log
## directory:
#LogDirectory = ${arflow:arflow.logdir}/execComp
##
## The log level is the same for all execution environment, the same applies to the usage of a CSV
## formatter:
#LogLevel = WARNING
#LogCSV = false
##
## The size of the log files can be configured via the size in bytes per log file and the number of
## log files per logger (EC-name). If this is exceeded, old log entries will be overwritten.
#LogFileSize = 2097152
#LogFileCount = 2
###

### Activity Configuration
## The activity configuration may be used to override configuration values that are valid for
## specific customers only. The overriding configuration needs to use a special pattern, in order
## to use different configuration values for the same activity, a configuration name could be used:
##
## Activity[Test]Configuration.$<ECName>{$<OpName>{$<AName>}}#.<ConfEntryName>
## Activity[Test]Configuration.<ConfName>{$<ECName>{$<OpName>{$<AName>}}}#.<ConfKey>
##
## Depending on the qualification of the configuration entry it may apply to all activities with a
## specific configuration name (optional), a specific EC, a specific operation or a specific
## activity.
##
## The following example shows how to configure a database access that is used at the customer
## site with or without a configuration name. The database component needs a connection URL 
## providing the address of the database server, the username and the password to access the 
## database server.
## Use 'bin/encryptPassword.bat' or 'bin/encryptPassword.sh' to encrypt the password.
##
#ActivityConfiguration.PROD$de.aristaflow.db.SQL#.DB.ConnectionURL = <connectionURL>
#ActivityConfiguration.PROD$de.aristaflow.db.SQL#.DB.UserName = <username>
#ActivityConfiguration.PROD$de.aristaflow.db.SQL#.DB.Password = <password>
##
#ActivityConfiguration.$de.aristaflow.db.SQL#.DB.ConnectionURL = <connectionURL>
#ActivityConfiguration.$de.aristaflow.db.SQL#.DB.UserName = <username>
#ActivityConfiguration.$de.aristaflow.db.SQL#.DB.Password = <password>
###
