Prev | Next |
Install and Configure
The Sparx Systems Pro Cloud Server product is installed using a standard Microsoft Windows Installer package that includes a number of components. The Floating License Server is included in the main 'Pro Cloud Server' component. It is possible to change the install location of the Pro Cloud Server; however this document assumes the default install location of C:\Program Files (x86)\Sparx Systems\Pro Cloud Server\ (assuming a 64 bit machine is being used).
Important: All communications to the Pro Cloud's Floating License Server are performed via HTTPS; therefore, to use the Pro Cloud Server's Floating License Server functionality at least one Port has to be configured to use the HTTPS protocol, and a valid certificate/private key file must be defined in the Pro Cloud Server's Services folder. See the Self-Signed SSL Certificates Help topic for more details.
The main Pro Cloud Server's configuration file (SSProCloud.config) defines two settings related to the Floating License Server: FLOATLIC_PATH and FLOATLIC_CONFIG.
The FLOATLIC_PATH option defines the path and file name of the Key Store file; by default this is:
%SERVICE_PATH%\sskeys.dat
"%SERVICE_PATH%" is replaced with the physical path of the 'Services' folder (that is, 'C:\Program Files (x86)\Sparx Systems\Pro Cloud Server\Service').
The FLOATLIC_CONFIG option defines the path and file name of the Key Store group file; by default this is:
%SERVICE_PATH%\ssflsgroup.config
Floating License Server Group Configuration File
The Pro Cloud Server's Floating License Server component installs a configuration file called ssflsgroup.config into the Service folder (C:\Program Files (x86)\Sparx Systems\Pro Cloud Server\Service\ssflsgroup.config). This file defines 'groups' of users that can obtain Licenses from the Floating License Server, and also controls which Enterprise Architect Product Licenses each group can use.
A group is identified by a group name and a set of credentials (user ID and password) that will be used to securely communicate with the Floating License Server over HTTPS.
From Pro Cloud Server v4.2 (build 60) the Floating License Server Group configuration file can be maintained using the Floating License Server Configuration Client (see Manage Group Configuration), prior to this editing the file was a manual process.
The Floating License Server's configuration file will typically consist of multiple group definitions; each group definition must be defined as shown:
GROUP
Name=human_resources
UserName={user name}
Password={password}
IsManager=false
ENTITLEMENT
Product=UltimateSuite
Academic=false
Limit=10
END ENTITLEMENT
ENTITLEMENT
:
END ENTITLEMENT
END GROUP
Group Definition Properties
A Group definition begins when the token GROUP is encountered on a new line, and extends until the token END GROUP is found on a new line.
Property |
Description |
See also |
---|---|---|
Name |
The common name of the Floating License group. |
|
UserName |
Required. Specifies the User ID for the Floating License Group. |
|
Password |
Required. Specifies the Password for the Floating License Group. |
|
StartDate |
Optional. Used in combination with the EndDate property to define the date range within which the Group can be used. |
|
EndDate |
Optional. Used in combination with the StartDate property to define the date range within which the Group can be used. |
|
Entitlement - Section |
Each Group can define multiple Entitlements. An Entitlement definition begins when the token ENTITLEMENT is encountered on a new line, and extends until the token END ENTITLEMENT is found on a new line. Each Entitlement definition accepts each of these sub-properties:
The valid Product codes are:
|
|
IsManager |
Optional. Specifies whether members of this group are permitted to perform management operations (such as add/remove keys) on the keystore. Default Value: false |
Configuration Changes
Changes to the Pro Cloud Server's Floating License Group file can be made while the Pro Cloud Server is running, without the need to restart it. The Floating License Server component will detects the last modified time, if the configuration file has changed since it was last read the entire content of the file is re-read.