|The commands in this guide are strongly biased towards UNIX type systems.|
After applying some changes to the KIM server like:
- modifications on the ontology
- modifications on the knowledge base
- modifications on the parameters of the IE resources
- other changes that affect the functionality of the server
We recommend you to clear the already generated indexes and all kinds of cache, as well as the logs, in order to be able to more easily diagnose if problems arise.
Stop those applications in order to clear the caches.
For the Jetty based KIM 3.6 stopping only KIM is enough.
Basically all the cache KIM generates lives in KIM_HOME>/context/default/populated folder. So in order to remove the cache, we should Remove the <KIM_HOME>/context/default/populated folder
Remove the content of <KIM_HOME>/log folder
Remove the deployed web archive
A recommended, although not mandatory, step would be to clear tomcat's generated cache