License Management Software

Creo View Installation and Configuration Guide > License Management Software

This chapter discusses license management software and describes the benefits of PTC License Server. License simplification is explained for new and existing users.

Overview of PTC Licensing

PTC software including PTC optional applications must be licensed for use. Licensing authorizes the installed software to run. Creo View licenses are not time-sensitive.

License Types

Depending on the PTC product, a license can be one of the following types.

• Node-locked licenses—Restricts the use of the software to a particular machine (independent workstation).

• Floating licenses—Served by the license server and can be used on any machine connected over the network. There are two different types of floating licenses:

◦ Single server licenses—Configured for a single machine as the server.

◦ Triad licenses—Configured for a set of three machines on the same network that work together to manage a pool of floating licenses. This configuration provides redundant backup in case of a server outage. An identical license file is used for each Triad partner.

• Extended license—An extended license makes floating licenses available for locked modules.

• Borrowed license—A borrowed license allows you to work temporarily on your machine without being connected to the license server. Refer to Obtaining and Configuring Licenses for details.

For more information on the additional license types that are supported for your product, refer to the product documentation.

PTC License Server

Flexera Software, Inc.’s FlexNet Publisher license management software is integrated with PTC software. For more information, visit www.flexerasoftware.com.

Benefits of Using FlexNet Publisher

Using FlexNet Publisher to control usage of licenses offers the following key advantages:

• Single-Server Solution—FlexNet Publisher can manage PTC software and other vendor applications without conflict. Note that the PTC license file cannot be combined with the license files of other vendors.

• Immediate License Recovery—If there is a premature exit of the licensed software (for example, the system shuts down), the FlexNet Publisher license server automatically reclaims the PTC license.

• Increased Flexibility—System administrators can reserve or deny licenses based on user name, host name, display name, or IP address. For more information see Managing the Options File in the FlexNet Publisher License Administration Guide.

• Centralized License Storage—PTC customers can store all PTC licenses for all PTC products in a single file for each license server.

• Multiple Licenses for a Single Command—One command can be used to execute multiple licenses of PTC software based on availability.

• License Borrowing—Using FlexNet Publisher 8.6 or later, you can borrow licenses from a license server and run a licensed application on a remote client without being connected to the license server.

Downward License Compatibility Using FlexNet Publisher

FlexNet Publisher license servers have downward compatibility with PTC applications using FLEXlm license servers. For example, a Creo View 2.0 license can run ProductView 9.1 software, because both releases of the software use the same PTC License Server.

To run the current release of Creo View, you must install FlexNet Publisher version 11.x or later.

Running FlexNet Publisher with Other Applications

You can use FlexNet Publisher to run PTC products as well as other applications. Each application that uses FLEXlm or FlexNet Publisher has a corresponding license server manager (lmgrd or lmadmin) and a vendor daemon. The license server manager starts the vendor daemon (for example, ptc_d) that controls the usage of licenses.

You cannot combine a PTC license file with a license file of another vendor. Do not, for example, combine PTC feature lines with those of other vendors in a single license file. This action causes the licenses to be invalid.

If all applications and vendor daemons are FLEXlm 6.1 or later, lmgrd or lmadmin can process multiple license files. This is true even when the Host IDs are different (as long as the license files refer to the same node). For more information, see Managing Licenses from Multiple Software Publishers in the FlexNet Publisher License Administration Guide.

Understanding Timeout Parameters

Timeout parameters enable the license client and the license server to communicate with one another so that licenses are released and available upon request.

You can reconfigure the TIMEOUTALL parameter within a specified range, as described in the next section, Changing the Inactivity Timeout Parameter.

Timeout Parameter	Value	Description
Inactivity timeout (TIMEOUTALL)	120 minutes (default)	This parameter prevents a license from remaining idle. If the license client is inactive for a specific period, the license can be reclaimed by the license server and used by another license client. For the Creo applications, the inactivity timeout default is 120 minutes. Activity is measured as active menu selections. You can change the default of 120 minutes so that the parameter ranges from 20 minutes (minimum value) to infinity (maximum value).
License refresh	1 minute	A license refresh occurs at intervals of 1 minute. When you select a command after such an interval, the license client communicates with the license server. The license client and the license server both must be working. If the license server is not found, the license client loses its license to run. If the license client is not found, the server reclaims the license for use by another license client.
Validation retries	None	The first time a license client cannot validate its license the application's graphical user interface will freeze. You are immediately given the following three options: Click Retry to request a license from an active license server. Click Save File(s). Click Exit to close the application without saving the file or files.
Startup	10 seconds	Upon starting a session, the license client requests a license and has 10 seconds in which to have the request validated.

Changing the Inactivity Timeout Parameter

You can set the TIMEOUTALL parameter that determines how long the system allows a license to remain idle before it is reclaimed by the license server. To change the default inactivity timeout parameter, you must update the FlexNet Publisher option file, ptc.opt in <ptc License Server loadpoint>/FLEXnet Publisher/licensing. The default is 120 minutes. Edit the default parameter:

TIMEOUTALL 7200

Change 7200 seconds (120 minutes) to another value in seconds.

The minimum value is 20 minutes (or 1200 seconds) and the maximum value is infinity. To make infinity the default, remove the TIMEOUTALL parameter from the ptc.opt file. If you set a minimum value to less than 20 minutes, the system defaults to 20 minutes.