Large Environment

This topic is only applicable to on-premises installations.

 A large environment is suitable for organizations with the following complexity factors:

  • Up to 750 concurrent users
  • Fewer than 750,000 content records
  • 50,000 or fewer new content records added per year
  • Up to nine significant data feeds per day
  • Up to 20 applications with complex Advanced Workflow processes enabled

See Archer Qualified and Supported Environments on the Archer Community, for the supported and qualified software and environments, browsers and tools. 

On this page

Recommended configuration

For a large environment, it is recommended that you set up 4 Web Servers running Web Application (IIS) and Advanced Workflow services, 2 Services Servers, 1 Database Server, and 1 or more Cache Servers.

The following table describes the recommended configuration.

Cache Server (1)

Web Servers (4)

Services Servers (2)

Database Server (1)

 

Web Application

Archer Advanced Workflow service

Remaining services

Instance Database

 

Archer Configuration service

 

Configuration Database

Third-party caching application
  • If ScaleOut StateServer is selected, the ScaleOut StateServer client is required.
  • If Redis is selected, no client is required.
  • If ScaleOut StateServer is selected, the ScaleOut StateServer client is required.
  • If Redis is selected, no client is required.

 

Database Server

The following table lists the minimum required hardware and software elements to build a Database Server for a large environment.
Element Requirements

Processor

At least 16 total processor cores (Hyper-threading technology is not equivalent to multiple dedicated cores)

Operating System

Microsoft Windows Server

Memory

96 GB RAM

DB Version

Microsoft SQL Server with the latest available SP or Enterprise Edition

Disk Space

1 TB (for 600K to 750K content records)

800 GB (for 400K to 600K content records)

600 GB (for 250K to 400K content records)

2 GB (Configuration Database)

Disks

15K spindles are the minimum for the DB tier, though it is strongly recommended that you use a SAN with SSDs, either as regular disks, caching (for example, EMC FAST Cache), or for automated tiering. Distinct spindles for data, transaction logs, and tempdb are a necessity if SSDs are not available.

Network Interface

Required: 1 Gbps

Recommended: 10 Gbps

Important: For High Availability configurations, use a load balancer to route traffic equally between available web servers. A SQL Cluster with 2 database servers is recommended for database fault tolerance. You can use multiple cache servers to handle failover and high availability.

Web Servers

Archer recommends that you run the Web Application and Advanced Workflow services together on all 4 Web Servers and using a load balancer to route traffic equally between the servers.

The following table lists the minimum required hardware and software elements to build the 4 Web Servers for a large environment.
Element Requirements

Processor

At least 8 total processor cores (Hyper-threading technology is not equivalent to multiple dedicated cores)

Operating System

Microsoft Windows Server

Memory

24 GB RAM

Disk Space

50 GB

Network Interface

1 Gbps

Services Servers

The following table lists the minimum required hardware and software elements to build a Services Server for a large environment.
Element Requirements

Processor

At least 8 total processor cores (Hyper-threading technology is not equivalent to multiple dedicated cores)

Operating System

Microsoft Windows Server

Memory

24 GB RAM

Disk Space

50 GB

Network Interface

1 Gbps

Cache Servers

See the ScaleOut StateServer or Redis documentation for the requirements of a large environment.