Product Licensing

Product Licensing

All Products
v12.5 SP1 - Feb 2018

This document discusses the licensing scheme for Logi Info v12 and its add-on modules and the most common license-related situations you're likely to encounter. Topics include:

 

About Licenses

All Logi products are licensed to customers using legal documents executed as part of the sales contract. Most products require the issuance of a license key (stored in our licensing system) and the presence of a license file on the system where the product and/or application is installed.

Logi Analytics licenses are server-based, rather than individual-user- or concurrent-access-based, so an unlimited number of end-users can access Logi reports through a single web server. Our Logi Info licensing scheme allows you to install our product on one development machine and one production server.

Logi Info requires a license for both our development tool, Logi Studio, and for our Server Engine, which is part of each Logi application you create. Your development system will likely require both but production web servers generally do not need Studio installed on them. So, for Logi Info we offer both a "Studio and Development Server" combination license and a standalone Server license, and this two-license approach allows flexibility in different situations.

 Logi is introducing new Application Services/Data Services (AS/DS) technology, requiring license files for the new versions of some add-on modules and products that previously did not need them. The associated license files are available for download from DevNet, as usual.

Here are the products and their license file requirements:
 

Products License Requirements

Logi Info, pre-v12.5

Requires Logi Info license file

Logi Info, v12.5+
includes Discovery v3.0 with AS/DS

Requires Logi Info v12.5 and Discovery v3.0 license files, or
Logi Info v12.5 and SSM v12.5 license files, or
Logi Info v12.5 and SSM v12.5 + DataHub v3.0 license files

Discovery Module pre-v3.0

Requires presence of Logi Info license file

Discovery Module v3.0+
with AS/DS

Requires Discovery v3.0, or
SSM v12.5 license file, or
SSM v12.5 + DataHub v3.0 license files

SSM pre-v12.5

Requires presence of Logi Info license file

SSM v12.5+

Requires SSM v12.5 license file, or
SSM v12.5 + DataHub v3.0 license file

DataHub pre-v3.0

Requires presence of Logi Info license file

DataHub v3.0+

Requires DataHub 3.0 license file, or
SSM v12.5 + DataHub v3.0 license file

 

Major Version Compatibility

If you upgrade an existing installation of one of our products, or an existing Logi application, from one major version to another major version, for example v11 to v12, you will need a new license key and file for the new product/application. Contact Customer Service if you want to upgrade and need a new license.

  Back to top

 

Built-in Trial License

Logi products come with a built-in 15-day trial license. You don't need to do anything but install the product and you can begin using it immediately. For Logi Info, a clearly-visible display, shown below, in the Studio main menu counts down the days remaining in the trial period.
 

Clicking the Studio license counter-down display will take you to a web page that offers information about purchasing a product license.

  After the Logi Info 15-day trial license period expires, unless you have a regular license file in place Studio will no longer start up and any Logi reports you've developed will no longer run. An expired trial license will cause other Logi products to block access to certain features and/or prevent you from saving your work.

  Back to top

 

License Keys and License Files

When you purchase a Logi product, here's what happens in the licensing process:

  1. We create a license key for each product you buy, specific to you or your organization, in our licensing database.
  2. You log into DevNet and visit the License Manager page to create a license file. You do this by assigning one of your license keys to a specific computer, by Computer Name. DevNet then generates a license file.
  3. You download this file and use it to license Logi Studio and each Logi Info application you develop, or other Logi products.
  4. Repeat Steps 2 and 3 for any additional license files required.

A typical license file name is lgx120201.lic and licenses are product-specific. License files are the same for both .NET and Java deployments.

When you download your license file, save it to:
 

Product/Platform

License File Location

Logi Info on Windows

C:\Program Files\LogiXML IES DEV\LogiStudio and in the application folder of any existing Logi application that you've created with a trial license, or any application that's being upgraded to v12.

Logi Info on Linux/UNIX

See the discussion below, in the License Management section.

Discovery 3.0

Installation folder, default is C:\LogiAnalytics\Discovery

SSM 12.5

Installation folder, default is C:\LogiAnalytics\Discovery

DataHub 3.0

Installation folder, default is C:\LogiAnalytics\Discovery

SSM 12.5 + DataHub 3.0

Installation folder, default is C:\LogiAnalytics\Discovery

 

Discovery 3.0+. SSM 12.5+, or DataHub 3.0+ Licenses

The very first time one of these products runs, the contents of any license file found (usually the trial license) are automatically copied into the Platform Database (PDB) and used directly from there. After that, any license file in that folder will be ignored. When the trial license expires or if you need to use a different license, you'll need to perform the steps detailed below in the Other Products: Missing or Expired License section to "replace" the license in the PDB with another license.

 If you deploy your PDB to another computer, for example by copying it from a development system to a production system, you will need to replace the development system license in the PDB with the production system license using this technique.
 

Moving a License to Another Machine

If you need to move an application to another machine, or to re-install your Logi product on a different machine, you can "un-assign" the license you've been using from one machine, assign it to another one, and generate a new license file.

OEM licenses operate in a similar fashion, but can be assigned to multiple machines.
 

Logi Info Centralized License File

If you have a large number of Logi Info apps on the same development machine or web server, you may care to use a single, centralized license file rather than managing multiple license file copies.

In Logi Info v12, the General element in the _Settings definition includes a License File Location attribute where the location of a centralized license file can be specified. This value is a fully-qualified web server file system path to the folder where the file is stored. For example, C:\myProjects\License.

 You must ensure that all web applications that will use this license run under an account that has file access permissions to access files in the folder you specify as the centralized license file location.

With this centralized license file approach, if you use the exact same file path to your license file on both your development machine and your production server, you can deploy Logi applications by copying them, without having to replace the license file or adjust your _Settings attributes each time.
 

Logi Info OEM License File

Customers with Logi Info OEM licenses can embed the entire license key inside their Logi application. In the _Settings definition, the General element has an OEM Distribution License attribute which allows Logi applications to run on a server that does not otherwise have a license key installed. This is especially useful for XCOPY-type deployments: the Logi installation program does not have to be run on the web server.

To use this attribute, double-click the attribute name to open its Zoom window and then copy the entire XML contents of your OEM license file into it. This attribute only works with OEM licenses; other types of licenses copied into here will be ignored. 

  Back to top

 

License Management

DevNet includes a License Management page where you can manage your product licenses and download license files. In order to manage your licenses, you must be a DevNet member and login to the DevNet site, then go to SupportManage Licenses. 


  

The details of the License Management page are shown above and explained below:

  1. Products, Status, Search - These controls let you filter the table of license keys, by product type and status, and search based on License Key name.
  2. Export - Use these icons to export your license key list to Excel or PDF.
  3. License Key Name - The license key we created for you when you purchased the product appears here.
  4. Type & Expires - The license type and expiration date appear here.
  5. License - License actions: click the "Create" link in this column to assign your license to a specific machine. Once done, the machine name will appear in the next column and the link will change to "Download". Click the link again to download and save your license file. You may download the file as many times as necessary but it's only valid on the assigned machine.
  6. Assigned To - The name of the machine a license has been assigned to. The icon allows you to "un-assign" the license - when this is done, the License link will revert back to "Create", and you may assign the license to another machine.
  7. Note - This column displays optional text you enter to help you more easily identify the computer. Click the icon to add or edit this text.
  8. Log - Click the icon to display the history of assignments for this license.


Here are the details of the process of creating and downloading a license file:
 

If the link in the Licenses column of the table shown earlier says "Create", clicking it will display the Create License File pop-up panel, shown above. You use it to assign the license to a specific machine, by entering the computer name. The Optional Note input is for your use if you want to further identify the machine and its text appears in the table of licenses shown earlier.

If the computer on which this license is to be used runs a Windows OS, then the computer name value is what's known in Windows parlance as the "machine name". You can open a Command Prompt window on the machine and enter "hostname", then press Enter to have the name displayed. If a multi-part name is displayed, such as "myPC.myCompany.local", use just the first part, "myPC".

If the computer on which this license is to be used runs a Linux or other UNIX-derivative OS, then the "computer name" value is the computer's "hostname". You can go to a command line and enter "#hostname", then press Enter to have the name displayed. Use the full hostname value, exactly as it's displayed, for your computer name value entry

Click OK to generate the license file for the designated computer.

 


Once the license file has been generated, the link in the Licenses column will change to "Download". Click this link to display the Download License File pop-up panel, shown above. Click Download to download and save the license file.

 Some browsers may add an .xml file extension to the downloaded file, which is wrong. A typical license filename looks like lgx120201.lic so don't let your browser add anything to it.

If the computer on which this license is to be used runs a Windows OS, then save the license file to

    C:\Program Files\LogiXML IES Dev\LogiStudio

This will provide licensing for development work using Logi Studio, as well as for new Logi applications that are developed on the machine and run there using any web server. If you're upgrading any older Logi applications, you'll also need to copy the license file into their application folder.

If the computer on which this license is to be used runs a Linux or other UNIX-derivative OS, then the license file location will depend on how you start the web server. If you start it from the bin folder, then save the license file there. If you start it elsewhere, for example, by running a script, then save it to the folder that you run the script from.

  Back to top

 

Logi Info: Missing or Expired License

As mentioned earlier, Logi Studio and your Logi Info applications require license files.
 

If no license file can be found when you start Logi Studio, a trial license will be automatically created but it may be expired (it's based on the date when the product was installed). If so, you'll see a message similar to the one above and be unable to use Studio.

 

If no license file can be found when you try to browse a Logi application, you'll see a message similar to the one above in your browser, instead of the application page.

Providing copies of a valid license file in the correct locations will allow Logi Studio and the application to run.
 

Logi Info Trial License Expires

When your trial license expires, and there is no regular license, you'll see the following messages:
 

If the trial license has expired, when you start Logi Studio, you'll see a message similar to the one above and be unable to continue to use Studio.

 

If the trial license has expired and you try to browse a Logi application, you'll see a message similar to the one above in your browser, instead of the application page.

Providing copies of a valid license file in the correct locations will allow Logi Studio and the application to run.
 

Logi Info Regular License Expires

When your regular license expires, you'll see the following messages:

 

If the regular license has expired, when you start Logi Studio, you'll see a message similar to the one above and be unable to continue to use Studio.

 

If the regular license has expired and you try to browse a Logi application, your application page will be displayed with a special warning banner added at the top, as shown above. A 7-day grace period is provided from the date when the license expired.
 

Once the grace period ends, reports will no longer run and only the message shown above will be displayed in the browser.

Providing copies of a valid license file in the correct locations will allow Logi Studio to be used and the application to run without the warning banner.

  Back to top

 

Other Products: Missing or Expired License

Other licensed Logi products, including the Discovery Module, SSM, and DataHub react differently when their licenses expire. A product or feature that requires a login, such as Dataview Authoring, will display an error message when a login is attempted:
 

Some products will allow you to view data but you cannot save visualizations or changes if the license has expired.

Other products will cause the Logi Info applications they work with to throw an error, with a descriptive error message in the usual format.
 

Replacing Expired License Files

If your license for Discovery 3.0+. SSM 12.5+, or DataHub 3.0+ expires, you'll need to replace it.

The very first time one of these products runs, the trial license file contents are automatically copied into the Platform Database (PDB) and used directly from there. After that, the actual trial license file and any other license files subsequently placed in the folder, will be ignored. You'll need to perform the following to "replace" your trial license with an extended-trial or regular license.

WINDOWS: The license file record can be deleted from the PDB, and another one inserted to replace it, using DeleteLicenseDB.txt and InsertLicenseDB.txt, as follows:

  1. Place the new license file in the same folder as the old license file, typically C:\LogiAnalytics\Discovery.
  2. Download and save the two files above to your desktop.
  3. Edit each file to include the correct Discovery Admin password, license file name, and license file path (if not the default). Note that, when editing DeleteLicenseDB.txt, you specify only the license file name, without its extension. For example, to delete the standard trial license, you specify "license-id=logiTrial03" (no quotes).
  4. Rename the downloaded file extensions to ".bat".
  5. Using Run As Administrator, execute the DeleteLicenseDB.bat file and allow it to fully complete.
  6. Using Run As Administrator, execute the InsertLicenseDB.bat file and allow it to fully complete.


LINUX/UNIX:

  1. Place the new license file in the same folder as the old license file, typically C:\LogiAnalytics\Discovery.
  2. Download and save the two files above to your desktop.
  3. Manually stop the Logi Application Server and Logi Data Service daemons.
  4. Manually run C:\LogiAnalytics\Discovery\platform\bin\licenseTool.sh, editing and using the arguments found in the DeleteLicenseDB file.
  5. Manually run licenseTool.sh again, editing and using the arguments found in the InsertLicenseDB file.
  6. Manually start the Logi Data Service daemon.
  7. Wait 10 seconds, manually start the Logi Application Server daemon

Information about this process is logged to: C:\LogiAnalytics\Discovery\platform\logs\licenseImport.log
 

  Back to top

 

Server Virtualization

Many organizations are using server virtualization to maximize hardware usage and reduce costs.

Server virtualization products allow the assignment of CPU resources to processes. This may take the form of a maximum percentage of combined CPU utilization, or as specific allocation of logical CPUs, to a virtual machine (VM). The server administrator is responsible for making these configuration decisions.

Logi v12 product licenses treat a VM just like a regular server and run just fine in this environment.

In order to ensure good performance in any virtualized server environment, administrators must be careful to allocate appropriate resources to VMs.

It's not uncommon to relocate a VM from one hardware platform to another, for example, for hardware maintenance. The Logi license will "move" with the VM, as long as its machine name doesn't change.

  Back to top

 


© Copyright 2007-2018 Logi Analytics, Inc. All Rights Reserved