Good morning, I am part of a team evaluating options for web services. We are looking for a way to provide a SOAP style front end for an existing transaction processor (TP). I am trying to find out what server options we have.
This project is an attempt to provide a standardized front end to replace several custom interfaces. The service definition will only be provided to third party application developers with a need to post transactions to our servers. Those will be web servers, POS servers and other application servers. The service will only be available to a few selected clients at each location. All connections must be secure, and client authentication is more important than server authentication. In addition, each client will only be able to use a specific subset of functions available on the TP. So there must be a way to tell the server which client sent each transaction. This must run on a Microsoft Windows server, and the interface to the TP is through DCOM objects. Is Axis2, in its current state, likely to be able to satisfy these basic requirements? We did look at Axis, which looked like it would work. But it does not support the client authentication we need. How much support overhead will there be to maintain 800 or so servers scattered all over North America? What is the quickest path to building a test server to evaluate this option? Thank you, Bob McConnell Principal Communications Programmer The CBORD Group, Inc. 61 Brown Road Ithaca NY, 14850 Phone 607 257-2410 FAX 607 257-1902 Email [EMAIL PROTECTED] Web www.cbord.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
