Using xGT on an On-premises Server
XGT is available to be run on-premises. Demo licenses are available.
On-premises use can eliminate the need to move sensitive data off-premises (e.g., into a cloud repository) and, depending on the server configuration, can speed up the ingest of large volumes of data.
Trovares xGT is supported on the x86-64 systems shown in the table below. Support for other platforms is coming soon. Contact email@example.com for more information.
xGT supports both Python 2.7+ and Python 3.5+.
In addition to the OS packages, several Python packages are required:
$ pip install grpcio jupyter pandas protobuf
To acquire an on-premises license for Trovares xGT contact firstname.lastname@example.org. For questions about or assistance with configuring an on-premises version of Trovares xGT, contact email@example.com.
License Entitlement Process
xGT is protected by the Gemalto entitlement management system from Thales.
xgtd (the server component of xGT) is encrypted using the Sentinel Rights Management System (RMS) and requires confirmation of an activated license at run time.
Users will need to interact with the Trovares Entitlement Management System (EMS) in order to fulfill the entitlement requirements.
The following steps are required to get xGT installed on your server.
Step 1: Request an entitlement
This step involves contacting Trovares by sending an email to firstname.lastname@example.org.
Step 2: Download an electronic distribution
Once Trovares creates an entitlement for you, you will receive an email from the Trovares EMS system with login credentials and instructions on downloading the electronic distribution. The email will have a URL to visit for logging in, where you should use either the Entitlements ID (EID) or Product Key that is supplied in the email.
Step 3: Server setup
Once the distribution is brought to your server and you install using the standard practice of package installation on your OS platform, there are three primary executables installed along with supporting executables and libraries:
xgtd-- the xGT server
lsinit-- a program that prepares the local system to receive entitlements
echoid64-- a program used to produce a hardware code
These actions on your server are required before moving to the next step:
$ lsinitas root. This program creates persistent storage on your filesystem in order to enable the activation process.
$ echoid64. Below is an example output. You will need to extract the hardware code from this output and use it in the next step. The ending of the line that begins with "Locking Code 1" contains two pieces of information: a digit indicating the type of hardware lock and the generated hardware code. In our example output below, there is a "4-" indicating the type of hardware locking used followed by the hardware code of
*13V PLD2 45E8 G7KV.
Example echoid64 output: Sentinel RMS Development Kit 9.4.0.0023 Host Locking Code Information Utility Copyright (C) 2018 SafeNet, Inc. Locking Code 1 : 4-*13V PLD2 45E8 G7KV Locking Code 1 (Old Style) : 4-220F1
Step 4: Activate entitlement
The entitlement activation is done using the same URL and login information used to retrieve the distribution (in step 2). After logging in again, you will find an "Activate" button.
The hardware code from the previous step is needed during this activation process.
The activation page on the Trovares EMS site may suggest you need to run a program called
You may ignore that suggestion; the
Wechoid program from Gemalto is only applicable for running on a Windows server, and xGT runs only on linux systems.
The task of running
echoid64 described in the previous step is sufficient to obtain the hardware code.
The activation process will produce a license file that must be stored on the filesystem of your server.
Step 5: Running the xgtd server
There are two environment variables used to validate the entitlements at runtime.
LSFORCEHOST = NO-NET LSERVRC = /path/to/license/file
We recommend that the license file be stored in a file called
lservrc alongside the
xgtd executable, in which case only the
LSFORCEHOST environment variable is needed.
Otherwise, both variables are needed.