How can I communicate between web servers on the same machine?

[Gery D. Dorazio]

Gurus,

I have a server running Windows Server 2003 Web Edition running multiple web
sites on the same server. All the web sites on this server are owned by the
same company. The company does secure credit card processing through a
payment processing company gateway service.

The company that owns the web sites wants to have a single payment gateway
mechanism for all the web sites on the server. Instead of having each of the
web sites call the payment processing gateway separately, they would like to
send the request to a dedicated web site on the server which then handles
the requests to the payment processors gateway server.

This allows the company to reduce costs, one of which is the number of SSL
certificates installed for the secure payment processing...

Can you suggest ways for these web sites to talk to the "web site" that
talks to the payment gateway service OR comment on the following thoughts
that have crossed my mind?

1) Create a specific web site like http://paymentprocessing.mycompany.com
which only accepts authenticated secure web service calls from the other web
sites on the server and then this site talks to the payment processing
gateway.
2) Possibly create a windows service that talks to the payment processing
gateway directly and have the web sites talk to the windows service.
3) Write code that runs on the web servers that talks directly to the
application domain running the payment processing code that talks to the
payment processor gateway...I don't know if this is feasible or even a
reliable method and if so, how is it done? The payment processing code could
be an application that starts when the machine is booted up.

Thanks,
Gery


--
Gery D. Dorazio
Development Engineer

EnQue Corporation
1334 Queens Road
Charlotte, NC 28207
(704) 377-3327

 

[Scott Allen]

Hi Gery:

IMHO, #1 will face some hurdles if you need to maintain session state,
application cache, etc while sending the user to a different
application.

#2 and #3 are more feasible, and #3 might be the easiest. You can make
the payment processing application an ASP.NET web service and
communicate from the various other applications via web service calls,
which can be simple and reliable.

I don't see how number 2 and 3 would save any money on SSL certs
though. You'd need certs for each application if they are under
distinct domain names. Only #1 could really save money by hosting a
single application with SSL.

 

[Gery D. Dorazio]

Hi Scott,

Thanks for the insight on all three counts. You've given me a lot to think
about.

Looks like I need to do more investigative work for the SSL certificates
issue. I no longer use a web hosting company for my sites but now run my own
servers. However, when I was at a hosting company, they had a service that,
rather than purchase ones own SSL cert, we could use theirs. I never did for
branding reasons but I never really understood how it could be used for
multiple sites...eg "distinct domain names" as you indicate.

Thanks,
Gery

--
Gery D. Dorazio
Development Engineer

EnQue Corporation
1334 Queens Road
Charlotte, NC 28207
(704) 377-3327

 

[Scott Allen]

Hi Gery:

Well, I suppose it is technically possible to share an SSL cert as
some ISPs provide this. I always felt the practice underminded the
whole concept of the browser trusting the site to be exactly what the
site claims to be. Since all your sites and domains are owned by the
same company I guess there is some leeway, but I think (opinion) the
best practice is to acquire a cert for each.

 

[Suvra B]

Why don't you try gateway using papal or something like that. It will
ease all your head each about SSL.


Suvra B
http://www.M6.net
Always On :: Always Performing :: Always Hosting