There are a few options to add a license to ServiceControl.
Note that the license file might allow running multiple products (NServiceBus Core, ServiceControl and ServiceInsight). Therefore the license file can also be loaded from other platform tools to achieve the same end result, as long as the licensing method imports the license into the registry.
ServiceControl has a license user interface which can be accessed in ServiceControl Management. ServiceControl Management is installed together with ServiceControl and can be found in the Windows Start Menu.
The designated license file will be imported into the file system at
%ProgramData%\ so it is available to all instances of ServiceControl regardless of the service account used.
A copy of the imported license will be added to the
HKEY_LOCAL_MACHINE registry hive for backward compatibility with older instances of ServiceControl.
To import a license using PowerShell:
- Start PowerShell from the start menu, ensure ServiceControl PowerShell Module is loaded
- Execute the following cmdlet with the path to the license file.
It is also possible to load the license from the file system but this must be done manually. This allows the license to be loaded from (for example) a central network share instead of the registry.
NServiceBus/ application setting to the
ServiceControl. configuration file.
<add key="NServiceBus/LicensePath" value="d:\NServiceBus\License\License.xml" />
See the ServiceInsight licensing page or the instructions for licensing manually using the registry for more information.
In Versions 1.17 and below, a license can be applied to an individual instance rather than using a license installed in the registry. To do this, copy the
license. file to a
license directory under the installation path of the instance.
License information is read at service startup and cached for 8 hours. Therefore, either wait for the cache to expire or restart the ServiceControl instance manually to have ServicePulse reflect the new license.