KB-1157 How to reset the analytics engines for self-managed installations of Appian

Purpose

This article outlines the process to reset the Analytics Engines in self-managed installations of Appian.

NOTE: These steps should only be performed when advised to do so by Appian Technical Support. They should only be performed on the process analytics engine. These steps are not supported on any other engine.

Instructions

Note: For the most up-to-date steps, always refer to the official Appian documentation. The steps below are provided as a reference for common deployment types.

Appian on Kubernetes (AoK)

Resetting the analytics engines on AoK requires a number of extra steps.

  1. Shut down the webapp cluster by scaling its statefulset to 0.
    kubectl -n <namespace> scale statefulset appian-webapp --replicas=0
  2. Checkpoint the execution and process-design engines.
    kubectl -n <namespace> exec -i --tty appian-service-manager-<engine>-0 -- ./serviceManagerScriptWrapper.sh services/bin/checkpoint.sh -s execution,process-design -w
  3. Scale down the execution engine statefulset to 0.
    kubectl -n <namespace> scale statefulset appian-service-manager-execution<XX> --replicas=0
  4. (If the site is HA) Scale down the analytics engine statefulset to 1.
    kubectl -n <namespace> scale statefulset appian-service-manager-analytics<XX> --replicas=1
  5. Scale down the process-design statefulset to 0.
    kubectl -n <namespace> scale statefulset appian-service-manager-process-design --replicas=0
  6. Stop the analytics engine with the OOTB script from within each analytics engine pod.
    kubectl -n <namespace> exec -i --tty appian-service-manager-analytics<XX>-0 -- ./serviceManagerScriptWrapper.sh services/bin/stop.sh -s analytics<XX>
  7. Reset the analytics engine with the OOTB script from within each analytics engine pod.
    kubectl -n <namespace> exec -i --tty appian-service-manager-analytics<XX>-0 -- ./serviceManagerScriptWrapper.sh services/bin/resetAnalytics.sh -s analytics<XX>
  8. Scale all statefulsets back up to their desired number.

Classic Linux

  1. Stop all app servers.
    <APPIAN_HOME>/tomcat/apache-tomcat/bin/stop-appserver.sh
  2. Stop the execution, analytics, and process-design engines.
    <APPIAN_HOME>/services/bin/stop.sh -p <SM_PASSWORD> -s analytics,execution,process-design
  3. Reset the analytics engine with the OOTB script.
    <APPIAN_HOME>/services/bin/resetAnalytics.sh -p <SM_PASSWORD> -s analytics<XX>
  4. Start the engines back up.
    <APPIAN_HOME>/services/bin/start.sh -s analytics,execution,process-design
  5. Start the app server.
    <APPIAN_HOME>/tomcat/apache-tomcat/bin/start-appserver.sh

Affected Versions

This article applies to all versions of self-managed installations of Appian.

Last Reviewed: April 2026

Related
Recommended