I have set mustunderstand to 1 as it does when it sends it out, and have
been able to get responses that are valid from a WS.
"The external WSDL I was trying to consume was not expecting the SOAP header
that Remedy was compiling"
This is more of the problem. The envelope that Remedy sends out is not in
the format that is expected as it tends to either use namespaces that do not
exist. This in some cases can be overcome by tweaking the filters a wee
bit.. But in complex envelopes, its harder (maybe even not possible) to
tweak the envelope at the AR level that the filter tries to generate...
So far I have had 50% success in tweaking filters to make non functional
filters functional.. Literally 50% success in fact..
-----Original Message-----
From: Tommy Morris
Sent: Thursday, June 28, 2012 10:21 AM Newsgroups:
public.remedy.arsystem.general
To: [email protected]
Subject: Re: Web Service questions
If you receive an ERROR 9130, this is the reason:
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.
The external WSDL I was trying to consume was not expecting the SOAP header
that Remedy was compiling. I had to contact that external app vendor and ask
them to add an inclusion to their authentication so that the app can process
the request. Otherwise on the external system I will continue to receive
Authentication Errors.
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Sean O'Sullivan
Sent: Thursday, June 28, 2012 8:55 AM
To: [email protected]
Subject: Web Service questions
Good Morning Listers,
We're building an integration between our in-house Remedy system and an
externally hosted SAAS system.
The integration is via Web Services. We're new at this and its been an
adventure.
Right now we're looking to consume a Web Service presented by the external
system.
The code that calls the external Web Service is a filter that does a set
field.
I'm trying to understand if the web service call is going out of the
mid-tier box or going out of the main application server so that I can open
the correct holes in the firewall. I've read lots of documentation and I've
seen references to it both ways.
Also, How common is it for the WSDL from the other system to need
modification before it works with Remedy?
Thanks for your help.
Sean O'Sullivan
Prudential Financial
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
