Altova LicenseServer can be installed on Windows systems in one of two ways:
•As an independent installation. Go to the Download page of the Altova website, download the installer package, and run the installation.
•As part of an Altova server product* installation. If you opt to include LicenseServer in the product installation, then the installer will automatically de-install any previous version of LicenseServer it might detect and install the new version.
* Altova server products are: Altova DiffDog Server, Altova FlowForce Server, Altova MapForce Server, Altova MobileTogether Server, Altova RaptorXML(+XBRL), and Altova StyleVision Server.
Windows 7 SP1 with Platform Update, Windows 8, Windows 10, Windows 11
Windows Server 2008 R2 SP1 with Platform Update or newer
Windows Server Core is a minimal Windows installation that does not use a number of GUI features. You can install LicenseServer on a Windows Server Core machine as follows:
1.Download the LicenseServer installer executable from the Altova website. This file is named licenseserver-3.8.exe. Make sure to choose the executable matching your server platform (32-bit or 64-bit).
2.On a standard Windows machine (not the Windows Server Core machine), run the command licenseserver-3.8.exe /u. This unpacks the .msi file to the same folder as the installer executable.
3.Copy the unpacked .msi file to the Windows Server Core machine.
4.If you are updating an earlier version of LicenseServer, shut down LicenseServer before carrying out the next step.
5.Use the .msi file for the installation by running the command msiexec /i LicenseServer.msi. This starts the installation on Windows Server Core.
Keep the .msi file/s in a safe place. You will need them later to uninstall, repair or modify your installation/s.
To test the return value of the installation, run a script similar to the following. The return code will be in the %errorlevel% environment variable. A return code of 0 indicates success.
start /wait msiexec /i LicenseServer.msi /q
For a silent installation with a return code and a log of the installation process, run:
start /wait msiexec /i LicenseServer.msi /q /L*v! <pathToInstallLogFile>
To modify the installation, run:
msiexec /m LicenseServer.msi
To repair the installation, run:
msiexec /r LicenseServer.msi
To uninstall Application, run:
msiexec /x LicenseServer.msi
To uninstall Application silently and report the detailed outcome in a log file:
start /wait msiexec /x LicenseServer.msi /q /L*v! <pathToUninstallLogFile>
When upgrading to a major version, you can retain your LicenseServer settings by using the properties listed below. To set a property, run the installation command with the property setting appended, like this:
msiexec /i LicenseServer.msi LS_WebServer_Host=127.0.0.1
In order to install LicenseServer, admin rights are required for the machine on which LicenseServer is to be installed.
New versions of Altova products can only be licensed with the version of LicenseServer that is the latest at the time of the Altova product's release. However, older versions of Altova products will work with newer versions of LicenseServer.
Consequently, if you are installing a new version of an Altova product and if your current LicenseServer version is not the latest, then de-install the older LicenseServer version and install the latest version from the Altova website. All registration and licensing information held in your older version of LicenseServer will be saved at the time of de-installation to a database on your machine, and will be imported automatically into the newer version of LicenseServer.
If you choose to install a newer version of LicenseServer without first de-installing your older version, then the older version will be de-installed automatically by the LicenseServer installer before the newer version is installed.
The version number of your LicenseServer is given at the bottom of all tabs of the LicenseServer configuration page.
Also see: Updating LicenseServer
After LicenseServer has been installed, the machine on which it has been installed does not need to be restarted. Make sure, however, that LicenseServer has been started as a service on the server machine (see next section).