Quickstart: JAR deployment

This guide walks you through running the Access Decision Service (ADS) from its JAR file using the minimum configuration required in under 10 minutes.

Prerequisites

• Java SE 17 (64-bit) or Java SE 21 (64-bit) installed and available on your PATH
• License file: axiomatics_ADS.license, provided by Axiomatics
• ADS JAR file: downloaded as described in Prepare your environment
• Authorization domain file: a domain.yaml file from Axiomatics or your own domain configuration

Steps

1. Arrange your files

Create a working directory and place these files inside it:

├─ access-decision-service-26.2.1.jar
├─ axiomatics_ADS.license
├─ deployment.yaml
├─ domain.yaml

caution

Place deployment.yaml in the same directory as the JAR. ADS looks for it in the current working directory at startup.

2. Create a minimal deployment.yaml

Create deployment.yaml with the following content:

engine:
  mode: ads

license: file:axiomatics_ADS.license

domain:
  path: domain.yaml

spring:
  security:
    user:
      name: admin
      password: changeme

tip

Use environment variables for passwords. The syntax ${MY_ENV_VAR:default_value} works anywhere in deployment.yaml.

With this configuration, ADS starts with the following defaults:

Setting	Value
Mode	ads (core ADS service only)
Domain	Loaded from the local domain.yaml file
Port	8080
Authentication	HTTP Basic, with the username and password you set above

For a more complete starting point, including extended options for TLS, caching, and logging, see Deployment configuration samples.

3. Run the JAR

From the directory that contains deployment.yaml, run:

java -jar access-decision-service-26.2.1.jar

4. Verify the service

Send a request to the health endpoint:

GET http://localhost:8080/health

note

By default, management endpoints (including /health) are accessible on server.port (default: 8080). If you have configured a separate management.server.port, use that port instead. See Configuration reference.

ADS returns HTTP 200 OK with a JSON body when it is healthy:

{
  "status": "UP"
}

Next steps

• Full JAR deployment guide: file structure, additional JARs, and troubleshooting
• Configure ADS: domain, authentication, TLS, logging, and caching
• Deployment configuration samples: basic and extended deployment.yaml templates