Just the same way DBT and NimPro are installed from an installer package (an .msi file), you install the Shared License Service from its .msi file, duxsls-100.msi. When you complete the installation, the network license-sharing service starts up automatically. This service allows other machines on the network to obtain their Duxbury activations from your server.
The DuxSLS installer guides you through each step, beginning with the End User License Agreement, which you must accept to continue.
By default the installer places the Shared License Service files in the "Duxbury\Shared License Server" folder. We recommend you accept the default location.
On the last page it pre-checks a box prompting you to "Configure and start service." This causes the Duxbury SLS Editor to open. If your installation includes multiple versions of Duxbury products or uses third-party software that is activated using "Sheriff," you need to configure them using the SLS Editor. Even if you have no complications, you must invoke the Editor to build the required initialization files and to start the service. If you uncheck this box, you will have to start the Editor manually to complete your installation. (Extra work – no gain.)
In the Duxbury SLS Editor, you will be prompted for the port number for the Shared License Service. The default is port 8080, and you can use that if it is not already in use or unsuitable for some reason local to your own network. If you chose a different port number in the Activation Wizard, enter that same port number here.
On this same screen, the Editor builds a list of checkboxes that allows you to indicate which Duxbury products are to be shared from this server. In the most common case, that list contains only the single version of the Duxbury program that you have just installed and activated. In the most complicated case, the list may include a range of Duxbury products and even third-party software.
Unless absolutely necessary, we do not recommend running third-party products (should any be listed) under the same port number as your Duxbury applications. In most cases, conflicts between Duxbury and third-party software may be resolved by editing the content of the initialization (.ini) files per the next screen in the Editor. Consult documentation on your third-party software if you need to do this. Normally no editing of these settings is required.
Finally, you must click the "Start Service" button to launch the Duxbury Shared License Service. You can confirm this service is running by finding it under this name in your "Administrative Tools: Services" screen.
The Duxbury Shared License Service is not added to the list of rules (or programs) in your firewall automatically. You must edit the Inbound Rules of the Windows Firewall (or similar program list on your third-party firewall) to add this service.
Using Windows 7 as an example:
In the Windows Firewall, you need to access the "Advanced settings" (administrative level) functions.
To avoid confusion, we suggest you name the new entry, "Duxbury Shared License Service."
Assuming you have installed the Shared License Service in the normal default location, the program you need to allow is under the "Duxbury\ Shared License Server" folder. The program you need to allow is named slsServer.exe.
Once you make the new entry, you can open the specific port number that this service communicates on. In the Windows Firewall this setting is found under the Properties of the Duxbury Shared License Service.
Please, consult your specific firewall documentation for additional guidance.