Archer Components

There are several main components to an Archer installation.

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

On this page

Web Application

The Archer Platform uses a web-based user interface that runs on a Web Server. Manage the Web Application through an Application Pool using Microsoft® Internet Information Services (IIS).

Microsoft Internet Information Service (IIS). For additional information, see System Requirements. The application is managed through an Application Pool through the Internet Information Services (IIS). For additional information, see Application Pool Requirements.

Instance Database

An Archer instance is a single setup that includes unique content in a database, the connection to the database, the interface, and user credentials. For example, you may have individual instances for each office location or region, or for development, test, and production environments.

File Repository

The File Repository stores components for the configuration. For example, the File Repository provides storage for the following services:

  • Attachments uploaded as content
  • Temporary files, such as packages, exports
  • Data feeds
  • Charts created by reports and searches

Configuration Database

The Configuration Database stores data that is not instance specific. For example, client information and application information (including date and version).

Services

There are several services, listed with Microsoft Windows Services, that control various functions of Archer. They control features such as configuration data, job engine, and advanced workflow.

The following table describes the Archer services.
Service Description

Archer Configuration

Connects to the Configuration Database, where configuration parameters of the Platform and Archer services are stored.

Note: This service must be installed and enabled on all web and Services Servers.

Archer LDAP Synchronization

Supports user and group maintenance by synchronizing the users and groups in Archer to users and groups in another system through Lightweight Directory Access Protocol (LDAP). You can only have 1  Archer LDAP Synchronization service enabled for an Archer instance.

Note: This service only needs to be active if you are using LDAP to manage user accounts.

Archer Job Engine

Administers all asynchronous job processing for Archer data feeds, findings generation, notifications, recalculations, and system jobs. For a complete listing of processing and system jobs, see "Job Types" in the Archer Control Panel Help.

Note: This service is required to be installed for Archer to run.

Archer Queuing

Builds and maintains indexes for keyword search and file attachments. You can only have 1  Archer Queuing service enabled for an Archer instance.

Note: This service is required on the Services Server assigned to queuing.

Archer Advanced Workflow

Administers the Advanced Workflow feature for processing workflows. This service is an integral part of Archer and should be running all the time. For solutions use cases in which the Advanced Workflow feature is available, workflow does not function unless the Archer Advanced Workflow service is running.

Note: As of version 6.1, the Advanced Workflow service can be installed on a Web Server or Services Server specified during installation. A example configuration dedicates Advanced Workflow service to 2 Web Servers behind a load balancer.

Archer Core

Interacts with the Advanced Workflow service to provide Advanced Workflow functionality. The Core service is an integral part of Archer and should be running at all times. For solutions use cases in which the Advanced Workflow feature is available, workflow does not function unless the Core service is running.

Note: The Archer installer automatically installs this service on each Web Server or Services Server where you install the Advanced Workflow service. An example configuration dedicates the Advanced Workflow service to 2 Web Servers behind a load balancer.

Archer Operational Risk

Interacts with the Advanced Workflow service to provide custom functionality for several applications in the Operational Risk Management solution. This service must be running in order to use the Operational Risk Management solution.

Note: The Archer installer automatically installs Operational Risk service on each server where you install the Advanced Workflow service.