New in phaf 26.11.1: Windows installer, CSV, Email and REST connectors. Release notes → A Spectro Web Solutions product ↗ EN PL

Installation guide · Windows Server

Installation overview

What you receive, what you need and the steps from the installer to a running phaf.

phaf DATA CONNECTOR is installed by you, on your own Windows server, with one installer. The installer copies phaf and the runtime it needs, creates the data folder and the configuration, and registers phaf as a Windows service that starts with the server. This guide takes you from the installer to a secure, running phaf. Allow about 30 minutes for a first installation.

What you receive

We send you two files:

FileWhat it is
phaf-<version>-setup.exeThe installer, about 50 MB. It contains the application, the Node.js runtime and the Windows service. You do not need to install Node.js, npm or internet access on the server.
phaf-<version>-setup.exe.sha256The SHA-256 checksum, to check that the installer arrived intact.

The installer holds no data, no passwords and no keys. Your encryption key, users and settings are created on your server the first time phaf starts.

The steps

  1. Check the requirementsWindows Server, disk space, network access to your partners and databases.
  2. Run the installerVerify the file, run it as administrator and create the first administrator.
  3. Choose the application databaseKeep SQLite, or move phaf's tables to SQL Server.
  4. Check the Windows serviceThe service the installer created, and the account it runs as.
  5. Publish over HTTPSPut IIS or nginx in front of phaf so users connect securely from their own computers.
  6. Secure and configureTwo-factor authentication, password policy, IP rules, email alerts and backups.

How the pieces fit

Users

Browserhttps://phaf.your-company.local

Your Windows server

IIS or nginxTLS certificate
phaf serviceC:\phaf\app
Data folderC:\phaf\data — key, settings, messages

Your systems

Application databaseSQLite file or SQL Server
Partners and databasesservers your flows connect to

phaf listens on the server itself (127.0.0.1). Users reach it through the HTTPS proxy, never directly.

Folders

The installer uses these folders by default. You can choose others during installation — the application and the data always stay in separate folders, so an upgrade never touches your data.

PathContentsChanges on upgrade?
C:\phaf\appThe application, the Node.js runtime, the service and config.json.Yes — replaced by the new version, except config.json.
C:\phaf\app.previousThe version before the last upgrade, kept for roll back.Replaced at each upgrade.
C:\phaf\dataEncryption key, users, settings, workspaces, certificates, messages and the SQLite database.No. The installer never changes it.