How to purge/clean-up a Dev/Test environment? We have had an on-going

Brandon over 9 years ago

How to purge/clean-up a Dev/Test environment?

We have had an on-going issue in our development environment that seems to have originated when it was not shutdown properly and KDBs got corrupt. We experience issues where incorrect sub processes are sometimes triggered, or the system says that a process model has not been found. When we try the same request again it works.

What we would like to do is purge all data in the environment, apart from the process models and user accounts. Can you please advise how we should go about doing this? We have tried deleting every single process through the Appian UI, but the problem remains. We also tried rebuilding analytics from scratch but that also doesn't help. Checkengine shows everything as normal.

thanks a lot.

Discussion posts and replies are publicly visible

Parents

0 Eduardo Fuentes
Appian Employee
over 9 years ago

1. If the error you were encountering was: "Process Model not Found on Execution server for sub process invocation" the solution was to individually launch one instance of the problematic model in standalone mode instead of as a sub-process to force the propagation between DESIGN and EXEC. See my comment at forum.appian.com/.../e-152404

2. You should not copy the pe*.kdb file from EXECX to EXECY. That puts the system in an inconsistent state. Each EXEC has an ID registered inside and knows whether it is 00, 01 or 02. If you copy the pe*.kdb from EXEC00 to process/exec/01/gw1 then you're duplicating an engine causing inconsistency because Appian now has two engines with the same ID and one is the wrong location.

Instead what you can do is:

1. Stop the environment
2. Blank out analytics
3. Blank all the execs, basically their gw1 directory (since you need to purge and fix the inconsistency)
4. Start the environment
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Eduardo Fuentes
Appian Employee
over 9 years ago

1. If the error you were encountering was: "Process Model not Found on Execution server for sub process invocation" the solution was to individually launch one instance of the problematic model in standalone mode instead of as a sub-process to force the propagation between DESIGN and EXEC. See my comment at forum.appian.com/.../e-152404

2. You should not copy the pe*.kdb file from EXECX to EXECY. That puts the system in an inconsistent state. Each EXEC has an ID registered inside and knows whether it is 00, 01 or 02. If you copy the pe*.kdb from EXEC00 to process/exec/01/gw1 then you're duplicating an engine causing inconsistency because Appian now has two engines with the same ID and one is the wrong location.

Instead what you can do is:

1. Stop the environment
2. Blank out analytics
3. Blank all the execs, basically their gw1 directory (since you need to purge and fix the inconsistency)
4. Start the environment
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data