<< Click to Display Table of Contents >> You are here:  Introduction to Sage Paperless Construction > Sage Paperless Construction - Initial Setup > Deployment Technical Playbook

Sage Paperless Construction is comprised of the following three main components:
 

•SQL Server Database Engine
Sage Paperless Construction uses a Microsoft SQL Server Database as the backbone of our program. We use a referential database to store your company’s data. By default, we install SQL Express, but due to its limitations on size and performance, it is always recommended that our customers have a SQL Standard license.

•Sage Paperless Construction Application Server
The Sage Paperless Construction Application Server is comprised of three services:

oApplication Service: The main service that handles all the data requests and work between the database and document file repository.

oJob Poll Service: A task scheduling service, which triggers configurable jobs from within the Sage Paperless Construction software. These jobs include importers, database maintenance, email notifiers and more.

oCloud Sync Service: Supports our mobile and portal applications. Data is synchronized from your on-premises server and hosted securely at rest within our secure Azure storage. Once the data is synced to our secure cloud, the four applications communicate only with that data and never directly connect back to the on-premises environment.

•Document Repository (Flat-File)
The document repository is a flat-file document storage location. Sage Paperless Construction stores your data in a standard windows NTFS folder structure. We do not compress or encrypt files; they are stored in their native format. It is highly recommended that documents imported into Sage Paperless Construction are captured at the recommended resolution and size.

 

Installation Models

 

There are three different models you can choose from for your Sage Paperless Construction installation. Sage Paperless Construction can be installed on-premises or in a cloud-hosted environment. Sage Paperless Construction can be installed in either a Domain or a workgroup network environment; however, domain is recommended.

 

Note: We do not recommend installing Sage Paperless Construction on a domain controller or installing any Sage Paperless Construction services/applications on the OS drive or volume within your server.

 

Installation Models:

 

•All-In-One: The easiest and most common way to install Sage Paperless Construction. In this model, we install all three components on the same server within our directory.

•Fully Distributed: SQL Database, Sage Paperless Construction Application Server and Document Repository are installed on three separate servers.

•Hybrid: A hybrid of the two options listed above. You have one component standalone (usually SQL) and two other components together (typically Application Server and Document Repository). It can be any combination of the three components, with SQL most commonly being installed on its own server.

 

Client Deployment

Sage Paperless Construction has a thick client that can be installed and deployed using several methods.

 

We support individual workstation installation, Remote Desktop Services (RDS) deployments and Published Applications (MS published app, Citrix, etc.)

 

VPN Deployment

Sage Paperless Construction access through client VPN endpoints is not a supported deployment method. While the Sage Paperless Construction application can be accessed via a client VPN endpoint, performance may be severely degraded. It is recommended that end users VPN into the main network and use an RDS or Published app connection to access Sage Paperless Construction.