Upgraded WebServices Agent to 3.2 keeps using old SOAP Adapter directory

Discussion created by lerch on Mar 6, 2017

That's a weird one which is a good reason for sharing...

After upgrading several WebServices Agent to 3.2 we had only one that was not working. Research showed that it keep looking for itsWS_*.jar-files in the old directory "soapAdapters" instead as specified explicitely in the AgentDefinition in the new Standard Directory "soapJars".

This behaviour could only be changed by deleting the WebServices Agent host from the Automic-DB and recreating it.