AXIS 1.4 which is bundled with Remedy AR since 7.5 onwards sets the mustunderstand attribute to 1 if it finds SOAP header information in the Client request to the Webservice (AR or External) for example WS Security information like username and password. When SOAP header information is sent out, the mustunderstand attribute is set to 1 which otherwise is 0; Because this attribute is set to 1, the Webservice is not able to understand it and thus the error.
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Wendy Lynne Sent: Tuesday, July 03, 2012 11:18 AM To: arslist@ARSLIST.ORG Subject: Netcool WSDL Integration with Remedy 7.6.01 ** I am working on an integration with Netcool through Web Services. The integration was working fine until the Netcool server, id and password were changed. This integration was built on my dev box and before the changes, the build worked fine for both the creation of tickets and the update for resolve/close. The Remedy WSDL was updated with the new Netcool server, id and password. Netcool can create tickets and receive incident numbers from Remedy. I made the changes to the Netcool WSDL and rebuilt the filters that Remedy used to send other data back to Netcool when an incident is resolved/closed. Through some troubleshooting and testing, it appears that Remedy does not like the format of the Netcool WSDL. The WSDL works fine through SoapUI. Has anyone experienced this and can share a possible solution. _attend WWRUG12 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
