It is very easy to delete unused WebServices if you use 7.1: **7.1 Leading Edge and NEWER** With 7.1 you can steer on new deployments whether old configurations should be removed. See the `configuration.cleanup` options here: options - in the engine.guide : https://developer.axonivy.com/doc/7.1.latest/EngineGuideHtml/administration.html#administration-deployment-directory-options - or for maven users: http://axonivy.github.io/project-build-plugin/release/7.1/deploy-to-engine-mojo.html#deployConfigCleanup **On 7.0 LTS and older** You can do it by hand in the database by removing the entries in `IWA_WebService` respectively `IWA_GlobalVariable`. Ensure that you have a backup in case you delete too many entries.

It is very easy to delete unused WebServices if you use 7.1: **7.1 Leading Edge and NEWER** With 7.1 you can steer on new deployments whether old configurations should be removed. See the `configuration.cleanup` options here: https://developer.axonivy.com/doc/7.1.latest/EngineGuideHtml/administration.html#administration-deployment-directory-options or for maven users: http://axonivy.github.io/project-build-plugin/release/7.1/deploy-to-engine-mojo.html#deployConfigCleanup **On 7.0 LTS and older** You can do it by hand in the database by removing the entries in `IWA_WebService` respectively `IWA_GlobalVariable`. Ensure that you have a backup in case you delete too many entries.

It is very easy to delete unused WebServices if you use 7.1: **7.1 Leading Edge and NEWER** With 7.1 you can steer on new deployments whether old configurations should be removed. See the `configuration.cleanup` options here: https://developer.axonivy.com/doc/7.1.latest/EngineGuideHtml/administration.html#administration-deployment-directory-options **On 7.0 LTS and older** You can do it by hand in the database by removing the entries in `IWA_WebService` respectively `IWA_GlobalVariable`. Ensure that you have a backup in case you delete too many entries.