k.exe file - What is it and what is its purpose?

In short it's something like an in-memory database that runs the entire application.  You need it for Appian to live.

Thanks for the input, Tim and David.

Next question I have is 'How do we identify which ones are obsolete and can be stopped from execution?" As I understand, we should ideally have only one instance of this executable file running at a time after server start.

Please correct in case my understanding is incorrect.

Thanks.

Hitesh

I think all engines are run on K, so I have a feeling every instance of K are all needed and you'll drop one or more engines if you turn any of them off.

If you're on a test environment, or if you don't have anything being used by enterprise on your prod environment yet, I suppose you could shut off K files and see what the effect is, provided you're actively monitoring engines and you're willing to accept the risk of adding more work to get it back up.

I think all engines are run on K, so I have a feeling every instance of K are all needed and you'll drop one or more engines if you turn any of them off.

If you're on a test environment, or if you don't have anything being used by enterprise on your prod environment yet, I suppose you could shut off K files and see what the effect is, provided you're actively monitoring engines and you're willing to accept the risk of adding more work to get it back up.