Introduction
Windows Server System Reference Architecture (WSSRA) is an integrated set of service solutions based on architectural guidance for typical enterprise scenarios. This guide focuses on the design of a middleware service solution. The design was created using the guidance provided in the Reference Blueprints, specifically the Middleware Services Blueprint that outlined the options available for the delivery of middleware services and the technologies available to support them. This guide provides a detailed breakdown of the design choices and requirements for the provision of .NET Framework middleware services in the Centralized Data Center (CDC) and Satellite Branch Office (SBO) scenarios. These scenarios are outlined in the Introduction to Windows Server System Reference Architecture document and detailed in the Lab Implementation of Windows Server System Reference Architecture document. In the Microsoft context, middleware services design is comprised of three application architecture elements:
The process for creating each of these middleware services elements consists of the following design phases:
These phases are described in the Middleware Services Blueprint. During each of the phases, the chosen technology solution may be required to meet specific service-level design goals, such as availability, security, and scalability. How these design goals are incorporated may either be implicit in the logical or physical design or explained separately in their relevant sections later in this guide. On This Page
Who Should Read This GuideThis guide is written to meet the requirements of information technology (IT) professionals responsible for the design and deployment of middleware services in enterprises that are similar in scale and scope to the CDC or SBO scenarios. These professionals include consultants, system architects, and other IT professionals who are involved in the planning stages of application or infrastructure development across multiple projects. Knowledge PrerequisitesThe reader should have a practitioner-level understanding of applications infrastructure. In addition, the reader should have a good working knowledge of operating systems and server hardware along with the types of applications that run on them; these are described in the Application Infrastructure Architecture Blueprint. The reader should also be familiar with the basic concepts of the following technologies:
Finally, because middleware services depend on other WSSRA services, the reader is expected to have a working knowledge of the technologies that support the applications architecture. Business NeedThe CDC design provides the network and software infrastructure that allows .NET-connected applications to provide and consume services from within the CDC implementation as well as from other data centers. Applications running in the CDC environment are typically business-critical and often have a high degree of complexity due to a complex mix of services that exist around differing requirements for solution capabilities. Applications running in the CDC environment include a mixture of applications connecting through Web Services, .NET Remoting, and DCOM. The CDC implementation must support .NET applications that use .NET Remoting to communicate between components running on different machines in the same or different security zones. It must also support communication between COM+ components. In addition to providing connectivity and security for client applications connecting from external sources and data centers, the CDC environment also includes client applications that connect from within the CDC environment itself. The type of environment that an application needs for its execution (whether an application is Web-based, a smart client, or runs on some type of device) is determined by the specific requirements of that application. For applications running in the trusted CDC environment, the method that an application uses to communicate with distributed components is typically different from the method it would use if it were running outside the CDC environment. For the SBO scenario a different business need was identified, SBO offices vary in size and number of staff, and it is likely that providing dedicated local IT resources and services may be cost prohibitive. The SBO implementation provides VPN-based Internet connectivity to the centralized data center. Using .NET-connected applications, local staff can connect to centralized data resources using technologies such as smart client applications connecting to application servers in the corporate perimeter or Web services or .NET Remoting to connect to the back end network. Alternatively, local staff can use their browsers to connect using HTTP to ASP.NET applications running on corporate Web servers. ReferencesThe Middleware Services Blueprint provides a number of references to support the design of middleware services using the .NET Framework. Additional information can be found in the following chapters in the MSA Enterprise Data Center v1.5 Reference Architecture Guide:
These guides are available at the following URL: http://www.microsoft.com/resources/documentation/msa/edc/all/solution/en-us/rak/rag/default.mspx For further information on securing .NET, refer to the article “Securing ASP.NET Web Services” at the following URL: http://msdn.microsoft.com/netframework/technologyinfo/infrastructure/default.aspx For information on deploying the .NET Framework, refer to the .NET Deployment Guide at the following URL: http://msdn.microsoft.com/netframework/technologyinfo/infrastructure/deployment/default.aspx |
Download
Solution Accelerator Notifications Feedback
|
