Been a while since I've done anything with SOAP, but the way I remember it is it's just a POST operation with a XML payload at the end of the day. If you have configured the endpoint properly in the processor's URL property and set it to do a POST, the *flowfile content* should be where you put the SOAP request body. In the example of SO, it looked like you were using a dynamic property to store the soap:Envelope segment, and I don't think that's going to work. Let me know if you make any progress with the method I suggested.
Mike On Fri, Mar 23, 2018 at 5:55 PM, Code Novice <tuxfa...@gmail.com> wrote: > I've only just subscribed to the dev@nifi.apache.org mailing list and > today > was my first time even knowing that a thing like 'maling lists' existed. > Regardless, I'm posting my question in hopes to seek out how you eventually > managed to get your InvokeHTTP Processor to work with SOAP as I have not > yet > been able to do so. > > I posted my original question on this matter on Stackoverflow here > <https://stackoverflow.com/questions/49457764/nifi-how- > to-use-invokehttp-processor-with-soap> > . I also referenced this post as it is the only place I am seeing somebody > use the InvokeHTTP with SOAP. > > I'm using SOAPUI to verify that everything works and it does as I am > getting > the appropriate XML response back. However I am unable to accomplish this > in > NiFi. My guess is that I don't know what to call my dynamic properties. I > also don't fully understand what data I would add to the Value of my > dynamic > properties. > > <http://apache-nifi-developer-list.39713.n7.nabble.com/file/t939/SOAP.png> > > > > -- > Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/ >
