Issues with SOAP - tried tSOAP, tWebservice, tWebserviceInput

[alawton]

I am working with a SOAP call to insert data to another service. I received a WSDL from the service and tried advancing with tWebservice component. The first difficulty with this approach is the authentication approach. I would map values to the header using variables. I am unable to determine I would make this happen. An excerpt of the XML below ...

<soapenv:Header>
 <sececurity>
  <UsernameToken>
   <Username> </Username>
   <Password> </Password>
  </UsernameToken>
 </sececurity>

</soapenv:Header>
<soapenv:Body>

As a second shot, I manually created items body using tSOAP and mapping fields by breaking text and inserting a variable created from tFlowToIterate. I was able to get this working, but it is clumsy and more challenging to maintain. What is the most maintainable approach to make SOAP calls while preserving the ability to edit login credentials in the SOAP header?

[fdenis]

first you have to define the needed authentification.
Kerberos, login - password, nothing….

to build your message you can generate xml into soap message box using java syntax:
" is used to surround string.
\" to replace " into this string.

good luck

[alawton · Accepted solution]

I fixed my own problem by switching to tESBConsumer with a preceding tXMLMap to build the XML doc. Authentication is handled in the tESBConsumer component and it is more sustainable. Thanks.