How To Install SLP Distributor Host Service (KB19)

SLP Distributor is installed as a Windows Service on a customer premise and manages concurrent licensing between connected licensed applications. In addition to the licensing service endpoint Distributor also provides a web interface for administration of the service e.g. to activate licenses, view usages etc.

The Distribtor Host service needs to be running on a network accessable PC.

Deploying SLP Distributor

To deploy the service, you will need to

  • Extract the permutation files from your permutation; this will include a Slps.Distributor.Host folder
  • Copy/package everything within the Slps.Distributor.Host folder to the destination machine on which the service is to be installed
  • Install the service

 

The Distributor service is installed by executing the install command file with elevated permissions (e.g. running as Administrator)

install.cmd -install

 

You can verify that the "Inistech Slps Distributor" service is running by using Windows Services control panel (Run -> services.msc ).


Once installed, this service will by default listen to HTTP traffic on ports 8731 for Distributor Server and 2468 for Web Console. (These port assignments are configurable).

Diagnostics

When the service is running and the required ports (2468 and 8731) are open, the service should perform as expected. Internal diagnostic information is output to trace.log in the directory of each component. Client runtime application errors are output to %temp%\slp.log


Configuration Files

Slps.Distributor.Host.exe.config contains the port and virtual directory for Distributor Web (defaults are 2468  and web).

Service\Slps.Distributor.Services.dll.config contains appSettings for the port for Distributor Service (default is 8731)

Configuration of Protected Application

Your protected application will require an app configuration file that includes an <appSettings> for the Distributor Server. (i.e. the IP adresss (or the Server Name) and port of the service). We recommend using Server Name rather than the IP address because Server Name will rarely change which saves the strength to change clients' app config files accordingly:

<add key="Slps.Distributor.Service.BaseUri" value="http://192.168.0.23:8731/"/>  or

<add key="Slps.Distributor.Service.BaseUri" value="http://<ServerName>:8731/"/>