My guess is that you need to deal with their web service? "a SOAP solution which will send claim information out to a site"
They will post back to your web service as well? "and return responses."
You have a Web presence already. "We have a separate web server, on a linux box, that can access the MS machine."
Just put up a web service on that web server to push to them as needed as well as wrote the reply you get back from them. Sounded easy right? Not necessarily the reality in the end. Basically you are going to send out an XML message for them to process. Expect to have a security layer or two as protection for you and them that need to be confirmed before you pass that XML message of the claim.
When they respond back you have to have the security set as well and then receive the xml from them, parse it and do what needs to be done depending on your logic.
On Mon, Mar 21, 2016 at 8:43 AM, Vince Teachout vince@recordables.com wrote:
After never needing it for 20 years, I now need to develop and implement a SOAP solution which will send claim information out to a site, and return responses.
I'm RTFM-ing now, but one thing that concerns me, is that if I understand this correctly, I need a web server to get responses back. Is this correct?
We have a MS database server where the data, and this application would live. We have a separate web server, on a linux box, that can access the MS machine.
If I write this,
- can I send this request out from the DB Server, and get a response back?
- Send something to the web server, have the server send and receive the
request and send it back to the db server? 3) run a very limited web server which would only listen for the client's ip range, in order to send/get requests?
I'm not looking for details, I just need an idea of the general direction I need to head. If I could do 1) that would be awesome, but if I'm understanding what I'm reading so far, I'll need to do 2 or 3.
Would appreciate clues. Thank you!
--
Vince Teachout Senior Analyst Recordables, Inc. 312-288-8566
-----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v2
mQENBE2o8OkBCADeegwZu8ZeYxoAwuTLcl1rEXT2fovoCSSHjyAUBrcezJDttLh7 pMCYVdwvwPesnaA4M05gv1VPhlgg+tjkyBxiqhZja7URMNasDvmzIyzFrh6Eedpf Vn8zf5SEzpi6PQuI4KKEvexL7eTilPtnB+lJmaVVDxDI1rUk6jsHAJ1FDAZDnRab PZfWt6woLhzIv3obq07dp1fnRr9CPG5OVjUfzUwLYcCy6eUw6555vnwnHeZG+W6c mAZEV0082sk00NcSz1FoE8hA+ULZjkRiIBhU7viLJ12Tpw5VcsCM6UjooOds7OhQ 3wYDYwBPy7WC9eH/3A3RGuZ8pfc0AT7e//FjABEBAAG0NVZpbmNlIFRlYWNob3V0 ICgyMDExMDQxNS1mb3Rzb3RhKSA8dmluY2VAY2FyYWNhbC5uZXQ+iQE4BBMBAgAi BQJNqPDpAhsPBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRCpaAY+vVSIgxjt B/0UPUl6ejbu0w1zhCfAVjqckKZoLbFqN7GUjPhKRpb3Fof5chzbI8/RYjgSiJF2 dXjKOH4xyXTDQ1M7zucjLC+3GNLb1y9N803z5FMA6pTtj3ySYPhY+r4yl6TiZDs8 8Re+hRA3e06gTy1N4oF24LgDckf78DPWMeqqKjowT623Ttvs1QBTCj3OIvbW2X+i XJWalOaKFCSUPaZX6zBaUDBT3fZ0sLnAUtDF0m7i1R7HKVI0RHyHWYlQURvV0glQ 1JSLGEsiHhWyetfbnz0hk4dZ/25S0WU+Mwq4CdEAluj6EdPCG4DurlB7TQogzZJ+ 8sqPYq1pQ5WTnsYQU5yIUHUm =LHkH -----END PGP PUBLIC KEY BLOCK-----
[excessive quoting removed by server]