The most recent patch for this version is 26.1.8.  Learn more  

Skip to main content
Version: 26.1

Deployment using the JAR file

This section describes how to run the Access Decision Service (ADS) application using its .jar file.

Deploy the application​

The instructions below describe how to deploy and start the ADS application.

Prepare to deploy​

To start the application, you need the following:

  • ADS JAR file

    This is the .jar file you downloaded in the previous steps.

  • Deployment configuration file

    The deployment.yaml file contains the deployment configuration, including file references to a domain and a valid license. Follow the instructions in the Basic configuration section to configure it.

    warning

    deployment.yaml should be in the same folder as the ADS JAR file.

  • Additional JAR files (optional)

    If you want to include additional resources to your deployment, such as a JDBC driver or custom attribute connectors, you must place all relevant .jar files within a lib folder that you create. The required file structure is the following:

    ├─ access-decision-service-26.1.8.jar
    ├─ deployment.yaml
    ├─ lib
        ├─ custom-attribute-connector.jar
        ├─ jbdc-driver.jar

    Read the Attribute connectors section to learn more about Attribute connectors.

    note

    The SQL and Table attribute connectors require a JDBC driver to connect to the database.

Start the application​

To start the deployment process, execute the following command:

*:first-child]:mt-0 hidden>
java -jar <path_to_file>/access-decision-service-26.1.8.jar
*:first-child]:mt-0>
java -jar <path_to_file>\access-decision-service-26.1.8.jar
warning

Make sure to execute the java command from the directory that contains the deployment.yaml and the lib folder.

Verify that ADS is running​

To verify that ADS is running smoothly, you can run a simple health check by running a GET request:

  GET http://localhost:8081/health

This will result in Status: 200 OK with a JSON reply indicating overall system health, component statuses (probes), and relevant details like the following example:

{
    "status": "UP",
    "components": {
        "diskSpace": {
            "status": "UP",
             "details": {
            ...
            }
        },
        "liveness": {
            "status": "UP",
            "details": {
                ...
                }
            }
        },
        "ping": {
            "status": "UP"
        },
        "readiness": {
            "status": "UP",
            "details": {
                ...
                }
            }
        },
        "startup": {
            "status": "UP"
        }
    },
    "groups": [
        "customProbes"
    ]
}

For more information, see the Healthcheck endpoint section.

See the System information endpoint section to learn how to access system data through an administration endpoint.

Next steps​

Explore additional configuration options to optimize your ADS implementation. See the contents of the Additional configuration section for more information: