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 |
---|---|
licenseExpirationWarning | Determines the lead time (in days) for ADS to issue a warning message notifying of an approaching license expiration. The default value is 30 days. Info: The log entry will look similar to this: WARN [2024-02-08 08:50:34,489] com.axiomatics.ads.license.LicenseChecker: License expires in 100 days |
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. |
├─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. The recommended value is 5 . |
└─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. |
server | Serves as a container for specifying how the server operates and interacts with clients and administrative users, ensuring efficient and secure handling of requests. |
└─applicationConnectors | Specifies the connectors used for handling incoming application traffic. These connectors define how the server listens for requests from client applications, including the protocol type such as, HTTP or HTTPS and the port numbers. |
├─adminConnectors | Configures the connectors that are specifically used for administrative purposes. Like application connectors, admin connectors define the protocol type and port, but they are typically set up with enhanced security measures to protect sensitive operations and data. |
└─maxThreads | Defines the maximum number of concurrent threads dedicated to processing requests. Setting a higher value can potentially improve response times, but the appropriate value depends on the environment. The default value is 1024 . It is recommended not to set this value below 8 . |
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. |
license: <path_to_file>/axiomatics_PDP.license
licenseExpirationWarning: 100 days
attributeConnectorContext:
jdbc:
connectionPool:
maximumSize: 5
minimumSize: 1
server:
applicationConnectors:
- type: http
port: 8080
adminConnectors:
- type: http
port: 8081
maxThreads: 1000
concurrentEvaluation:
numberOfWorkers: 8
Sample of deployment with additional configurations.