How do I upgrade from Verint Community 14 or later?

Upgrading from one Community 14 release to a newer Community 14 release is primarily an image replacement plus an installer run against your existing data.

Prerequisites

Preserve Persistent Data

Before replacing images, back up these three sets of data. Their locations are defined within the compose stack.

SQL Server data
CFS content
Solr data

Bind mounts make this process easier to inspect, back up, and control, but named volumes also work if you retain them.

Replace Images

Pull the newer Community 14 images by updating your Compose file's image references:

# ...
web:
  # ...
  image: af1.verintconnect.com/dfe-community/community/web:<VERSION>
  # ...
job:
  # ...
  image: af1.verintconnect.com/dfe-community/community/job:<VERSION>
  # ...
search:
  # ...
  image: af1.verintconnect.com/dfe-community/community/search:<VERSION>
  # ...
infra:
  # ...
  image: af1.verintconnect.com/dfe-community/community/infra:<VERSION>
  # ...
installer:
  ## ...
  image: af1.verintconnect.com/dfe-community/community/installer:<VERSION>
  # ...

Stop the stack

Temporarily stop the compose stack.

docker compose down --remove-orphans

Upgrade the database

A benefit of using the stack is that it will also re-run the installer container at startup to check if the database requires upgrades and perform them if necessary. Therefore, it should not normally be necessary to do this manually.

If your release requires a fuller update path than schema patches alone, set DB_FORCE_UPGRADE=true and run the installer manually.

DB_FORCE_UPGRADE=true docker compose up installer

Review the Search Index

If the version of the search image is changing, clear the volume mounted by the search container.

For a volume mount:

docker volume rm name_of_search_volume

If using a file mount such as:

search:
  # ...
  volumes:
    - ./data/solr:/var/solr
  # ...

Then delete the contents of ./data/solr.

Bring the Stack Back Up

Start the supporting services and application tier:

docker compose up -d --remove-orphans

Review logs for startup failures, repeated schema work, or plugin/file installation errors.

Validate

Community loads successfully
Background jobs resume
Health checks pass in Administration
Expected plugins still load
CFS content is intact

Rollback Planning

For local testing, the simplest rollback is usually:

Stop the upgraded stack
Restore the previous SQL/CFS/Solr state
Restore the previous image set
Start the earlier release again

If you cannot restore prior data state, assume the database may no longer be safely reusable by the earlier release.