Getting Started with License Filebased. FLEXnet Publisher Licensing Toolkit 11.5 P/N: FNP-115-GSLF01

Transcription

1 Getting Started with License Filebased Licensing FLEXnet Publisher Licensing Toolkit 11.5 P/N: FNP-115-GSLF01

2 Legal and Contact Information Part Number: P/N: FNP-115-GSLF01 Product Release Date: December 2007 Contacting Macrovision Macrovision Corporation 2830 De La Cruz Blvd. Santa Clara, CA Tel: (408) Fax: (408) For general information, technical support, the Macrovision knowledgebase, or to learn about consulting and training services, visit For the Macrovision Online Community, visit To access the RightAccess and RightCommerce Documentation Center, visit To access Installshield, Admin Studio, FLEXnet Connect, Update Service, or Install Anywhere documentation, visit Copyright Notice Copyright 2007 Macrovision Corporation and/or Macrovision Europe Ltd. All Rights Reserved. This product contains proprietary and confidential technology, information and creative works owned by Macrovision Corporation and its subsidiaries and their respective licensors. Any use, copying, publication, distribution, display, modification, or transmission of such technology in whole or in part in any form or by any means without the prior express written permission of Macrovision Europe Ltd. and Macrovision Corporation is strictly prohibited. Except where expressly provided by Macrovision Europe Ltd. and Macrovision Corporation in writing, possession of this technology shall not be construed to confer any license or rights under any of Macrovision Europe Ltd. and Macrovision Corporation s intellectual property rights, whether by estoppel, implication, or otherwise. ALL COPIES OF THE TECHNOLOGY and RELATED INFORMATION, IF ALLOWED BY MACROVISION CORPORATION, MUST DISPLAY THIS NOTICE OF COPYRIGHT AND OWNERSHIP IN FULL. This product incorporates software developed by others and redistributed according to license agreements. Copyright notices and licenses for these external libraries are provided in a supplementary document that accompanies this one. Trademarks Macrovision, AdminStudio, DemoNow, DemoShield, FLEXenabled, FLEXlm, FLEXnet, FLEXnet Certified, FLEXnet Connector, FLEXnet Manager, FLEXnet Publisher, Globetrotter, Hawkeye, InstallFromTheWeb, InstallShield, InstallShield Developer, InstallShield DevStudio, InstallShield Professional, It All Starts Here, OneClickInstall, Package For The Web, QuickPatch, ReadySell, RipGuard, SafeCast, Trymedia Systems, and Zero G Software are registered trademarks or trademarks of Macrovision Corporation in the United States of America and/or other countries. All other brand and product names mentioned herein are the trademarks and registered trademarks of their respective owners. Restricted Rights Legend The software and documentation are commercial items, as that term is defined at 48 C.F.R , consisting of commercial computer software and commercial computer software documentation, as such terms are used in 48 C.F.R or 48 C.F.R , as applicable. Consistent with 48 C.F.R or 48 C.F.R through , as applicable, the commercial computer software and commercial computer software documentation are being licensed to U.S. government end users (A) only as commercial items and (B) with only those rights as are granted to all other end users pursuant to the terms and conditions set forth in the Macrovision Corporation standard commercial agreement for this software. Unpublished rights reserved under the copyright laws of the United States of America.

3 Contents Legal and Contact Information Introduction to this Document What s New in this Document FLEXnet Publisher Licensing Toolkit Product Documentation Introduction to Licensing-File Based Licensing The FLEXnet Licensing Ecosystem FLEXnet Licensing Components License Model Overview Component Descriptions The License Request Process Evaluating FLEXnet Publisher Licensing Toolkit on Windows Identifying the Build Directories Evaluating the End-User Experience Unserved License Model Uncounted License File Using an Uncounted License File Served License Model Counted License File Configuring the Demo License Server as a Windows Service Starting the Demo License Server (using LMTOOLS) Checking the Status of the Demo License Server System Using a Served License Attempting to Checkout an Unlicensed Feature Stopping the Demo License Server (using LMTOOLS) Evaluating the Vendor Experience FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 3

4 Contents Licensing a Feature Editing the License File Re-signing the License File A Locked, Uncounted License Creating a Locked, Uncounted License Testing the License Security Considerations An Expiring License Building the FLEXnet Publisher Licensing Toolkit Setting Up the C Development Environment Configuring the FLEXnet Publisher Licensing Toolkit Changing TRL Strength Building the FLEXnet Publisher Licensing Toolkit Toolkit Resigning the Sample License File Conclusion Evaluating FLEXnet Publisher Licensing Toolkit on UNIX Identifying the Build Directories Evaluating the End-User Experience Viewing the Sample License Files Starting the Demo License Server System Checking the License Server System Status Running the Sample FLEXenabled Application Trying to Check Out an Unlicensed Feature Stopping the Demo License Server System Testing an Uncounted License Evaluating the Vendor Experience Licensing a Feature Editing the License File Re-signing the License File A Locked, Uncounted License Creating a Locked, Uncounted License Testing the License Security Considerations An Expiring License Building the FLEXnet Publisher Licensing Toolkit Configuring the FLEXnet Publisher Licensing Toolkit Changing TRL Strength Building the FLEXnet Publisher Licensing Toolkit Re-signing the Sample License File Conclusion License Models Basic License Models FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

5 Contents Node-locked/Uncounted Models Evaluation License Model Node-locked/Counted Models Floating Models License Model Modifiers Required License Model Modifiers Expiration Date Version Optional License Model Modifiers Usage-Based Licensing Mobile Licensing Deciding the Need for a License Server System Vendor Decisions Summary of Vendor Decisions Core Decisions Determining Licensable Product Configurations Hostid Support Checkout Failure Behavior Checkin Considerations Optional Diagnostic Handling License Server System Decisions Maintaining Consistency with the License Server System Connection/Reconnection Strategy Heartbeat Implementation Strategy License Sharing Checkin Considerations for Served Licenses License Server System Redundancy License Security Systems Overview Limiting Exposure Server-Side Exposure Product-Side Exposure License Signature Encryption Method Expiring Licenses Date Tampering HOSTID Choices Building the Product: Dynamic vs. Static Linking Tracking End-User Usage Usage Data Limitations License Fulfillment FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 5

6 Contents License Fulfillment Automated Fulfillment Other Methods Strategy for Delivering Rights Over Time Upgrading Incrementing Superseding Support Entitlement Transferring Rights - License Rehosting Evaluation Licensing Strategy Limited Time Demos Limited Functionality Demos Case Study Background FLEXnet Publisher Licensing Toolkit Use Case License Policy Definition Basic License Model License Model Modifiers Usage-Based Licensing Mobile Licensing License Server System Requirement Vendor Decisions Licensable Product Configurations Hostid Support Checkout Failure Behavior Checkin Considerations License Server System Consistency License Sharing Licensing Security License Fulfillment Usage Rights over Time License Rehosting Evaluation Licensing Strategy License File Location Sample License Certificates Evaluation Product Configuration Certificate Standard Product Configuration Certificate Updating the License Certificate Product Deliverables Glossary FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

7 Contents Index FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 7

8 Contents 8 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

9 Introduction to this Document This manual, FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing, describes the basic concepts of FLEXnet Licensing, license models, and concepts for designing license policies using License Files. To obtain a complete overview of the FLEXnet Publisher Licensing Toolkit capabilities, read this document and the companion document, Getting Started with Trusted Storage-based Licensing. This document contains the following chapters: Table -1: FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing Chapter Overview Topic Introduction to this Document Chapter 1, Introduction to Licensing-File Based Licensing Chapter 2, Evaluating FLEXnet Publisher Licensing Toolkit on Windows Chapter 3, Evaluating FLEXnet Publisher Licensing Toolkit on UNIX Chapter 4, License Models Chapter 5, Vendor Decisions Chapter 6, License Security Systems Content Provides an overview of the FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing, including Help Library conventions and usage. This chapter provides a general overview of FLEXnet Licensing using license rights held in license files. This chapter walks you though the process of evaluating FLEXnet Licensing behavior on Windows, both from the end-user s and the vendor s perspective. This chapter walks you though the process of evaluating FLEXnet Licensing behavior on UNIX, both from the end-user s and the vendor s perspective Gives a brief overview of FLEXnet Licensing and the basic steps for creating a license model. This chapter presents licensing policy concepts that you need to think about when designing a licensing policy for your product. Discusses license security, including issues and strategy for implementation. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 9

10 Chapter : Introduction to this Document What s New in this Document Table -1: FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing Chapter Overview Topic Chapter 7, License Fulfillment Chapter 8, Case Study Content Provides an overview of license fulfillment and installation at the end-user site. Presents a case study based on products and business strategies of a fictitious company, giving users insight into realistic FLEXnet Licensing scenarios. What s New in this Document The following chapters that were removed from version 11.4 of this document have been added back in: Chapter 2, Evaluating FLEXnet Publisher Licensing Toolkit on Windows Chapter 3, Evaluating FLEXnet Publisher Licensing Toolkit on UNIX The Windows FLEXnet Publisher Licensing Toolkit 11.5 requires a different installation procedure. Some instructions in Chapter 2, Evaluating FLEXnet Publisher Licensing Toolkit on Windows have been rewritten. FLEXnet Publisher Licensing Toolkit Product Documentation The following documents provide information about the FLEXnet Publisher Licensing Toolkit: Release Notes communicates information about changes to the application and supported thirdparty applications. Installation Guide describes how to install the Licensing toolkit. Getting Started with Trusted Storage-based Licensing is an introduction to FLEXnet Licensing using Trusted Storage. It includes step-by-step instructions for using example files provided within Licensing toolkits. These demonstrate how FLEXnet Licensing can be used to provide various licensing models. Getting Started with License File-based Licensing contains information for those software vendors new to FLEXnet Licensing using license file-based licensing. It includes an evaluation procedure that introduces these licensing concepts from both the software publisher and end-user s perspective. License File-based Programming Reference contains information about license file-base licensing. Certain information is relevant to both license file-based and trusted storage-based licensing. You should read this document and Getting Started with License File-based Licensing to understand the basic concepts of FLEXnet Licensing if you have not previously used it. Trusted Storage-based Programming Reference contains information licensing using Trusted Storage. If you have not previously used this capability, you should also read Getting Started with Trusted Storage-based Licensing to understand the basic concepts of FLEXnet Licensing using Trusted Storage. 10 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

11 Chapter : Introduction to this Document FLEXnet Publisher Licensing Toolkit Product Documentation Licensing for Java Programming Reference Guide contains guidelines for using the FLEXnet Publisher Licensing Toolkit for Java. License Administration Guide contains information the setup and administration of a licensing system, including setting up an options file and using Licensing utilities. Creating a Licensed Product: Setting up and Using the Development and Build Environment describes how to integrate the toolkit into the development environment, build a production licensing toolkit, and distribute a FLEXenabled application. C/C++ Function Reference summarizes and describes all publicly available C/C++ functions in the Licensing toolkit. Licensing for Java API Reference summarizes and describes all publicly available Java classes and methods in the Licensing for Java toolkit. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 11

12 Chapter : Introduction to this Document FLEXnet Publisher Licensing Toolkit Product Documentation 12 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

13 1 Introduction to Licensing-File Based Licensing FLEXnet Publisher Licensing Toolkit is a product licensing package that allows licensing a product on a per-computer basis (node-locked) as well as on a concurrent-usage basis (floating). FLEXnet Licensing using license files allows for the implementation of a wide variety of functionality within the licensing policy. General FLEXnet Licensing features include: A wide variety of licensing policy functionality and license styles, including, but not limited to: Node-locked licenses Demo licenses Personal-use licenses Floating licenses Counted and uncounted licenses Expiring licenses Administration tools for end-user license administrators Support for independent features from one or multiple vendors Several vendor-definable fields for each product feature Operation in a heterogeneous network of supported computer systems Transparent reconnection of the FLEXenabled product when its license server system becomes unavailable, including conditions of license server machine failure Simple configuration by using a single license file per network Configuration controls for system administrators FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 13

14 Chapter 1: Introduction to Licensing-File Based Licensing The FLEXnet Licensing Ecosystem The FLEXnet Licensing Ecosystem The FLEXnet Licensing ecosystem consists of: You, the vendor. You develop the license policy and enable your product with FLEXnet Publisher Licensing Toolkit. The end user. This is your customer to whom you deploy your FLEXenabled product and all related components. The FLEXnet Publisher Licensing Toolkit. The Licensing toolkit resides on a development machine at your site. You use it to integrate FLEXnet Licensing, via a client-side library, into your product, to generate license certificates, and to make customizations to the license server system. The FLEXnet Licensing components. This is your FLEXenabled product, in conjunction with the license certificate and other license model components, that you deploy at your end-user s site. FLEXnet Licensing Components This section presents: License Model Overview The FLEXnet Licensing components necessary for both unserved and served license models are presented. Component Descriptions A description of each license model component and the role it plays in your licensing policy. License Model Overview A major distinguishing characteristic of a license model is its requirements for a license server system. The need for a license server system stems from either a FLEXnet Publisher Licensing Toolkit requirement, your requirement, your end-user s requirement, or a combination of the three. The section titled Deciding the Need for a License Server System explores the requirements for license server systems in more depth. The Unserved License Model A license model that does not need a license server system has two components: The FLEXenabled Product A License Certificate Examples of this type of licence model include: expiring evaluation licenses; site licenses available to an unlimited number of users; and single-use, node-locked licenses. 14 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

15 Chapter 1: Introduction to Licensing-File Based Licensing FLEXnet Licensing Components Figure 1-1 shows this model. Each component is described in subsequent sections. FLEXenabled Product Your Product Code Licensing toolkit Client Library License Certificate Figure 1-1: FLEXnet Licensing Unserved License Model Components Implementing your licensing policy for unserved licenses requires you to: Instrument your product with calls to the FLEXnet Publisher Licensing Toolkit client library Create a license certificate with keywords appropriate to your license model For an unserved license, the FLEXenabled product and license certificate reside on the same machine. The Served License Model For served licenses, there are four required FLEXnet Licensing components: The FLEXenabled Product The FLEXnet License Server Manager daemon, lmgrd The Vendor Daemon, which, along with the license server manager, comprises the license server system A License Certificate In addition to the four required components, there are three optional components: Debug Log File End-User Administration Options File Report Log File Served licenses allow a fixed number of concurrent users access to your application at any one time. The server keeps track of the number of concurrent users. The licenses are not node-locked to a specific machine, but rather, float on the network, allowing network wide usage. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 15

16 Chapter 1: Introduction to Licensing-File Based Licensing FLEXnet Licensing Components Figure 1-2 shows the relationship these components have to one another. Each component is described in subsequent sections. FLEXenabled Product Your Product Code Licensing toolkit Client Library TCP/IP Port License Server System Components License Server FLEXnet Licensing License Server Manager Vendor Daemon License Certificate Debug Log File Administration Options File Report Log File Figure 1-2: FLEXnet Licensing Served License Model Components Implementing your licensing policy for served licenses requires you to: Instrument your product with calls to the FLEXnet Publisher Licensing Toolkit client library Configure a vendor daemon Create a license certificate with keywords appropriate to your license model The license server system components can reside on the same machine as the FLEXenabled product; but typically, they reside on a machine in the network and communicate with the product via a TCP/IP port. The end user enables the Debug and Report logs, and configures the FLEXnet Publisher Licensing Toolkit end-user Administration Options file. Component Descriptions The FLEXenabled Product The FLEXenabled product is your product instrumented with calls to the FLEXnet Publisher Licensing Toolkit client library. The Licensing toolkit client library provides routines that establish the productside licensing policy, read the license file, and, in the case of served licenses, provide communication with the license server system. This ultimately results in granting or denying usage. License Certificate The license certificate is created by the product vendor. It is installed as a license file by the end-user license administrator or can be installed automatically as part of the product installation process. It contains at least one line of data (called a FEATURE or INCREMENT line) for each FLEXenabled product configuration. Each FEATURE line contains a license key or signature based on the data in that line. 16 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

17 Chapter 1: Introduction to Licensing-File Based Licensing FLEXnet Licensing Components For a served license model, information about the license server machines, their hostids, and vendor daemons are specified with SERVER and VENDOR lines. A FLEXenabled product implementing an unserved license model need only read a valid license file to run it does not need a license server system. The FLEXnet License Server Manager The FLEXnet license server manager, lmgrd, handles the initial contact with the FLEXenabled product, passing the connection on to the appropriate vendor daemon. It also starts and restarts the vendor daemon. The Vendor Daemon In FLEXnet Licensing, served licenses are granted by processes running on the license server machine. There is one process specific for each vendor who has a FLEXenabled product on the network. This process is called the vendor daemon. The vendor daemon keeps track of how many of its licenses are checked out, and who has them. A FLEXenabled product communicates with a vendor daemon, usually through TCP/IP network communications. The FLEXenabled product and the daemon processes (the license server system) can run on separate machines on your network, across any size wide-area network. Also, the format of the traffic between the FLEXenabled product and the vendor daemon is machine independent, allowing for heterogeneous networks. This means the license server system and the computer running a product can be either different hardware platforms or even different operating systems (Windows and UNIX, for example). Debug Log File A debug log file contains status and error messages useful for debugging the license server system. Some of the debug log output describes events specific to lmgrd and some of the debug log output describes events specific to a vendor daemon. End-User Administration Options File The options file allows the end-user license administrator to control various operating parameters of FLEXnet Licensing within the limits of the product s licensing policy. Specifically, the license administrator can: Administer named-user and named-host licenses: Allowing features to be used by specific users/hosts/groups Denying feature use to specific users/hosts/groups Reserve licenses for specific users/hosts/groups Restrict the number of licenses available Control the amount of information logged about license usage Enable a report log file FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 17

18 Chapter 1: Introduction to Licensing-File Based Licensing FLEXnet Licensing Components Report Log File The report log file contains feature usage information and is generated by the vendor daemon. Report log output is encrypted and is utilized by reporting products such as FLEXnet Manager. The License Request Process Served License Model When the FLEXenabled application runs in the context of a served license model, the following occurs: 1. The license module in the FLEXenabled application finds the license file, which includes the host name of the license server machine and TCP/IP port number of the license server manager, lmgrd. 2. The FLEXenabled application establishes a connection with the license server manager (lmgrd) and tells it what vendor daemon it needs to talk to. 3. lmgrd determines which machine and TCP/IP port correspond to the master vendor daemon and sends that information back to the FLEXenabled application. 4. The FLEXenabled application establishes a connection with the specified vendor daemon and sends its request for a license. 5. The vendor daemon checks in its memory to see if any licenses are available and sends a grant or denial back to the FLEXenabled application. 6. The FLEXnet Publisher Licensing Toolkit client library routines in the application grants or denies use of the feature, as appropriate. Unserved License Model Unserved license models depend solely on the Licensing toolkit client library routines in the application to grant or deny usage based solely upon the contents of the license file. 18 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

19 2 Evaluating FLEXnet Publisher Licensing Toolkit on Windows This chapter walks you though the process of evaluating FLEXnet Licensing behavior using license files on Windows, both from the end-user s and the vendor s perspective. Before you start this chapter, please install the FLEXnet Publisher Licensing Toolkit as described in the instructions in the Installation Guide. The Licensing toolkit contains these pre-built files used to evaluate FLEXnet Licensing: Sample license files (counted.lic, expired.lic, and uncounted.lic) Sample vendor daemon (demo.exe) Toolkit Test Program, a sample FLEXenabled application (lmflex.exe) License generation utility (lmcrypt.exe) FLEXnet Publisher Licensing Toolkit utilities (lmtools.exe) DEMO license server system The demo vendor keys provided to you by Macrovision are used later in this chapter. If your demo vendor keys expire before you complete this evaluation, contact your salesperson at Macrovision. Note: Microsoft Visual C++ version 6.0 or.net is required for part of this evaluation. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 19

20 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Identifying the Build Directories Identifying the Build Directories The procedures in this chapter assume you have installed the Licensing toolkit. Table 2-1 lists the directories that are involved in the evaluation exercises along with their shortcuts. Take a few moments to identify the location of each shortcut for your particular installation before proceeding: the shortcuts are used throughout this chapter. Table 2-1: Toolkit Directories Shortcut Name install_dir platform machind Default Location No default, you define this path at installation time. <install_dir>\<platform_identity> An example of a <platform_identity> is i86_n3 <install_dir>\machind Now you are ready to begin your evaluation of FLEXnet Licensing. All operations take place in the platform directory unless otherwise noted. Evaluating the End-User Experience The evaluation steps in this section take you through different actions that an end user or license administrator at your end-user s site may take. Typical scenarios are demonstrated in the following sections: Using an Uncounted License File Configuring the Demo License Server as a Windows Service Starting the Demo License Server (using LMTOOLS) Checking the Status of the Demo License Server System Using a Served License Attempting to Checkout an Unlicensed Feature Stopping the Demo License Server (using LMTOOLS) All components required to perform the steps in this section are prebuilt and have been placed on your system during installation. Unserved License Model This demonstration of the unserved license model uses two example components provided in the toolkit in install_dir\platform : The sample Licensing toolkit Test Program - lmflex.exe 20 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

21 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the End-User Experience A sample uncounted license file - uncounted.lic Uncounted License File Open the sample uncounted license file, install_dir\platform\uncounted.lic, in a text editor. You see something like this output: # an uncounted license FEATURE f2 demo permanent uncounted HOSTID=ANY \ SIGN=" C50 609D 13F4 353F 4866 A D \ 05F9 2D83 2B0C A15F" This license is for feature f2. It is licensed to the vendor demo. It is a permanent license, that is it will not expire. It is uncounted and therefore it does not need a license server system. It is valid on any machine as HOSTID=ANY. The following figure shows where these items are located in the license file. Figure 2-1: Uncounted License File Using an Uncounted License File Follow the steps below to start the Test Program, install_dir\platform\lmflex.exe, and use it to check out a license for the feature f2 from the uncounted.lic license file. Task To check out a license for feature f2: 1. Open a command window and change to the platform folder. In this window, type lmflex. You see: Enter "f1" to demo floating functionality Enter "f2" to node-locked functionality Enter feature to checkout [default: "f1"]: 2. Type f2 and press Enter to check out a license for feature f2. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 21

22 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the End-User Experience 3. If you have not used the licensing toolkit on this machine before, the following dialog is displayed: Use the FLEXnet License Finder dialog to specify the uncounted.lic license file as follows: a. Click Specify the License File and click Next. b. Type uncounted.lic and click Next. c. Click Finish. 4. The following message is displayed, confirming that a license for feature f2 has been checked out: f2 checked out...press return to exit Press Enter to check the f1 license back in and exit lmflex. Note that step 3 is required because lmflex does not specify the location of the license file, but instead relies on a license server system searching for license files in its local directory. When a license file has been used to successfully checkout a license, the path to the license file is stored in the registry. This path will be used subsequently when searching for a license. Served License Model This demonstration of the served license model uses the following components provided in the toolkit: The sample Licensing toolkit Test Program - install_dir\platform\lmflex.exe A sample counted license file - install_dir\platform\counted.lic DEMO license server system - demo.exe and lmgrd Tool for managing license server systems - LMTOOLS Macrovision provides tools for managing license server systems that you can distribute to your customers. On Windows, Macrovision provides lmutil.exe, a set of command-line utilities, and LMTOOLS, a similar set of utilities with a graphical user interface which is used in this demonstration. 22 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

23 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the End-User Experience Counted License File Open the sample counted license file, install_dir\platform\counted.lic, in a text editor. You see something like this output: SERVER this_host ANY VENDOR demo FEATURE f1 demo 1.0 permanent 4 SIGN="AADD B062 54D1 47E3 \ 1FF6 145F 59CE FE69 0FBC 0000 AA10 FFB3 6EB3" This sample license file is valid on any machine (because on the SERVER line the server hostid is ANY ). It contains one FEATURE line for f1 that has a license count of 4 and is served by the vendor daemon demo. The following diagram shows where these items are located on the FEATURE line. Figure 2-2: Counted FEATURE line Configuring the Demo License Server as a Windows Service The machine on which the license server system is installed is normally set up so that the license server system is run as a service and automatically started when the machine is started. This section gives instructions on how to configure the demo license server system as a service using the toolkit utility LMTOOLS. To configure a license server system as a service, you must have Administrator privileges. Task To configure the demo license server system as a service: 1. From the platform directory double-click lmtools.exe. This runs LMTOOLS. 2. Click the Configuration using Services button, and then click the Config Services tab. 3. In the Service Name, type the name of the service. It is recommended that you choose a service name that includes the toolkit version, for example 11.4 DEMO License Manager. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 23

24 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the End-User Experience 4. In the Path to the lmgrd.exe file field, enter or browse to the lmgrd.exe provided in this toolkit. 5. In the Path to the license file field, enter or browse to the license file that is used to start up this license server system. Ensure that you choose a license file that was generated for use with the Demo vendor daemon, for example counted.lic from the toolkit platform directory. 6. In the Path to the debug log file, enter or browse to the debug log file that this license server system writes. Prepending the debug log file name with the + character appends logging entries. The default location for the debug log file is the c:\winnt\system32 folder. To specify a different location, make sure you specify a fully qualified path. 7. Check Use Services. Figure 2-3: Completed example LM_TOOLS Config Services screen 8. To save the service, click Save Service. Note that for this evaluation the demo license server system is started manually. Normally a license server system is set to start automatically when the machine is switched on. To configure this, at step 7 check Use Services and Start Server at Power Up. Starting the Demo License Server (using LMTOOLS) Task To start the demo license server using LMTOOLS: 1. From the platform directory double-click lmtools.exe. 2. Click the Start/Stop/Reread tab. 24 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

25 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the End-User Experience 3. Select the demo license server service name (see step 3 in Configuring the Demo License Server as a Windows Service). 4. Click Start Server. Checking the Status of the Demo License Server System Use LMTOOLS to check the status of the demo license server system and determine: Whether it is running Number of licenses issued Number of licenses in use Users of each FLEXenabled feature Task To check the license server system status: 1. In LMTOOLS, click the Server Status tab. 2. Click Perform Status Enquiry. 3. Scroll down the display; you should see output similar to that shown below: demo: UP v11.4 Feature usage info: Users of f1: (Total of 4 licenses issued; Total of 0 licenses in use) FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 25

26 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the End-User Experience Note that no users have any of the licenses for f1 checked out. Using a Served License Follow the steps below to start the Test Program, lmflex.exe, and use it to check out a license for the feature f1 from the counted.lic license file. To complete this section you must have completed the previous sections and the demo license server system must be running. Task To demonstrate the use of a served license: 1. Open a command window and change to the platform folder. In the this window, type lmflex. You see: Enter "f1" to demo floating functionality Enter "f2" to node-locked functionality Enter feature to checkout [default: "f1"]: 2. Press Enter to check out a license for feature f1. The following confirmation message is displayed: f1 checked out...press return to exit To check the status of the license server system with a license checked out, in the Server Status pane of LMTOOLS, click Perform Status Enquiry. Scroll down to see output with user, host, and display information about the f1 license that you just checked out: demo: UP v11.4 Feature usage info: Users of f1: (Total of 4 licenses issued; Total of 1 license in use) "f1" v1.0, vendor: demo floating license daniel myhost myhost (v1.0) (myhost/ ), start View the tail of the debug log file, platform\demo.dl, by clicking the Config Services tab and clicking the View Log button. A viewer opens and you should see something like: 19:03:54 (demo) OUT:"f1" daniel@myhost 5. In the Config Services tab, click the Close Log button to close the debug log viewer. 6. In the command window, press Enter to check the f1 license back in and exit lmflex. 7. Use LMTOOLS t0 check the server status again to see that now no licenses are checked out. Attempting to Checkout an Unlicensed Feature 1. Run lmflex again, and instead of selecting the default feature f1 for which you have a license, type f3 as the feature to check out. 2. An error dialog appears telling you that the feature does not exist. Click OK in the dialog. 26 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing

27 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the Vendor Experience Stopping the Demo License Server (using LMTOOLS) 1. In the Start Stop Reread tab of LMTOOLS, click Stop Server. 2. Check the license server system status now that you have stopped the DEMO license server system. You see: lmgrd is not running: Cannot connect to license server The server (lmgrd) has not been started yet, or the wrong or license file is being used, or the port or hostname in the license file has been changed. 3. Look at the license server system debug log file at platform\lmgrd.dl to review the activity of the DEMO license server system. Evaluating the Vendor Experience This section of the evaluation demonstrates some of the activities you perform in the course of implementing your license policy. The versatility of FLEXnet Licensing s policy in the license is showcased in the following subsections: Licensing a Feature A Locked, Uncounted License An Expiring License Building the FLEXnet Publisher Licensing Toolkit Now, proceed to the next sections for a demonstration of FLEXnet Licensing s policy in the license technology. Licensing a Feature Editing the License File In order to give yourself a license for feature f3, the sample license file must be edited. Follow the steps below to edit the license by replacing the feature to be licensed. Task To edit the sample license file: 1. Open install_dir\platform\counted.lic in a text editor. 2. Duplicate the f1 FEATURE line at the bottom of the file. 3. On the second f1 FEATURE line, replace f1 with f3. 4. Save and close counted.lic. 5. Click the Start Stop Reread tab in LMTOOLS. Select DEMO License Manager and click the Start Server button. This starts the license server system and forces the edited license file to be read. Wait a few seconds for the server to start. FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing FNP-115-GSLF01 27

28 Chapter 2: Evaluating FLEXnet Publisher Licensing Toolkit on Windows Evaluating the Vendor Experience 6. Start lmflex and try to check out f3 again. 7. You see an error dialog indicating you cannot check out the license. You added an f3 FEATURE line in the license file by copying it from f1 and simply changing the feature name. However, the signature is still authenticated for feature f1 at that point. In the next section, you re-sign the certificate so it is authenticated for f3. Click OK in the error dialog. Re-signing the License File In the last section, you saw that it is not possible to simply edit the license file, as an end user may try to do, to create a FEATURE line for f3. Now, generate a license file with valid FEATURE lines for both f1 and f3 with lmcrypt. Task To re-sign the license file: 1. Open a command-line window and change to the platform folder. In this window, type lmcrypt counted.lic. The license file should now resemble that shown below: SERVER this_host ANY VENDOR demo FEATURE f1 demo 1.0 permanent 4 SIGN="AADD B062 54D1 47E3 \ 1FF6 145F 59CE FE69 0FBC 0000 AA10 FFB3 6EB3" FEATURE f3 demo 1.0 permanent 4 SIGN="CDFE \ AD DEFE 8FDD 0000 ADDE FFB3 3545" 2. Click the Start Stop Reread tab in LMTOOLS. Click the ReRead License File button to tell the license server system to reread its edited license file. 3. Run lmflex again and try to check out f3. Now that you have a valid license for f3, you are able to check out a license for it. 4. When you are finished experimenting in the Start Stop Reread pane of LMTOOLS, click the Stop Server button. 5. Exit lmflex. A Locked, Uncounted License This section takes you through the process of locking a license to a specific machine simply by regenerating the FEATURE line within the license file, which incorporates the HOSTID into the license signature. There is no need to modify either the Licensing toolkit or application to incorporate this license policy. The steps below demonstrate how to node-lock the license for feature f2 to your specific machine. 28 FNP-115-GSLF01 FLEXnet Publisher Licensing Toolkit 11.5: Getting Started with License File-based Licensing