226 WebSphere and .Net Interoperability Using Web Services
All other non-functional requirements such as load balancing, fail-over
capabilities and server clustering can be added using external equipment and
operating system built-in capabilities. The Microsoft paper “Application
Architecture for .NET: Designing Applications and Services” includes a large
number of different deployment patterns for Web services; it can be found at:
Detailed information about security in a Microsoft environment can be found in
the Microsoft white paper Securing ASP.NET Web Services,
found at:
10.4 Summary
We have described how a Web service is deployed on the WebSphere and
Microsoft .Net platforms and summarized the runtime architecture guidance from
Microsoft and IBM. The architecture builds on the infrastructure used for Web
sites today.
The guidance on deploying Web services from Microsoft makes use of
capabilities in the Windows platform that will be familiar to Windows System
Programmers to secure the new services.
The IBM approach focuses on managing Internet access to Web services by
introducing a new cross-platform component, the Web Services Gateway. The
Web Services Gateway provides a single point of control for Web services across
multiple platforms that can be managed by a Systems Programmer with
WebSphere skills.
Both approaches share the same objective: exposing as little as possible of the
IT infrastructure to outside attention.

Get WebSphere and .Net Interoperability Using Web Services now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.