topic Re: Using SOAP with default proxy in ArcGIS Web AppBuilder Questions

Using SOAP with default proxy

FrancisGagne1 — Wed, 21 Feb 2018 21:34:35 GMT

I'm trying to POST a SOAP request on a service not under my control.

Since it's cross domain, I need to use a proxy.

I am only using Postman for now.

When I call the service directly, the response is good. But when I add https://myserver:3344/proxy.js? before my service url in postman. The service return me "Server was unable to process request. ---> Root element is missing." meaning that my xml I sent is not good anymore.

Can I have some help with SOAP request using the default proxy coming with WebApp Builder?

Is it supported?

Thanks.

Re: Using SOAP with default proxy

RobertScheitlin__GISP — Wed, 21 Feb 2018 21:48:32 GMT

Francis,

I have never seen anyone (including myself) able to get a SOAP request through the JS API.

Re: Using SOAP with default proxy

FrancisGagne1 — Thu, 22 Feb 2018 15:05:34 GMT

You mean in WAB?

Because I have another application that uses the 3.16 JS API and it works just fine.

Re: Using SOAP with default proxy

RobertScheitlin__GISP — Thu, 22 Feb 2018 15:26:54 GMT

Francis,

Well if you were able to do it using the JS API then you should be able to do it using WAB. Can you share your code for how you did a SOAP call successfully?

Re: Using SOAP with default proxy

FrancisGagne1 — Thu, 22 Feb 2018 21:42:54 GMT

Pretty straightforward I guess:

var xhr = new XMLHttpRequest();
xhr.open('POST',esri.config.defaults.io.proxyUrl + '?' + this.somumWebURL,true);
var soapRequest = (
'<?xml version="1.0" encoding="utf-8"?>' +
'<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"' +
' xmlns:xsd="http://www.w3.org/2001/XMLSchema"' +
' xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">' +
'<soap:Body>' +
.....................
'</soap:Body>' +
'</soap:Envelope>'
);
xhr.onreadystatechange = dojo.hitch(this,function() {
if (xhr.readyState == 4 && xhr.status == 200) {
this.loadSOAPResponse(xhr.responseXML);
} else {
this.setErrorMessage(xhr.status);
}
});
xhr.setRequestHeader('Content-Type', 'text/xml; charset=utf8');
xhr.send(soapRequest);

The problem really is the proxy.js included with WAB.

I'm currently trying to find how it process my xml. I'll return with my findings.

Re: Using SOAP with default proxy

RobertScheitlin__GISP — Fri, 23 Feb 2018 01:19:42 GMT

Francis,

OK, I thought you meant you were using esriRequest on a SOAP web service.

Re: Using SOAP with default proxy

CCWeedcontrol — Fri, 23 Feb 2018 20:06:30 GMT

Francis are you trying to access a CAMA system?

Re: Using SOAP with default proxy

FrancisGagne1 — Fri, 23 Feb 2018 20:40:22 GMT

It's a system that automates sms and calls in a city.

Re: Using SOAP with default proxy

CCWeedcontrol — Fri, 23 Feb 2018 21:32:18 GMT

I see, I trying to look into accessing out CAMA system from a WAB application and i am not sure how to do i thought maybe you were trying to do that.

Re: Using SOAP with default proxy

RobertScheitlin__GISP — Fri, 23 Feb 2018 21:38:20 GMT

CC,

I access CAMA Data but I developed a RESTfull web service to do that, since SOAP is difficult to consume in JS.

Re: Using SOAP with default proxy

CCWeedcontrol — Mon, 26 Feb 2018 17:54:39 GMT

Robert i have some questions if you don't mind.

What data are you retrieving from the CAMA system, what are you doing with it?

How exactly are you doing it?

Re: Using SOAP with default proxy

RobertScheitlin__GISP — Mon, 26 Feb 2018 18:12:40 GMT

What data: All required parcel and improvement info for the selected parcel

What I do with it: Generate JS/HTML custom reports

How Exactly: Using esriRequest to my custom .Net web service that returns the CAMA data based a parcel number query.

Re: Using SOAP with default proxy

FrancisGagne1 — Tue, 27 Feb 2018 16:41:16 GMT

Instead of using the proxy in WAB to handle the cross domain problem, I passed in a service that handle CORS and all is fine now: https://cors-anywhere.herokuapp.com/

I'll setup a cors-anywhere on my client's server but at least I know that works with this one.