This page covers the process for a new installation of the CHPS Floating Licence Service. Some of the steps involved are also applicable for upgrading, configuring or troubleshooting the service.
See Upgrading Floating Licence Service for the process for upgrading from a previous version of the Floating Licence Service.
Components involved in managing CHPS floating licences are:
•CHPS Floating Licence Database (SQL Server Database)
•Floating Licence Web Service (ASP .NET Web Service)
•The Web Server on which the CHPS Floating Licence Service is to be installed must meet the following criteria:
oBe accessible to all CHPS client computers on the network
oAble to connect to the database server on which the CHPS Floating Licence Database is to be installed.
oBe able to connect externally to the GBS Licensing Service. The service URL is https://gbslicensing.azurewebsites.net/LicensingService.
oMicrosoft Internet Information Services version 6.0 or greater.
oMicrosoft .NET Framework version 4.0
•The Database Server on which the Floating Licence Database is to be installed must be the following criteria (note that the database and service can potentially be on the same server):
oBe accessible to the server hosting the CHPS Floating Licence Service
oMicrosoft SQL Server 2008 or newer.
•Administrative rights are required for installation.
1.Have your CHPS Floating Licence Activation Key handy.
2.Decide on the deployment model: Single-server or Multi-server
a.Single-server: all the components reside on the same server.
b.Multi-server: each component resides on a different server.
3.Decide on the authentication model to be used when connecting to the CHPS Floating Licence Database: Windows or SQL Server
a.Windows Authentication: the Floating Licence Web Service will connect to the Floating Licence Database using a Windows account. This requires the identity to be provide of the application pool assigned to the Floating Licence Web Service to be specified.
In a Multi-server setup, this account must be an Active Directory account. Single-server setup can utilise either an Active Directory or Local account.
b.SQL Server Authentication: the Floating Licence Web Service will connect to the Floating Licence Database using SQL Server login credentials. This requires the username and password of the SQL Server login to be entered into the Floating Licence Web Service configuration file.
4.Identify the IIS web site and application pool to be used for the Floating Licence Web Service. The default web site and application pool will typically be fine. Otherwise, create them as required. Note these details as they are required later in the process.
5.If using Windows Authentication, specify the identity that the application pool will run as. If in a Multi-server setup, this must be an Active Directory account.