Archer Configurations
Archer can be structured in various configurations, depending upon your unique needs.
It is recommended that you choose a configuration that is easily adaptable and scalable to the growing demands of your business. When determining which configuration is best for you, consider the expected user load, utilization, and availability requirements for your business operations. For additional information about optimizing performance, see "Planning the Archer On-Premises Environment" in the Archer Platform Help.
On this page
Recommended configuration
For optimal scalability and performance, it is recommended that you use a multiple server configuration for Archer. This configuration includes dedicated servers for hosting the Web Application and the services. Each server plays a specific role within the Archer configuration.
|
Database |
Description |
|---|---|
|
Instance |
The primary database for storing Archer content. The Content Database is synonymous with Instance Database. |
|
Configuration |
A central repository for configuration information for the Web Application and Services Servers. This database facilitates the installation and maintenance of multiple application servers in a multiple server deployment. |
Test environment configuration
The test environment configuration consists of a single server that hosts the Web Application and services. Archer recommends this configuration only for test environments. You can install other resources on additional servers. For instructions on how to set up this environment, see Test Environment.
