Thank you, poj. That introduces some namespace pieces I wasn't sure how to work with. However, replacing proxy with the API endpoint, I get this in response:
<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http:
+//schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/20
+01/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><
+soap:Body><soap:Fault><faultcode>soap:Client</faultcode><faultstring>
+Server did not recognize the value of HTTP Header SOAPAction: http://
+tempuri.org/AWEService/API/WASAPI#RunLocator.</faultstring><detail />
+</soap:Fault></soap:Body></soap:Envelope>
That is using the soap:address location from the wsdl file, as the proxy. Running it with loopback of course just spits the envelope back out. On the bright side, the envelope looks better now:
<soapenv:Envelope
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:was="http://tempuri.org/AWEService/API/WASAPI"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<was:RunLocator>
<was:userIdentification>
<WAS_userName>WS_Decom</WAS_userName>
<WAS_password>PASSWORD</WAS_password>
</was:userIdentification>
<was:locatorSearchFieldsIdentification>
<DEVICE_NAME>SERVER</DEVICE_NAME>
</was:locatorSearchFieldsIdentification>
</was:RunLocator>
</soapenv:Body>
</soapenv:Envelope>
Only issue I'm seeing with the envelope anymore is no prefix assigned to the lowest children, which will cause problems. I've corrected that issue manually, and I'm still left with the HTTP header faultstring.