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

pauline.delacruz — Wed, 01 Apr 2026 16:43:59 GMT

Current Revision posted to Appian Knowledge Base by pauline.delacruz on 4/1/2026 4:43:59 PM

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.

Shut down the webapp cluster by scaling its statefulset to 0.

kubectl -n <namespace> scale statefulset appian-webapp --replicas=0

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

Scale down the execution engine statefulset to 0.

kubectl -n <namespace> scale statefulset appian-service-manager-execution<XX> --replicas=0

(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

Scale down the process-design statefulset to 0.

kubectl -n <namespace> scale statefulset appian-service-manager-process-design --replicas=0

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>

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>

Scale all statefulsets back up to their desired number.

Classic Linux

Stop all app servers.

<APPIAN_HOME>/tomcat/apache-tomcat/bin/stop-appserver.sh

Stop the execution, analytics, and process-design engines.

<APPIAN_HOME>/services/bin/stop.sh -p <SM_PASSWORD> -s analytics,execution,process-design

Reset the analytics engine with the OOTB script.

<APPIAN_HOME>/services/bin/resetAnalytics.sh -p <SM_PASSWORD> -s analytics<XX>

Start the engines back up.

<APPIAN_HOME>/services/bin/start.sh -s analytics,execution,process-design

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

Tags: self-managed, engines, infrastructure

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

Parmida Borhani — Tue, 29 Sep 2020 03:17:00 GMT

Revision 16 posted to Appian Knowledge Base by Parmida Borhani on 9/29/2020 3:17:00 AM

Purpose

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

Instructions

18.2.70.0 and later

Follow the steps exactly as documented here.

17.3 - 18.2.69.0

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Run the Reset Analytics Script.
Start all engines except for Execution and Analytics.
Run the Status Script to ensure these engines have come up.
Start the Analytics engines.
Run the Status Script to ensure these engines have come up.
Wait for CPU usage to stabilize.
Start the Execution engines.
Run the Status Script again to ensure all the engines are okay.
Wait for CPU usage to stabilize.
Checkpoint all engines.
Start the search server.
Start the application server.

17.2 and earlier

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Delete all files ending in .kdb in the Analytics Engine gateway directories (<APPIAN_HOME>/server/process/analytics/00XX/gw1).
Note: If you have additional gateway directories (gwX) with engine database files (pa*.kdb) in them, you need to delete those files as well for each analytics engine.

Example Unix commands:
```
cd <APPIAN_HOME>/server/process/analytics/00**/gw* rm pa*.kdb
```
Example Windows commands:
```
cd <APPIAN_HOME>\server\process\analytics\00**\gw* del pa*.kdb
```
Start all engines except for Execution and Analytics. This can be done by running the start-gw commands specific to your operating system located in <APPIAN_HOME>/server/_scripts/<ENGINE_NAME> (make sure you exclude running the scripts from the exec and analytics folders for this step).
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start all Analytics engines only. This can be done by running the start-gw command specific to your operating system located in <APPIAN_HOME>/server/_scripts/analytics/.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start all Execution engines only. This can be done by running the start-gw command specific to your operating system located in <APPIAN_HOME>/server/_scripts/exec/.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Wait for CPU usage to stabilize on the machine.
Checkpoint all engines using the checkpoint script, located in <APPIAN_HOME>/server/_scripts.
Start the search server.
Start the application server.

Affected Versions

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

Last Reviewed: October 2019

Tags: self-managed, engines, infrastructure

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

Rebecca Jonas — Fri, 25 Oct 2019 18:48:00 GMT

Revision 15 posted to Appian Knowledge Base by Rebecca Jonas on 10/25/2019 6:48:00 PM

Purpose

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

Instructions

18.2.70.0 and later

Follow the steps exactly as documented here.

17.3 - 18.2.69.0

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Run the Reset Analytics Script.
Start all engines except for Execution and Analytics.
Run the Status Script to ensure these engines have come up.
Start the Analytics engines.
Run the Status Script to ensure these engines have come up.
Wait for CPU usage to stabilize.
Start the Execution engines.
Run the Status Script again to ensure all the engines are okay.
Wait for CPU usage to stabilize.
Checkpoint all engines.
Start the search server.
Start the application server.

17.2 and earlier

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Delete all files ending in .kdb in the Analytics Engine gateway directories (<APPIAN_HOME>/server/process/analytics/00XX/gw1).
Note: If you have additional gateway directories (gwX) with engine database files (pa*.kdb) in them, you need to delete those files as well for each analytics engine.

Example Unix commands:
```
cd <APPIAN_HOME>/server/process/analytics/00**/gw* rm pa*.kdb
```
Example Windows commands:
```
cd <APPIAN_HOME>\server\process\analytics\00**\gw* del pa*.kdb
```
Start all engines except for Execution and Analytics. This can be done by running the start-gw commands specific to your operating system located in <APPIAN_HOME>/server/_scripts/<ENGINE_NAME> (make sure you exclude running the scripts from the exec and analytics folders for this step).
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start all Analytics engines only. This can be done by running the start-gw command specific to your operating system located in <APPIAN_HOME>/server/_scripts/analytics/.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start all Execution engines only. This can be done by running the start-gw command specific to your operating system located in <APPIAN_HOME>/server/_scripts/exec/.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Wait for CPU usage to stabilize on the machine.
Checkpoint all engines using the checkpoint script, located in <APPIAN_HOME>/server/_scripts.
Start the search server.
Start the application server.

Affected Versions

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

Last Reviewed: October 2019

Tags: engines, infrastructure

KB-1157 How to reset the analytics engines for on-premise installations of Appian

Parmida Borhani — Fri, 21 Jun 2019 04:09:53 GMT

Revision 14 posted to Appian Knowledge Base by Parmida Borhani on 6/21/2019 4:09:53 AM

Purpose

This article outlines the process to reset the Analytics Engines in on-premise installations of Appian.

Instructions

18.2.70 and later

Follow the steps exactly as documented here.

17.3 - 18.2.0.69

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Run the Reset Analytics Script.
Start all engines except for Execution and Analytics.
Run the Status Script to ensure these engines have come up.
Start the Analytics engines.
Run the Status Script to ensure these engines have come up.
Wait for CPU usage to stabilize.
Start the Execution engines.
Run the Status Script again to ensure all the engines are okay.
Wait for CPU usage to stabilize.
Checkpoint all engines.
Start the search server.
Start the application server.

17.2 and earlier

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Delete all files ending in .kdb in the Analytics Engine gateway directories (<APPIAN_HOME>/server/process/analytics/00XX/gw1).
Note: If you have additional gateway directories (gwX) with engine database files (pa*.kdb) in them, you need to delete those files as well for each analytics engine.

Example Unix commands:
```
cd <APPIAN_HOME>/server/process/analytics/00**/gw*
rm pa*.kdb
```
Example Windows commands:
```
cd <APPIAN_HOME>\server\process\analytics\00**\gw*
del pa*.kdb
```
Start all engines except for Execution and Analytics. This can be done by running the start-gw commands specific to your operating system located in <APPIAN_HOME>/server/_scripts/<ENGINE_NAME> (make sure you exclude running the scripts from the exec and analytics folders for this step).
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start all Analytics engines only. This can be done by running the start-gw command specific to your operating system located in <APPIAN_HOME>/server/_scripts/analytics/.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start all Execution engines only. This can be done by running the start-gw command specific to your operating system located in <APPIAN_HOME>/server/_scripts/exec/.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Wait for CPU usage to stabilize on the machine.
Checkpoint all engines using the checkpoint script, located in <APPIAN_HOME>/server/_scripts.
Start the search server.
Start the application server.

Affected Versions

This article applies to all versions of on-premise installations of Appian.

Last Reviewed: June 2019

Tags: engines, infrastructure

KB-1157 How to reset the analytics engines for on-premise installations of Appian

Parmida Borhani — Fri, 21 Jun 2019 04:09:18 GMT

Revision 13 posted to Appian Knowledge Base by Parmida Borhani on 6/21/2019 4:09:18 AM

Purpose

This article outlines the process to reset the Analytics Engines in on-premise installations of Appian.

Instructions

18.2.70 and later

Follow the steps exactly as documented here.

17.3 - 18.2.0.69

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Run the Reset Analytics Script.
Start all engines except for Execution and Analytics.
Run the Status Script to ensure these engines have come up.
Start the Analytics engines.
Run the Status Script to ensure these engines have come up.
Wait for CPU usage to stabilize.
Start the Execution engines.
Run the Status Script again to ensure all the engines are okay.
Wait for CPU usage to stabilize.
Checkpoint all engines.
Start the search server.
Start the application server.

17.2 and earlier

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Delete all files ending in .kdb in the Analytics Engine gateway directories (<APPIAN_HOME>/server/process/analytics/00XX/gw1).
Note: If you have additional gateway directories (gwX) with engine database files (pa*.kdb) in them, you need to delete those files as well for each analytics engine.

Example Unix commands:
```
cd <APPIAN_HOME>/server/process/analytics/00**/gw*
rm pa*.kdb
```
Example Windows commands:
```
cd <APPIAN_HOME>\server\process\analytics\00**\gw*
del pa*.kdb
```
Start all engines except for Execution and Analytics. This can be done by running the start-gw commands specific to your operating system located in <APPIAN_HOME>/server/_scripts/<ENGINE_NAME> (make sure you exclude running the scripts from the exec and analytics folders for this step).
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start all Analytics engines only. This can be done by running the start-gw command specific to your operating system located in <APPIAN_HOME>/server/_scripts/analytics/.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start all Execution engines only. This can be done by running the start-gw command specific to your operating system located in <APPIAN_HOME>/server/_scripts/exec/.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Wait for CPU usage to stabilize on the machine.
Checkpoint all engines using the checkpoint script, located in <APPIAN_HOME>/server/_scripts.
Start the search server.
Start the application server.

Affected Versions

This article applies to all versions of on-premise installations of Appian.

Last Reviewed: June 2019

Tags: engines, infrastructure

KB-1157 How to reset the analytics engines for on-premise installations of Appian

Parmida Borhani — Fri, 21 Jun 2019 04:08:52 GMT

Revision 12 posted to Appian Knowledge Base by Parmida Borhani on 6/21/2019 4:08:52 AM

Purpose

This article outlines the process to reset the Analytics Engines in on-premise installations of Appian.

Instructions

18.2.70 and later

Follow the steps exactly as documented here.

17.3 - 18.2.0.69

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Run the Reset Analytics Script.
Start all engines except for Execution and Analytics.
Run the Status Script to ensure these engines have come up.
Start the Analytics engines.
Run the Status Script to ensure these engines have come up.
Wait for CPU usage to stabilize.
Start the Execution engines.
Run the Status Script again to ensure all the engines are okay.
Wait for CPU usage to stabilize.
Checkpoint all engines.
Start the search server.
Start the application server.

17.2 and earlier

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Delete all files ending in .kdb in the Analytics Engine gateway directories (<APPIAN_HOME>/server/process/analytics/00XX/gw1).
Note: If you have additional gateway directories (gwX) with engine database files (pa*.kdb) in them, you need to delete those files as well for each analytics engine.

Example Unix commands:
```
cd <APPIAN_HOME>/server/process/analytics/00**/gw*
rm pa*.kdb
```
Example Windows commands:
```
cd <APPIAN_HOME>\server\process\analytics\00**\gw*
del pa*.kdb
```
Start all engines except for Execution and Analytics. This can be done by running the start-gw commands specific to your operating system located in <APPIAN_HOME>/server/_scripts/<ENGINE_NAME> (make sure you exclude running the scripts from the exec and analytics folders for this step).
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start all Analytics engines only. This can be done by running the start-gw command specific to your operating system located in <APPIAN_HOME>/server/_scripts/analytics/.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start all Execution engines only. This can be done by running the start-gw command specific to your operating system located in <APPIAN_HOME>/server/_scripts/exec/.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Wait for CPU usage to stabilize on the machine.
Checkpoint all engines using the checkpoint script, located in <APPIAN_HOME>/server/_scripts.
Start the search server.
Start the application server.

Affected Versions

This article applies to all versions of on-premise installations of Appian.

Last Reviewed: June 2019

Tags: engines, infrastructure

KB-1157 How to reset the analytics engines for on-premise installations of Appian

Parmida Borhani — Mon, 30 Jul 2018 04:12:32 GMT

Revision 11 posted to Appian Knowledge Base by Parmida Borhani on 7/30/2018 4:12:32 AM

This article outlines the process to reset the Analytics Engines in on-premise installations of Appian.

NOTE: These steps should only be performed when advised to do so by Appian Technical Support.

NOTE: These steps should only be performed on the process analytics engine. These steps are not supported on any other engine.

For Appian versions 17.3 and later, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Run the Reset Analytics Script.
Start all engines except for Execution and Analytics.
Run the Status Script to ensure these engines have come up.
Start the Analytics engines.
Run the Status Script to ensure these engines have come up.
Wait for CPU usage to stabilize.
Start the Execution engines.
Run the Status Script again to ensure all the engines are okay.
Wait for CPU usage to stabilize.
Checkpoint all engines.
Start the search server.
Start the application server.

For Appian versions 17.2 and earlier, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Delete all files ending in .kdb in the Analytics Engine gateway directories (<APPIAN_HOME>/server/process/analytics/00XX/gw1).
Note: If you have additional gateway directories (gwX) with engine database files (pa*.kdb) in them, you need to delete those files as well for each analytics engine.

Example Unix commands:
```
cd <APPIAN_HOME>/server/process/analytics/00**/gw*
rm pa*.kdb
```
Example Windows commands:
```
cd <APPIAN_HOME>\server\process\analytics\00**\gw*
del pa*.kdb
```
Start all engines except for Execution and Analytics. This can be done by running the start-gw commands specific to your operating system located in <APPIAN_HOME>/server/_scripts/<ENGINE_NAME> (make sure you exclude running the scripts from the exec and analytics folders for this step).
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start all Analytics engines only. This can be done by running the start-gw command specific to your operating system located in <APPIAN_HOME>/server/_scripts/analytics/.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start all Execution engines only. This can be done by running the start-gw command specific to your operating system located in <APPIAN_HOME>/server/_scripts/exec/.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Wait for CPU usage to stabilize on the machine.
Checkpoint all engines using the checkpoint script, located in <APPIAN_HOME>/server/_scripts.
Start the search server.
Start the application server.

Affected Versions

This article applies to all versions of on-premise installations of Appian.

Last Reviewed: February 2018

Tags: engines, infrastructure

KB-1157 How to reset the analytics engines for on-premise installations of Appian

Nick Vigilante — Mon, 26 Feb 2018 11:46:04 GMT

Revision 10 posted to Appian Knowledge Base by Nick Vigilante on 2/26/2018 11:46:04 AM

This article outlines the process to reset the Analytics Engines in on-premise installations of Appian.

NOTE: These steps should only be performed when advised to do so by Appian Technical Support.

NOTE: These steps should only be performed on the process analytics engine. These steps are not supported on any other engine.

For Appian versions 17.3 and later, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Run the Reset Analytics Script.
Start all engines except for Execution and Analytics.
Run the Status Script to ensure these engines have come up.
Start the Analytics engines.
Run the Status Script to ensure these engines have come up.
Wait for CPU usage to stabilize.
Start the Execution engines.
Run the Status Script again to ensure all the engines are okay.
Wait for CPU usage to stabilize.
Checkpoint all engines.
Start the search server.
Start the application server.

For Appian versions 17.2 and earlier, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Delete all files ending in .kdb in the Analytics Engine gateway directories (<APPIAN_HOME>/server/process/analytics/00XX/gw1).
Note: If you have additional gateway directories (gwX) with engine database files (pa*.kdb) in them, you need to delete those files as well for each analytics engine.

Example Unix commands:
```
cd <APPIAN_HOME>/server/process/analytics/00**/gw*
rm pa*.kdb
```
Example Windows commands:
```
cd <APPIAN_HOME>\server\process\analytics\00**\gw*
del pa*.kdb
```
Start all engines except for Execution and Analytics. This can be done by running the start-gw commands specific to your operating system located in <APPIAN_HOME>/server/_scripts/<ENGINE_NAME> (make sure you exclude running the scripts from the exec and analytics folders for this step).
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start all Analytics engines only. This can be done by running the start-gw command specific to your operating system located in <APPIAN_HOME>/server/_scripts/analytics/.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start all Execution engines only. This can be done by running the start-gw command specific to your operating system located in <APPIAN_HOME>/server/_scripts/exec/.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Wait for CPU usage to stabilize on the machine.
Checkpoint all engines using the checkpoint script, located in <APPIAN_HOME>/server/_scripts.
Start the search server.
Start the application server.

Affected Versions

This article applies to all versions of on-premise installations of Appian.

Last Reviewed: February 2018

Tags: engines

KB-1157 How to reset the analytics engines for on-premise installations of Appian

Nick Vigilante — Mon, 26 Feb 2018 10:53:35 GMT

Revision 9 posted to Appian Knowledge Base by Nick Vigilante on 2/26/2018 10:53:35 AM

This article outlines the process to reset the Analytics Engines in on-premise installations of Appian.

NOTE: These steps should only be performed when advised to do so by Appian Technical Support.

NOTE: These steps should only be performed on the process analytics engine. These steps are not supported on any other engine.

For Appian versions 17.3 and later, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Run the Reset Analytics Script.
Start all engines except for Execution and Analytics.
Run the Status Script to ensure these engines have come up.
Start the Analytics engines.
Run the Status Script to ensure these engines have come up.
Wait for CPU usage to stabilize.
Start the Execution engines.
Run the Status Script again to ensure all the engines are okay.
Wait for CPU usage to stabilize.
Checkpoint all engines.
Start the search server.
Start the application server.

For Appian versions 17.2 and earlier, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Delete all files ending in .kdb in the Analytics Engine gateway directories (<APPIAN_HOME>/server/process/analytics/00XX/gw1).
Note: If you have additional gateway directories (gwX) with engine database files (pa*.kdb) in them, you need to delete those files as well for each analytics engine.

Example Unix commands:
```
cd <APPIAN_HOME>/server/process/analytics/00**/gw*
rm pa*.kdb
```
Example Windows commands:
```
cd <APPIAN_HOME>\server\process\analytics\00**\gw*
del pa*.kdb
```
In <APPIAN_HOME>/server/process/analytics, copy the file named pa.kdb into each engine/gateway directory (<APPIAN_HOME>/server/process/analytics/00XX/gwX) and rename each copy to pa1.kdb. Do not rename the original file.
Start all engines except for Execution and Analytics. This can be done by running the start-gw commands specific to your operating system located in <APPIAN_HOME>/server/_scripts/<ENGINE_NAME> (make sure you exclude running the scripts from the exec and analytics folders for this step).
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start all Analytics engines only. This can be done by running the start-gw command specific to your operating system located in <APPIAN_HOME>/server/_scripts/analytics/.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start all Execution engines only. This can be done by running the start-gw command specific to your operating system located in <APPIAN_HOME>/server/_scripts/exec/.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Wait for CPU usage to stabilize on the machine.
Checkpoint all engines using the checkpoint script, located in <APPIAN_HOME>/server/_scripts.
Start the search server.
Start the application server.

Affected Versions

This article applies to all versions of on-premise installations of Appian.

Last Reviewed: February 2018

Tags: engines

KB-1157 How to reset the analytics engines for on-premise installations of Appian

Parmida Borhani — Wed, 31 Jan 2018 00:14:51 GMT

Revision 8 posted to Appian Knowledge Base by Parmida Borhani on 1/31/2018 12:14:51 AM

This article outlines the process to reset the Analytics Engines in on-premise installations of Appian.

NOTE: These steps should only be performed when advised to do so by Appian Technical Support.

NOTE: These steps should only be performed on the process analytics engine. These steps are not supported on any other engine.

For Appian versions 17.3 and later, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Run the Reset Analytics Script.
Start all engines except for Execution and Analytics.
Run the Status Script to ensure these engines have come up.
Start the Analytics engines.
Run the Status Script to ensure these engines have come up.
Wait for CPU usage to stabilize.
Start the Execution engines.
Run the Status Script again to ensure all the engines are okay.
Wait for CPU usage to stabilize.
Checkpoint all engines.
Start the search server.
Start the application server.

For Appian versions 17.2 and earlier, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Delete all files ending in .kdb in the Analytics Engine gateway directories (<APPIAN_HOME>/server/process/analytics/00XX/gw1).
Note: If you have additional gateway directories (gwX) with engine database files (pa*.kdb) in them, you need to delete those files as well for each analytics engine.

Example Unix commands:
```
cd <APPIAN_HOME>/server/process/analytics/00**/gw*
rm pa*.kdb
```
Example Windows commands:
```
cd <APPIAN_HOME>\server\process\analytics\00**\gw*
del pa*.kdb
```
In <APPIAN_HOME>/server/process/analytics, copy the file named pa.kdb into each engine/gateway directory (<APPIAN_HOME>/server/process/analytics/00XX/gwX) and rename each copy to pa1.kdb. Do not rename the original file.
Start the Appian engines. Wait for the CPU usage to stabilize.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start the search server.
Start the application server.

Affected Versions

This article applies to all versions of on-premise installations of Appian.

Last Reviewed: January 2018

Tags: engines

KB-1157 How to reset the analytics engines for on-premise installations of Appian

Parmida Borhani — Wed, 31 Jan 2018 00:13:34 GMT

Revision 7 posted to Appian Knowledge Base by Parmida Borhani on 1/31/2018 12:13:34 AM

This article outlines the process to reset the Analytics Engines in on-premise installations of Appian.

NOTE: These steps should only be performed when advised to do so by Appian Technical Support.

NOTE: These steps should only be performed on the process analytics engine. These steps are not supported on any other engine.

For Appian versions 17.3 and later, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Run the Reset Analytics Script.
Start all engines except for Execution and Analytics.
Run the Status Script to ensure these engines have come up.
Start the Analytics engines.
Run the Status Script to ensure these engines have come up.
Wait for CPU usage to stabilize.
Start the Execution engines.
Run the Status Script again to ensure all the engines are okay.
Wait for CPU usage to stabilize.
Checkpoint all engines.
Start the search server.
Start the application server.

For Appian versions 17.2 and earlier, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Delete all files ending in .kdb in the Analytics Engine gateway directories (<APPIAN_HOME>/server/process/analytics/00XX/gw1).
Note: If you have additional gateway directories (gwX) with engine database files (pa*.kdb) in them, you need to delete those files as well for each analytics engine.

Example Unix commands:
```
cd <APPIAN_HOME>/server/process/analytics/00**/gw*
rm pa*.kdb
```
Example Windows commands:
```
cd <APPIAN_HOME>\server\process\analytics\00**\gw*
del pa*.kdb
```
In <APPIAN_HOME>/server/process/analytics, copy the file named pa.kdb into each engine/gateway directory (<APPIAN_HOME>/server/process/analytics/00XX/gwX) and rename each copy to pa1.kdb. Do not rename the original file.
Start the Appian engines. Wait for the CPU usage to stabilize.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start the search server.
Start the application server.

Affected Versions

This article applies to all versions of on-premise installations of Appian.

Last Reviewed: November 2017

Tags: engines

KB-1157 How to reset the analytics engines for on-premise installations of Appian

Parmida Borhani — Tue, 05 Dec 2017 22:46:40 GMT

Revision 6 posted to Appian Knowledge Base by Parmida Borhani on 12/5/2017 10:46:40 PM

This article outlines the process to reset the Analytics Engines in on-premise installations of Appian.

NOTE: These steps should only be performed when advised to do so by Appian Technical Support.

NOTE: These steps should only be performed on the process analytics engine. These steps are not supported on any other engine.

For Appian versions 17.3 and above, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Run the Reset Analytics Script.
Start the Appian engines. Wait for the CPU usage to stabilize.
Run the Status Script to ensure all the engines are okay.
Start the search server.
Start the application server.

For Appian versions 17.2 and prior, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Delete all files ending in .kdb in the Analytics Engine gateway directories (<APPIAN_HOME>/server/process/analytics/00XX/gw1).
Note: If you have additional gateway directories (gwX) with engine database files (pa*.kdb) in them, you need to delete those files as well for each analytics engine.

Example Unix commands:
```
cd <APPIAN_HOME>/server/process/analytics/00**/gw*
rm pa*.kdb
```
Example Windows commands:
```
cd <APPIAN_HOME>\server\process\analytics\00**\gw*
del pa*.kdb
```
In <APPIAN_HOME>/server/process/analytics, copy the file named pa.kdb into each engine/gateway directory (<APPIAN_HOME>/server/process/analytics/00XX/gwX) and rename each copy to pa1.kdb. Do not rename the original file.
Start the Appian engines. Wait for the CPU usage to stabilize.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start the search server.
Start the application server.

Affected Versions

This article applies to all versions of on-premise installations of Appian.

Last Reviewed: November 2017

Tags: administration, engines

KB-1157 How to reset the analytics engines for on-premise installations of Appian

Nick Vigilante — Tue, 05 Dec 2017 08:56:31 GMT

Revision 5 posted to Appian Knowledge Base by Nick Vigilante on 12/5/2017 8:56:31 AM

This article outlines the process to reset the Analytics Engines in on-premise installations of Appian.

NOTE: These steps should only be performed when advised to do so by Appian Technical Support.

NOTE: These steps should only be performed on the process analytics engine. These steps are not supported on any other engine.

For Appian versions 17.3 and above, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Run the Reset Analytics Script.
Start the Appian engines. Wait for the CPU usage to stabilize.
Run the Status Script to ensure all the engines are okay.
Start the search server.
Start the application server.

For Appian versions 17.2 and prior, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Delete all files ending in .kdb in the Analytics Engine gateway directories (<APPIAN_HOME>/server/process/analytics/00XX/gw1).
Note: If you have additional gateway directories (gwX) with engine database files (pa*.kdb) in them, you need to delete those files as well for each analytics engine.

Example Unix commands:
```
cd <APPIAN_HOME>/server/process/analytics/00**/gw*
rm pa*.kdb
```
Example Windows commands:
```
cd <APPIAN_HOME>\server\process\analytics\00**\gw*
del pa*.kdb
```
In <APPIAN_HOME>/server/process/analytics, copy the file named pa.kdb into each engine/gateway directory (<APPIAN_HOME>/server/process/analytics/00XX/gwX) and rename each copy to pa1.kdb. Do not rename the original file.
Start the Appian engines. Wait for the CPU usage to stabilize.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start the search server.
Start the application server.

Affected Versions

This article applies to all versions of on-premise installations of Appian.

Last Reviewed: November 2017

Tags: administration, engines

KB-1157 How to reset the analytics engines for on-premise installations of Appian

Parmida Borhani — Wed, 15 Nov 2017 17:24:11 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 11/15/2017 5:24:11 PM

This article outlines the process to reset the Analytics Engines in on-premise installations of Appian.

NOTE: These steps should only be performed when advised to do so by Appian Technical Support.

For Appian versions 17.3 and above, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Run the Reset Analytics Script.
Start the Appian engines. Wait for the CPU usage to stabilize.
Run the Status Script to ensure all the engines are okay.
Start the search server.
Start the application server.

For Appian versions 17.2 and prior, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Delete all files ending in .kdb in the Analytics Engine gateway directories (<APPIAN_HOME>/server/process/analytics/00XX/gw1).
Note: If you have additional gateway directories (gwX) with engine database files (pa*.kdb) in them, you need to delete those files as well for each analytics engine.

Example Unix commands:
```
cd <APPIAN_HOME>/server/process/analytics/00**/gw*
rm pa*.kdb
```
Example Windows commands:
```
cd <APPIAN_HOME>\server\process\analytics\00**\gw*
del pa*.kdb
```
In <APPIAN_HOME>/server/process/analytics, copy the file named pa.kdb into each engine/gateway directory (<APPIAN_HOME>/server/process/analytics/00XX/gwX) and rename each copy to pa1.kdb. Do not rename the original file.
Start the Appian engines. Wait for the CPU usage to stabilize.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start the search server.
Start the application server.

Affected Versions

This article applies to all versions of on-premise installations of Appian.

Last Reviewed: November 2017

Tags: administration, engines

KB-1157 How to reset the analytics engines for on-premise installations of Appian

Parmida Borhani — Wed, 15 Nov 2017 17:23:01 GMT

Revision 3 posted to Appian Knowledge Base by Parmida Borhani on 11/15/2017 5:23:01 PM

This article outlines the process to reset the Analytics Engines in on-premise installations of Appian.

NOTE: These steps should only be performed when advised to do so by Appian Technical Support.

For Appian version 17.3 and above, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Run the Reset Analytics Script.
Start the Appian engines. Wait for the CPU usage to stabilize.
Run the Status Script to ensure all the engines are okay.
Start the search server.
Start the application server.

For Appian version 17.2 and prior, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Delete all files ending in .kdb in the Analytics Engine gateway directories (<APPIAN_HOME>/server/process/analytics/00XX/gw1).
Note: If you have additional gateway directories (gwX) with engine database files (pa*.kdb) in them, you need to delete those files as well for each analytics engine.

Example Unix commands:
```
cd <APPIAN_HOME>/server/process/analytics/00**/gw*
rm pa*.kdb
```
Example Windows commands:
```
cd <APPIAN_HOME>\server\process\analytics\00**\gw*
del pa*.kdb
```
In <APPIAN_HOME>/server/process/analytics, copy the file named pa.kdb into each engine/gateway directory (<APPIAN_HOME>/server/process/analytics/00XX/gwX) and rename each copy to pa1.kdb. Do not rename the original file.
Start the Appian engines. Wait for the CPU usage to stabilize.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start the search server.
Start the application server.

Affected Versions

This article applies to all versions of on-premise installations of Appian.

Last Reviewed: November 2017

Tags: administration, engines

KB-1157 How to reset the analytics engines for on-premise installations of Appian

Parmida Borhani — Wed, 15 Nov 2017 17:22:09 GMT

Revision 2 posted to Appian Knowledge Base by Parmida Borhani on 11/15/2017 5:22:09 PM

This article outlines the process to reset the Analytics Engines in on-premise installations of Appian.

NOTE: These steps should only be performed when advised to do so by Appian Technical Support.

For Appian version 17.3 and above, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Run the Reset Analytics Script.
Start the Appian engines. Wait for the CPU usage to stabilize.
Run the Status Script to ensure all the engines are okay.
Start the search server.
Start the application server.

For Appian version 17.2 and prior, follow the steps below.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Delete all files ending in .kdb in the Analytics Engine gateway directories (<APPIAN_HOME>/server/process/analytics/00XX/gw1).
Note: If you have additional gateway directories (gwX) with engine database files (pa*.kdb) in them, you need to delete those files as well for each analytics engine.

Example Unix commands:
```
cd <APPIAN_HOME>/server/process/analytics/00**/gw*
rm pa*.kdb
```
Example Windows commands:
```
cd <APPIAN_HOME>\server\process\analytics\00**\gw*
del pa*.kdb
```
In <APPIAN_HOME>/server/process/analytics, copy the file named pa.kdb into each engine/gateway directory (<APPIAN_HOME>/server/process/analytics/00XX/gwX) and rename each copy to pa1.kdb. Do not rename the original file.
Start the Appian engines. Wait for the CPU usage to stabilize.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start the search server.
Start the application server.

Affected Versions

This article applies to all versions of on-premise installations of Appian.

Last Reviewed: November 2017

Tags: administration, engines

KB-1157 How to reset the analytics engines for on-premise installations of Appian

Nick Vigilante — Tue, 28 Feb 2017 19:50:33 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 2/28/2017 7:50:33 PM

This article outlines the process to reset the Analytics Engines in on-premise installations of Appian.

NOTE: These steps should only be performed when advised to do so by Appian Technical Support.

Shut down Appian completely, including application server, search server, and the engines. Refer to Starting and Stopping Appian for more information.
Delete all files ending in .kdb in the Analytics Engine gateway directories (<APPIAN_HOME>/server/process/analytics/00XX/gw1).
Note: If you have additional gateway directories (gwX) with engine database files (pa*.kdb) in them, you need to delete those files as well for each analytics engine.

Example Unix commands:
```
cd <APPIAN_HOME>/server/process/analytics/00**/gw*
rm pa*.kdb
```
Example Windows commands:
```
cd <APPIAN_HOME>\server\process\analytics\00**\gw*
del pa*.kdb
```
In <APPIAN_HOME>/server/process/analytics, copy the file named pa.kdb into each engine/gateway directory (<APPIAN_HOME>/server/process/analytics/00XX/gwX) and rename each copy to pa1.kdb. Do not rename the original file.
Start the Appian engines. Wait for the CPU usage to stabilize.
Run checkengine.(bat|sh) to ensure all the engines have a status of OKAY.
Start the search server.
Start the application server.

Affected Versions

This article applies to all versions of on-premise installations of Appian.

Last Reviewed: February 2017

Tags: administration, engines