Message API/docs/installer/overview

Installer Overview

What ViewsoftInstaller.exe installs, the installation flow, and what to do after installation.

Prerequisites

Before running the installer, ensure these requirements are met.

  • Windows Server or Windows 10/11
  • Administrator rights (Run as Administrator)
  • IIS installed with Static Content feature (required for all packages)
  • Node.js installed (required for running the db backend)

Download Releases

Download the current supported installer for new deployments and upgrades.

This release includes Placement-related updates and Batch Export support. After installation, or after any backend .env change, restart the DB backend process or service so the new configuration is applied.

Installer releases

Download the version you need

Stable
VersionRelease dateNotesDownload
4.0.5
Available nowAdded insertCountPointMode support for count annotations, enabling continuous count-point placement that can be turned on and off by annotation GUID.Download
4.0.6Latest
Available nowUpdated fixes in annotation styles | update the pages list, selection.Download

What is the Installer?

ViewsoftInstaller.exe is a self-contained Windows installer (Burn bundle) that installs three MSI packages in sequence.

The installer bundles everything needed, just download and run as Administrator.

  • Backend: 3rd-party Rasterex document viewer engine
  • Viewsoft Backend: Express.js server files for API and file processing
  • Viewsoft Canvas: The user interface for viewing and interacting with documents

Installation Flow

Packages install in this order. Each must complete before the next begins.

  • 1. Backend: Interactive license UI (user must accept)
  • 2. Viewsoft Backend: Copies server files to C:\Program Files\ViewsoftBackend
  • 3. Viewsoft Canvas: Creates IIS site on port 4203

What the Installer Does NOT Do

After installation, additional configuration is required for production deployments.

  • Does NOT install Node.js - You must install Node separately to run the backend
  • Does NOT run the backend as a service - See the NSSM page for service setup
  • Does NOT configure HTTPS/SSL - See SSL & Domain Setup for production security
  • Does NOT set up reverse proxy - See Reverse Proxy page if routing backend through IIS