Operating Environment and Scalability

Operating Environment and Scalability

In developing any commercial system, it is essential to develop a scaled roadmap that allows validation of the service architecture in a lab or prototype phase, with a simple way to scale up to an initial commercial presence. Once this model is running, you can gradually meet increasing service loads, by separating functionality across computers, almost without limit. The following two-server configuration is quite capable of prototyping all of the functionality described here. A commercial deployment would separate functionality as described in a later chapter.

Hardware Installed Software
Gateway Server
  • Single-Processor 1+ GHz
  • 500 MB RAM
  • 40 GB mirrored IDE (RAID 0) hard drive
Windows 2000 with latest service pack

Internet Security and Acceleration (ISA) Server

Small Space Server
  • Dual-Processor 2 GHz
  • 4 GB RAM
  • 100 GB mirrored IDE (RAID 0) hard drive
Windows 2000 Server SP2

Internet Information Systems (IIS) 5.0

MSMQ

SQL Server 2000

Exchange Server 2000 (if SMTP supported)


A full capability configuration can be built from the following components:

Configuration Installed Software
Gateway Server Array (1-16 servers)
  • Single-Processor 500 MHz
  • 500 MB RAM
  • 40 GB RAID 0 SCSI disk
Windows 2000 Server SP2

ISA Server – Enterprise Edition

Host Integration Server (opt)

Transport Conversion Server Cluster (2-16 servers)
  • Dual-Processor 2 GHz
  • 4 GB RAM
  • 100 GB RAID 5 SCSI array
Windows 2000 Advanced Server SP2

.NET Framework

IIS 5.0

MSMQ

Exchange Server 2000

Accounting Server (2-4 servers)
  • Dual-Processor 2 GHz
  • 4 GB RAM
  • 100 GB RAID 5 SCSI array
Windows 2000 Advanced Server

SQL Server 2000

.NET Framework

Commerce Server 2000 (opt)

Core Navigation Server (2-16 servers)
  • Quad-Processor 700 MHz
  • 1 gig RAM
  • 200 GB RAID 5 SCSI array
Windows 2000 with latest service pack

IIS 5.0

.NET Framework

Host Integration Server (opt)


General Considerations

Host Integration Server can be included if it is necessary to establish client-server connectivity with a mainframe system at the Gateway or for content integration at the Core Navigation server. These options are discussed in more detail in the next chapter.

Previous  Next


Microsoft Corporation - Microsoft. Net Server Solutions for the Enterprise
Microsoft .NET Server Solutions for the Enterprise
ISBN: 0735615691
EAN: 2147483647
Year: 2002
Pages: 483

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net