I’m new to BigFix and soap but have been tasked to learn everything about both, so bear with me. We’re on bes 7.2
I’ve created a .hta with some basic code I found on these forums to begin testing soap requests.
I’m using the files; RelevanceLogic.js and soapclient.js and they are in the same folder as my .hta. I keep getting a ‘null’ response when the .hta is run. I don’t know if I need to modify these two scripts or if they should work as is.
I’ve tested with ‘soapUI’ and am able to send and receive a response back.
I’m looking for suggestions or any other documentation that might be out there.
I wish there was an error but null is the only thing that’s returned.
Is there a way to debug the script to see where it’s failing?
You can debug Javascript with the Firebug extension for Firefox. I’d also recommend the Web Developer toolbar. You would probably have to (temporarily) convert your .hta file to .html.
If you don’t mind me asking, where did you get RelevanceLogic.js and soapclient.js from?
I guess what i’m wondering is that all things being equal should I have to debug the two .js files? I was under the impression based on the vid anyway that they should work as is.
I am very new at this, am I just missing something here in my train of thought?
I was a little curious, because I didn’t think this Javascript would work, since I thought most browsers did not allow cross-domain AJAX requests. I tested the scripts, and it looks like that may in fact be your issue. Here’s the error I receive in the javascript console:
This seems to indicate to me that this type of request isn’t allowed in a standard web browser (and presumably an hta). Maybe someone at BigFix can confirm this.
Ok, that makes sense. So I would have to make the call from within the domain the web reports server was on? or… find work around or a different method…i.e. vbs
I’m hoping someone from BigFix will chime in to confirm this. Yes, you could still use vbs, php, perl, or just about anything else that send soap requests.
A good test might be to see if it will run if you put it on the same domain as the web reports server, as you suggested.
I’ll test it out next week and let ya know how it goes. I suspect it will work just fine. I did some reading on ajax and cross-domain requests, there really isn’t a viable secure method to use as a workaround.