Copyright 2001-2011 Riversand Technologies, Inc.
MDMCenter
Hardware
Specification
2011
This document provides the recommended specifications for the hardware required to run MDMCenter on different environments. It also provides a list of prerequisite software that needs to be installed on the servers. The recommended specifications provided here are estimates only based on the assumptions listed in the Introduction.
2
Technologies, Inc and owned by Riversand Technologies, Inc.
TRADEMARKS
Riversand, the Riversand logo, and Riversand ProductCenter are U.S. trademarks or registered trademarks of Riversand Technologies, Inc. Other brands and product names mentioned in this guide are trademarks or registered trademarks of their respective owners and hereby acknowledged.
DISCLAIMER
NO WARRANTY. The technical documentation is being delivered to you AS-IS, and Riversand Technologies, Inc makes no warranty as to its accuracy or use. Any use of the technical documentation or the information contained therein is at the risk of the user. Documentation may include technical or other inaccuracies or typographical errors. Riversand Technologies, Inc reserves the right to make changes without prior notice.
No part of this publication may be copied without the express written permission of Riversand Technologies Inc., 9800 Richmond Ave, Suite #140, Houston, TX-77042 USA.
COMPANY INFORMATION
3
Contents
Introduction ... 4 Purpose ... 4 Document Scope ... 4 Assumptions ... 4Infrastructure Design and Components ... 5
Riversand MDM Infrastructure Conceptual Design ... 5
Riversand MDMCenter Production Logical Design ... 6
Pre-Production Environment: ... 7
Development/QA Environment: ... 8
Server Count ... 9
4
Introduction
Purpose
The purpose of this document is to provide a logical infrastructure design for Riversand MDM
Implementation. This document includes information related to the MDM infrastructure and its
components.
Document Scope
This is the Infrastructure logical Design document for Riversand MDM project. This document
will describe the high level design of all applicable infrastructure platform services utilized by
the Riversand MDM solution.
Assumptions
Product: Est. 500K products, 10M attribute records
Users: Est. 25 concurrent users (100 Named Users)
Avg. Content Length per request = 5 kb
Avg. requests per user per second = 10
Total bandwidth per user per second = 50 kb
5
Riversand Architecture
Infrastructure Design and Components
Riversand MDM Infrastructure Conceptual Design
Riversand MDM Production environment includes Riversand Web Server, Database Server,
Batch Server/Job Service server and existing Internal AD. All Riversand MDM roles will be setup
for high availability in production environment.
SAN
Clustered Database Server Load Balanced
Application Servers
Load Balanced Web Servers Users
6
Web and Application servers could be physical for both production and Pre-production
environments. Pre-Production environment will also be used as Quality Assurance and
Performance Testing environment. In production there will be approximately 25 concurrent
Web users.
TCP AD S ync H TTP Ex te rn al Se rv ic es Internet DB Server Web Server Web Server TCP TC P P o rt 8 0 8 1 P o rt 3 3 3 3 Clients TC P P o rt 8 0 8 1 P o rt 3 3 3 3 Load Balancer HTTP HTTP TCP DB ServerCPU: 2X 3.0GHz Quad CPU RAM: 16GB RAM
HDD: 200GB SAN (Grow On-Demand) OS: Windows 2008 R2
RAID: 10 Failover : Optional
App Server
CPU: 2X 3.0GHz Quad CPU RAM: 8GB RAM
HDD: 50GB (Grow On-Demand) OS: Windows 2008 R2 RAID: 10 Load Balance: None
Web Server
CPU: 2X 3.0GHz Quad CPU RAM: 4GB RAM
HDD: 50GB (Grow On-Demand) OS: Windows 2008 R2 RAID: 10
Software: .NET 3.5/IIS 7.0/Ajax
Hardware Load Balancer with Sticky Sessions
Active Directory
App Server
Data Volume Estimation
Products – 500K Items with avg. 20 attributes each Users: 25 Concurrent users and 100 total users.
Specification
DB Server
Application Server
Web Server
CPU 4 Dual Core/2 Quad Core 3.0 GHz 4 Dual Core/2 Quad Core 3.0 GHz 4 Dual Core/2 Quad Core 3.0 GHz (2 Servers)
RAM
16 GB 8 GB 4 GB
Hard drive
7
Pre-Production Environment:
Pre-Production environment will completely mimic production environment to facilitate similar
SLA’s available in the Pre-Production environment. The Pre-Production environment will also
be used as Quality Assurance/Performance Testing environment.
TCP AD Syn c H TTP Ex te rn al Se rv ic es Internet DB Server Web Server Web Server TCP TC P P o rt 8 0 8 1 P o rt 3 3 3 3 Clients TC P P o rt 8 0 8 1 P o rt 3 3 3 3 Load Balancer HTTP HTTP TCP DB Server
CPU: 2X 3.0GHz Quad CPU RAM: 16GB RAM
HDD: 200GB SAN (Grow On-Demand) OS: Windows 2008 R2
RAID: 10 Failover : Optional
App Server
CPU: 2X 3.0GHz Quad CPU RAM: 8GB RAM
HDD: 50GB (Grow On-Demand) OS: Windows 2008 R2 RAID: 10 Load Balance: None
Web Server
CPU: 2X 3.0GHz Quad CPU RAM: 4GB RAM
HDD: 50GB (Grow On-Demand) OS: Windows 2008 R2 RAID: 10
Software: .NET 3.5/IIS 7.0/Ajax
Hardware Load Balancer with Sticky Sessions
Active Directory
App Server
Data Volume Estimation
Products – 500K Items with avg. 20 attributes each Users: 25 Concurrent users and 100 total users.
Specification
DB Server
Application Server
Web Server
CPU 2 Quad Core Intel 3.0 GHz or better
2 Quad Core Intel 3.0 GHz or better
1 Quad Core Intel 3.0 GHz or better (2 Servers) RAM
16 GB 8 GB 4 GB
Hard drive
8
Development Environment:
The Development environment will provide a physical location to deploy and test: Builds, code,
patches and configuration changes without disturbing or altering the Production or
Pre-Production environments. It is not necessary for the performance of this environment to be
designed for performance and scalability.
Database Server 2 Quad Core 3.0GHz 8 GB RAM 200 GB HD 2 Quad Core 3.0GHz 4 GB RAM 100 GB HD
Web and Application Server
Specification
DB Server
Web Server and
App Server
CPU 2 Quad Core Intel 3.0 GHz or better (1 Server) 1 Quad Core Intel 3.0 GHz or better (1 Server)
RAM 8 GB 4 GB
9
Server Count
Here is the breakdown on number of servers for Production, Pre-Production and Development
in the Riversand MDM environment.
Roles
Environment
Server
Count
Load Balanced
/ Clustered
Virtual/Physical
Riversand MDM Web Server Production 2 Load Balanced Virtual
Riversand MDM APP Server Production 1 None Virtual
SQL Database Server for MDM (Clustering could be Optional upgrade)
Production 1 Optional Physical
Riversand MDM Web Server Pre-Production 2 Load Balanced Virtual
Riversand MDM Web Server Pre-Production 1 None Virtual
SQL Database Server for MDM Pre-Production 1 Optional Physical
Development and Test Server (Web, App)
Development 1 Virtual
SQL Database Server for MDM Development 1 Virtual
Total New Servers
10
10
Hardware Configuration
Here is the hardware configuration for each Riversand MDM server role in the Production and
Pre-Production environment.
Server Role & Notes Qty Virtual / Physical Hardware Description
Base Software & Comments Web Server (Prod,
Pre-Prod)
4 2 x Quad Core Intel Processors (or better) with 4 GB RAM and at least 1 x 50GB 15K RPM drives
Windows Server 2008 R2 R2 Standard 64 bit
IIS 7.0
App Server(Prod, Pre-Prod)
2 2 x Quad Core Processors (or better) with 8 GB RAM and at least 50GB 15K RPM drive
Windows Server 2008 R2 R2 Standard 64 bit IIS 7.0 SQL cluster for hosting MDM, databases (Prod, Pre-Prod)
2 2 x Quad Core Processors (or better) with at least 8 GB RAM and at least 200 GB or SAN space.
Windows Server 2008 R2 Enterprise 64 bit SQL Server 2008 Standard 64bit Part of Core Infrastructure shared service
N/A SAN (All DB's and Log files will be on their own LUN's configured to use minimum of RAID 1+0 or RAID 10+1 for DB and RAID 1+0 or RAID 1 for Log)
Total SAN - Approx 200GB to start and grow as needed
Web and App Server (Dev.)
1 2 x Quad Core Processors with 4 GB RAM and at least 100GB 15K RPM drive. Windows Server 2008 R2 R2 Standard 64 bit IIS 7.0 SQL Server MDM DB Server (Dev.)
1 2 x Quad Core Processors with 4 GB RAM and at least 200 GB 15K RPM drive.
Windows Server 2008 R2 Enterprise 64 bit
SQL Server 2008 Standard 64bit
