Manual Installation (ZIP)
The ZIP package holds the same application files as the EXE installer. The difference is that the EXE automates Node.js installation, service registration and the firewall rule. With the ZIP you do those steps yourself.
Use the ZIP when you want to control each step, or when you deploy behind IIS without running a wizard.
Prerequisites
- Windows Server 2016 or later. Windows 10 and 11 also work.
- Node.js v18 or later from nodejs.org. Check it with
node --version. - SQL Server 2016 or later — see Install SQL Server.
- A database and service account — see Create Database & Service Account.
- Administrator rights on the server.
Steps
- Extract
Primentra-vX.X.X.zipto your install folder, for exampleC:\Program Files\Primentra. - Open a command prompt as Administrator in that folder.
- Register the Windows service with the
nssmcommands below. Replace the paths with your own. - Add a firewall rule if users connect from other machines.
- Start the service and check that it runs.
- Open
http://localhost:3001and complete the first-run setup wizard.
Register the service
Run where node first to find the Node.js path. Replace PORT=3001 with your own port if needed.
Open the firewall
Skip this when IIS handles the traffic on port 80 or 443.
Start and verify
Open http://localhost:3001. You should see the Primentra setup screen. From here the steps are the same as for the EXE installer — connect to the database, deploy the schema, create the administrator account. See Install Primentra.
Upgrade from the ZIP
You can unpack a newer ZIP over an existing installation.
- Back up the database. On a virtual machine, take a snapshot as well.
- Stop the service:
net stop Primentra. A running service locks files, and the copy stops halfway. - Extract the new ZIP into the install folder. Replace all existing files.
- Start the service:
net start Primentra. - Open Primentra. If the database schema is older than the application, click Upgrade Database.
The ZIP does not contain mds-config.json or the logs folder. Your database connection, licence key, email settings and logs stay as they are.
web.config and dist\web.config. If you changed the port in one of them, change it again after the upgrade.Files that a newer version no longer uses stay in the folder. They do no harm.
Manage the service
You can also manage it in services.msc, under the name Primentra.
Change the port
Run this from the install folder as Administrator. It updates the service environment variable and restarts Primentra.
Related
- Install Primentra — the first-run setup wizard in detail
- Production Deployment (IIS) — put IIS in front of the service
- Health & Monitoring — check the service answers
- Troubleshooting — the service will not start