Additional deployment properties

For successful deployment, Access Decision Service (ADS) requires the deployment.yaml file that contains all the essential properties needed for the ADS service to function. Additionally, there are optional configuration properties you can use to customize the deployment further which are described in this section.

Important

ADS cannot be running when the configuration is updated. Before editing the deployment.yaml file, stop the ADS service. After finishing your editing, restart ADS for the new configurations to take effect.

Properties	Description
concurrentEvaluation	Enables concurrent or multi-threaded evaluations of Multiple Decision Profile (MDP) requests. If not set, all evaluations will be sequential.
└─numberOfWorkers	Controls the number of workers that can perform decision request evaluations in parallel. The value must be a positive integer. Note: Multiple Decision Profile (MDP) is a standards-based way of grouping multiple similar access requests into a single "batch" request which will reduce the performance cost incurred by over-the-network use. See the Multiple Decision ProfileOpens in a new tab specification, for more information.
attributeConnectorContext	To configure the connection pool for standard attribute connectors that access databases through JDBC, you can set additional attributes according to your specific execution environment.
└─jdbc	Determines that database access is done through JDBC.
└─connectionPool	Sets the sub-properties that will determine the maximum and minimum size of the allowed pool.
├─minimumSize	Defines the minimum connection pool size that is created by each Table or SQL attribute connector at startup. Any additional connections above this minimum will be automatically closed after 10 minutes of inactivity. Set the value to 0 or leave it blank to create connections only when needed. The recommended value is 1. Info: Connections above the minimum number will be closed after a 10-minute period of inactivity.
└─maximumSize	Defines the maximum pool size, which controls the total number of connections (idle and active) your application can maintain to the database. The value should be a non-negative integer. A value of 0 or leaving it unset disables connection pooling altogether.

attributeConnectorContext:
    jdbc:
        connectionPool:
            minimumSize: 5
            maximumSize: 10

concurrentEvaluation:
    numberOfWorkers: 3

Sample of deployment with additional configurations.