On 2011-05-25 11:14, Mike Wills wrote:
I realize this would probably be a prefect use of web services on the i. But
we would prefer to not punch a hole through the firewall from the internet
side (DMZ) to the intranet side if possible. Or can this be done securely
and avoid the possible problems with holes into our internal network?

Any thoughts?


I've done something similar with a java web service on the i, running in Tomcat. I haven't worked in .net much, but as I recall, .net apps can easily consume a web service. The web service, running on the i can then pass data to a back-end process via a data queue, command, or a direct program call, passing a delimited data stream. The request into the DMZ can also be an XML document containing a batch of transactions if you use XMLHTTP. The web service on the i can contain logic to validate the requester, the request content or both. A simple HTTP post works just fine too for single transactions. It's fairly secure to allow a server in the DMZ to communicate with the i. It has the advantage that there is direct hand-off; no file drops, no polling interval. Direct return of a result message is very possible. You could eliminate the i web service and have a 3 tiered solution if you can figure out how to use jtopen in .net. The .net web service could contain credentials to log in on the i. That's speculative though. I haven't done it.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.