Install the Server Components
On this page
Use Advanced Installation in the unified installer to install Alloy Navigator components one target at a time. For each target, the installer checks prerequisites and starts that target's setup program.
The Alloy Navigator setup program relaunches itself with administrative privileges when it is not already running elevated. The Web App, Self Service Portal, and API setup programs require administrative privileges, so Windows asks for elevation when they start.
Before you begin
- The machine must not have a version 8 Alloy Navigator Express product installed: Alloy Navigator Express, or its Web App, Self Service Portal, Mobile Portal, or API. When the unified installer finds one, the product compatibility check fails for every target except Microsoft SQL Server 2017 Express Advanced, and the Alloy Navigator setup lists an installed Alloy Navigator Express of the version 8 lineage in an error message and stops. An Alloy Navigator Express 6 or 7 installation is not detected and does not stop the installation.
In the Installer
Choose a target
- On the unified installer's Welcome page, choose Advanced Installation.
- Choose a target from one of the three groups on the page:
- Desktop Apps and Server Components: Alloy Navigator or Alloy Discovery.
- Web Services: Web App, Self Service Portal, or API.
- Other Software: Microsoft SQL Server 2017 Express Advanced, which installs the database engine if you do not have a SQL server to host the product's database.
- Install the target. The unified installer first shows the prerequisites for that target, then starts that product's own setup program.
The SQL Server target starts Microsoft's own SQL Server setup with no preset options: the setup's prompt for an extraction folder and the SQL Server Installation Center, including the choice of authentication mode, are yours to complete. The unified installer stays on the Advanced page.
Prerequisite checks
The installer builds a separate list of checks for each target, so a check that one target runs is absent for another.
| Check | Alloy Navigator | Web App | Self Service Portal | API | SQL Server Express |
|---|---|---|---|---|---|
| Product compatibility | Yes | Yes | Yes | Yes | - |
| OS version | Yes | Yes | Yes | Yes | Yes |
| Physical memory | Yes | Yes | Yes | Yes | Yes |
| IIS state | - | Yes | Yes | Yes | - |
| .NET Framework 4.8 | Yes | Yes | Yes | Yes | Yes |
| ASP.NET Core hosting bundle | - | On a first installation, or an upgrade without the module | On a first installation, or an upgrade without the module | - | - |
| PowerShell | Yes | Yes | Yes | Yes | - |
| Free disk space | Yes | Yes | Yes | Yes | Yes |
| HTTPS on existing instances | - | On an upgrade | On an upgrade | - | - |
| Check | Passes when |
|---|---|
| Product compatibility | No incompatible Alloy product is installed. The check fails when it finds a version 8 Alloy Navigator Express product (Alloy Navigator Express, its Web App, Self Service Portal, Mobile Portal, or API), either Administrative Tools 8 package, or version 8 of the Mobile Portal. |
| OS version | 64-bit Windows 8 or Windows Server 2012 or later. 32-bit Windows 8, Windows 10 and later, and Windows 7 SP1 or Windows Server 2008 R2 SP1 also pass, except on the SQL Server target. On the SQL Server target, a domain controller fails. |
| Physical memory | At least 1 GB when SQL Server is being installed, otherwise at least 500 MB. |
| Free disk space | The Program Files volume has at least the sum of the figures for the components being installed: Alloy Navigator 600 MB, Web App 120 MB, Self Service Portal 32 MB, API 32 MB, SQL Server Express 4300 MB, .NET Framework 4.8 2560 MB, ASP.NET Core hosting bundle 390 MB. |
| .NET Framework 4.8 | .NET Framework 4.8 is installed. |
| ASP.NET Core hosting bundle | The ASP.NET Core Module V2 for IIS is installed, version 16.0.21322.1 or later. |
| PowerShell | The PowerShell 3 engine is installed. When the check fails, its message names PowerShell 3.0 or later, up to 5.1. |
| IIS state | IIS is installed and configured, including the Windows Authentication role service, and the IIS web service (W3SVC) is running. The installer offers to start the service. Windows Authentication is required even if you plan to use another authentication method. |
| HTTPS on existing instances | Checked only when you upgrade a Web App or Self Service Portal of a version earlier than 2024; a first installation is never checked. Every existing Alloy instance must have an HTTPS binding: HTTP together with HTTPS gives a warning, HTTP alone fails. |
On the Advanced route, an operating system older than Windows 7 SP1 or Windows Server 2008 R2 SP1 and insufficient memory give a warning rather than a failure; on the SQL Server target, an unsupported operating system still fails.
While any check fails, the installer does not let you continue; a warning does not block it. The checks run when the page opens. When you click Recheck, the installer first re-reads the system path, so a path change made by a prerequisite you have just installed takes effect without restarting the installer. To see the details of a failed or informational check, click its message. The details dialog can show a link and, for .NET Framework 4.8 and the ASP.NET Core hosting bundle, a button that starts the installer for that prerequisite and closes the dialog.
Install Alloy Navigator
- Start the Alloy Navigator target. On a first installation, the setup shows Welcome, License Agreement, and Setup Type.
-
On Setup Type, choose the setup type, and change the installation folder if you need to. This is the only page where you choose components.
- Client (the default): Settings and Database Tools, including the Import tool. It leaves out the Automation Server, the Server Manager, Active Directory Import, Mail Connector, the Data Archiving Service, the Scheduled Task Agent, the Alloy Discovery Connector, and AlloyScan.
- Server: the Automation Server with the Server Manager, Active Directory Import, Mail Connector, the Data Archiving Service, the Scheduled Task Agent, the Alloy Discovery Connector, and AlloyScan, plus Settings and Database Tools.
- Full (Client and Server): every component.
The Server type leaves out the report viewer, the Audit Viewer, the spell-check dictionary, and the barcode font, which Client and Full (Client and Server) install. No page asks you to choose report viewer parts separately. 3. On a first installation, if a version 6 or 7 installation is found, the Previous Installations page shows one Uninstall box for each version found, captioned with that product's name. Both boxes are selected by default, and a selected box removes that version. Clear a box to keep that version beside the new one. An installation of the current product line is upgraded in place and cannot be kept beside the new version. 4. When the setup is ready to install, start the installation. 5. On the finish page, the Run the Database Management to create a new Alloy Navigator database box starts the Database Management wizard when the setup ends; see Create the Database. The setup picks the mode for you: depending on what it finds on the machine, the box offers either to create a new database or to upgrade the existing one. When the setup had to relaunch itself with administrative privileges and your account is not a member of the local Administrators group, the wizard starts in your own session.
The setup also installs Microsoft Report Viewer 2016 and its SQL Server CLR Types prerequisite silently when they are missing, by two paths. The Alloy Navigator package installs them on an installation that is neither a maintenance run nor an upgrade of the current product line, when it finds the extracted Report Viewer package and CLR Types is installed or its package is present. After the package, the setup program installs each one that is still missing, provided one of the Alloy products in its list is installed. When the package's own path ran and Report Viewer is still missing afterward, the finish page shows "Microsoft Report Viewer for SQL Server 2016 was not installed."
Beyond copying files, the setup runs the following actions. If any of them fails, the installation fails.
- When it installs the Automation Server, it runs
AServer.exe /install /silent. - When it installs the report viewer, it registers it with
ReportView.exe /regserver. - On a first installation or a major upgrade, it creates the registry key
HKLM\SOFTWARE\Alloy Software\Access Keys, and when it installs the Automation Server, the keyHKLM\SOFTWARE\Alloy Software\Alloy Navigator\Service Connection. The setup writes no key or connection into them.
When the machine has an Alloy Navigator Express of the version 8 lineage or either Administrative Tools 8 package installed, the setup lists those products in an error message and stops. An Alloy Navigator Express 6 or 7 installation does not stop it.
Install the Web App, Self Service Portal, or API
The three web packages show the same pages.
- Start the Web App, Self Service Portal, or API target.
- On a first installation, go through Welcome and License Agreement to Setup Type, where you can change the installation folder with Change.
- When the setup is ready to install, start the installation.
- On the finish page, the Run the Web Configuration box (Web App and Self Service Portal) or Run the Web Configuration Manager box (API) opens the Web Configuration tool, where you configure a new instance; see Publish the Web Applications.
When the Web App setup is not an upgrade, its finish page can also show the warning "Microsoft Report Viewer for SQL Server 2016 was not installed."
If an Alloy web product of version 8.7.2 or 2024.2 (24.2.0), such as a Web App, Self Service Portal, or API, is installed on the machine, the setup program first closes every running Web Configuration tool without a prompt and replaces that version's Web Configuration tool. If the old tool cannot be deleted, the setup leaves it in place without a message.
When a web package upgrades or patches an existing installation, the setup goes from Welcome straight to Files Backup, without License Agreement or Setup Type. The page states that the upgrade replaces all files. The backup box is selected by default, and the backup folder defaults to a dated subfolder of the Backups folder in the installation folder. Customized instance files survive only in that backup. After an upgrade, the finish page does not offer the Web Configuration tool; the setup runs the tool to carry the settings of the existing instances forward instead of asking for them again.
An administrative installation goes from Welcome to a network location page and installs from there; it does not offer the Web Configuration tool either. The finish page also does not offer the tool when the package is already installed.
Client and administrative tools
- The Client setup type of the Alloy Navigator target installs Settings and Database Tools without the Automation Server and the other server components.
- A separate Administrative Tools package also exists. It cannot share a machine with the Alloy Navigator package: the Alloy Navigator setup lists an installed Administrative Tools 8 package in an error message and stops, and the Administrative Tools setup refuses to install where Alloy Navigator is present. Like the Alloy Navigator setup, the Administrative Tools setup relaunches itself with administrative privileges when it is not already running elevated.