-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of maggie2007
Sent: Thursday, October 18, 2007 11:34 AM
To: [email protected]
Subject: Remedy web service authentication: map SOAPHeader under the ROOT
element

Hi, I went through all the sessions about Remedy web service authentication,
still don't understand how to 
set up authentication for consuming external web service which requires
username, password, certificate serial number ( it uses WSE3.0 X509). 

I know how to consume that external web service in C# .Net web service
client, but didn't figure out in Remedy.

In Remedy Integrating document, it mentioned that
"When you use an external web service requires a SOAP header, BMC Remedy
Administrator will automatically make an element called SOAPHeader under the
ROOT element. You can map elements inside
the SOAPHeader just as you would regular elements"

question 1: how do I know that that external web service requires a SOAP
header?
                 I mean by the WSDL, can we tell? I know in C# .Net ws
client, I need to specify username/pwd/certificate serial number.

question 2: If the external web service requires a SOAP header, the Remedy
Administrator tool output mapping wizard will automatically populate
SOAPHeader under Root element? I didn't see the SOAPHeader element, so I
couldn't map the authentication info. Anybody can attached the picture if
you see that?

 
-- 
View this message in context:
http://www.nabble.com/Remedy-web-service-authentication%3A-map-SOAPHeader-un
der-the-ROOT-element-tf4637027.html#a13243226
Sent from the ARS (Action Request System) mailing list archive at
Nabble.com.

____________________________________________________________________________
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

<<attachment: SOAPHeader.gif>>

Reply via email to