thanks, but jar files are not the issue.
The MQ adapter worked fine until our MQ admin decided to change the q manager’s name while the IS is down. So when the IS restarted, it is trying to connect to the q manager using the old name, hence mq connection error. the problem is IS kept on trying in a loop, hence I can’t get to the IS Admin screen.
My problem is to figure out where Webmethods stored this q manager name in the file system so I can manually change it, and restart the IS.
Thanks for trying.