Application Development Framework Installation & Upgrade

27/02/2026

This guide summarizes the installation and upgrade procedures for the Application Development Framework (ADF).

Note

For more information on how to migrate existing ADF data, please refer to the dedicated ADF data migration guide.

The ADF Search Application is built within the Application Development Framework (ADF). It is a low-code development platform that provides an architectural basis for fully programmed and customizable frontends, workbenches, and dashboards. The ADF Search Application is a separate out-of-box solution built on the ADF that uses a knowledge graph to provide intelligent semantic search capabilities. It encompasses several features, such as:

searching for documents
highlighting extracted concepts from documents
expanding found concepts using inference tagging
recommending relevant documents

Starting with version 1.8.1, ADF is deployed using a fully cloud-native approach via Helm charts on Kubernetes. The previous installation method using download scripts and standalone WAR files has been replaced by a dockerized, Helm-managed deployment.

Note

While this documentation page summarizes the how to upgrade, install, and uninstall ADF, refer to the Helm Chart for ADF for more information on how to configure and customize your ADF deployment.

For installation and upgrade use the following command:

helm upgrade --install --create-namespace --namespace adf adf ./

To remove a deployed ADF installation, use:

helm uninstall adf

Note

General deployment information for all PoolParty addons (such as ADF) using Docker (Compose) can be found in the Docker compose files as well as the Docker images page.

To deploy the services that complement PoolParty, you can use the addons.yaml file.

Important

Your PoolParty license must have the Semantic Workbench capability in order to use this service.

Before starting the services, copy the nginx configuration files from files/nginx/addons to files/nginx/includes/extra_includes. These will expose the service through nginx on their respective context paths.

Now you can start all services:

docker compose -f docker-compose.yaml -f addons.yaml up -d

In this section: