System Requirements

Community Server runs exclusively on the Microsoft Web application platform. This enables Community Server to focus on being the best-of-breed solution rather than being limited by common denominators across multiple vendors’ web application platforms.

Community Server has the following requirements:

Web Application Server(s)

• Recommended: Microsoft Windows Server 2003 R2
• Microsoft Windows Server 2000
• Development only: Microsoft Windows XP
• Microsoft Internet Information Services (IIS)
• Microsoft .NET 2.0

Database Server(s)

• Recommended: Microsoft SQL Server 2005 64-bit
  • Windows Server 2003 R2 64-bit
• Microsoft SQL Server 2000
• Development only: Microsoft SQL Desktop Engine (MSDE)

Recommended Configuration

Professional Edition

For the Professional Edition of Community Server, Telligent recommends the following configuration:

• Clustered Web Application Servers – 2 or more clustered servers for uninterrupted request servicing.
• Database Server Configuration – minimum requirements: 32-bit dual-processor CPUs with 4 GB of memory. (64-bit strongly recommended)
• Web Application Server Configuration – minimum requirements: 32-bit dual-processor CPUs or single Multi-core CPU with 1 GB of memory.

Please see the Enterprise Recommended Configuration below for additional options.

Enterprise Edition

For optimal performance and reliability of the Enterprise Edition of Community Server, Telligent recommends the following configuration:

• Clustered Web Application Servers – 3 or more clustered servers for uninterrupted request servicing.
• Dedicated Enterprise Search Server – Moves search off the database and onto a dedicated search server which is queried via web services APIs.
• Dedicated Enterprise Job Server – Moves background jobs to a dedicated server; can optionally reside on the dedicated Enterprise Search Server.
• Web Application Server Configuration – 32-bit Multi-core CPU(s) or Multiple CPUs, 4 GB of memory.
• Database Server Configuration – 64-bit dual-processor, hyper-threaded CPUs, 2-4 GB of memory, 15K RPM spindles with separate controllers for system, data, and log files.

Backing Up Data

All data within Community Server resides within the database. For Enterprise customers Telligent recommends continuous incremental backups throughout the day and full backups daily.

High Availability Considerations

In high availability environments with multiple Web nodes, some files need to be synchronized to ensure a consistent user experience. Telligent makes no official recommendation on how to accomplish this. You should consult with your system administrator or IT department.

Telligent employs Microsoft Windows® Active Directory and implements DFS / FRS to synchronize files among Web nodes in many cases. You should make sure you thoroughly understand the cost and security ramifications of such an implementation.

Synchronization can also be accomplished by using external storage strategies, 3^rd party replication / synchronization software, UNC sharing, or custom scripts. You should test your strategy thoroughly to ensure capabilities under load and compatibility.

Depending on your implementation and availability requirements, Telligent also suggests considering the following:

• Running your production SQL server in an Active Passive Cluster
• Clustering your load balancers / Firewalls

Hardware Load-Balancing

Telligent recommends hardware, not software, load-balancing requirements. Load balancers come from a variety of manufacturers. When choosing your load balancing hardware, consider scalability and clustering capabilities.