Chapter 7
License Codes
This Chapter explains the structure and usage of the FLEXlm licensing file (license.dat) in PTC's implementation and the delivery of codes in the new License Pack format. License Packs Your license codes are given to you in a License Pack. The license pack contains a customer information section and a license information section. The license information section contains "feature lines" that define your PTC licenses and floating options.

For floating licenses, the license information section also contains "SERVER" and "DAEMON" lines.

If you obtained your License Pack by e-mail or through the www, you can save the License Pack to a file. The file can be imported directly into Pro/SETUP. This eliminates the task of manually entering your license information. This technique is highly recommended.

If you cannot obtain an on-line copy of your License Pack, your license information will need to be entered into Pro/SETUP manually.

Your license file contains all the license information (multiple feature lines) for all Configuration IDs assigned to a particular CPU. That is, all licenses for all PTC products licensed to a single machine can be defined in a single license file.

Example: A configuration of Pro/ENGINEER, Pro/FLY-THROUGH, and a license of Pro/MECHANICA are all licensed to a single license server. PTC can provide license information for all products on a single License Pack. If an on-line copy of this file is obtained, the single file can be used during the installation of all three products and needs to be imported into Pro/SETUP only once.

Server Lines For floating licenses, the license information section of your License Pack contains a SERVER line. The SERVER line defines the hostname of the FLEXlm license server, the CPUID of the server, and the TCP/IP port number for communication with PTC clients. Only one server line is needed per license server.

When you get your license pack, a generic string will populate the hostname field. If you import the license pack into Pro/SETUP, this field will be replaced with the actual hostname of the server. If you are entering your license information into Pro/SETUP manually, you will need to replace this hostname when your license information is entered.

On your License Pack, the default server line format is:

SERVER __hostname__ PTC_HOSTID=(Your CPUID) 7788

 

If your license server’s hostname was "spock", the hostname field will be expanded to read: SERVER spock PTC_HOSTID=08-00-69-76-0A-2E 7788
Daemon Lines Each license server requires a daemon line to define the name of the PTC FLEXlm daemon and the path to the executable in the FLEXlm installation directory. On your License Pack, the path to the executable is replaced with a generic string that is replaced with the appropriate path when the License Pack is imported into Pro/SETUP.

On your License Pack, the default server line format is:

DAEMON ptc_d __PTCDPATH__

 

If your license server was installed in the /opt/ptc/flexlm directory, the daemon line would read: DAEMON ptc_d /opt/ptc/flexlm/sun4_solaris/obj/ptc_d

Feature Lines

With FLEXlm, serial numbers and security codes have been replaced with "feature lines" to license your software.

Feature lines define all the licensing elements (product, modules, number of licenses, and so on) to use the license on the proper host. Since all elements of a license are defined in a feature line, it can be said that feature lines replace the serial number, and security codes (revision codes, option codes, floating license codes, etc.) of PTC’s proprietary licensing scheme.

Feature lines are stored in a "license file" that is used by FLEXlm and PTC software. A single license file can contain multiple feature lines for a single or multiple products.

Feature line formats vary depending on the type of license and its usage. Refer to Appendix B for examples of feature lines per license type.

The following example shows a feature line for five locked evaluation licenses of Release 20.0 Pro/ENGINEER license for cpu_id 08-00-4E-22-AB-08. Note that the feature line contains all licensing information for the license and replaces the serial number and associated security codes.

INCREMENT PROE_366 ptc_d 20.0 11-Jul-1998 0 \ 85739247224342g47s94 VENDOR_STRING="VSVER=1.0 \

LO=(0 2 4 6 7 9 10 17 19 21 22)"\

HOSTID="PTC_HOSTID=08-00-4E-22-AB-08 \

PTC_HOSTID=08-00-4E-22-AB-09 \

PTC_HOSTID=08-00-4E-22-AB-10 \

PTC_HOSTID=08-00-4E-22-AB-11 \

PTC_HOSTID=08-00-4E-22-AB-12" \

SUPERSEDE ISSUED=01-Feb-1998

 

 

Feature Line Components Each feature line contains all the components necessary to license the software including Feature name (product prefix_configuration ID), release, expiration date for timed licenses, number of licenses, optional modules, issue date, and the license code. The license code is defined by all the parameters that define the license.

The figure below shows an example of five floating evaluation licenses of Pro/ENGINEER Release 20.0. For licenses that use a FLEXlm server (floating licenses, floating options, and counted locked licenses) the CPUID is specified in the SERVER line, not the feature line.

 

 

 

 

 

 

 

 

 

 

 

INCREMENT PROE_366 ptc_d 20.0 11-Jul-1998 5 85739247224342 \

VENDOR_STRING="VSVER=1.0 LO=(0 2 4 6 7 9 10 17 19 21 22)"\

SUPERSEDE ISSUED=01-Feb-1998

   

 

Feature Line Comments

 

To help PTC customers manage their license files with ease, comment lines precede each feature line. The comment lines allow you to quickly identify a license. If you are manually entering your license information into Pro/SETUP, the comment lines need not be entered.

 

#####################################################

# Feature Name = PROE_266 Type = evaluation

# Release = 20.0

# Number of Licenses = 5

# License Code = 85739247224342

# Issued Date = 01-Feb-98

# Cpu_id = 08004E22AB08

# Optional Modules = Pro/FEATURE, Pro/ASSEMBLY, Pro/DESIGN, Pro/INTERFACE, Pro/SURFACE, Pro/DETAIL, Pro/REPORT, Pro/PLOT

 

INCREMENT PROE_366 ptc_d 20.0 11-Jul-1998 5 \ 85739247224342 VENDOR_STRING="VSVER=1.0 \

LO=(0 2 4 6 7 9 10 17 19 21 22)"\

SUPERSEDE ISSUED=01-Feb-1998 

 

License File Pro/SETUP stores your feature lines in a file called the "license file". By default, the file is a text file written to flexlm_installation_directory/licensing/license.dat. This file is read by the PTC/FLEXlm daemon ptc_d to manage the use of the licenses.

For floating installations, the license file contains:

Locked installations with the exception of Pro/MECHANICA licenses will not contain SERVER and DAEMON lines.

For triad installations, an identical license file will be used by each triad partner. The license file will contain three SERVER lines, feature lines for all products licensed to the triad, and any additional products licensed to any single partner.

Combining License Files from Different Vendors Do not combine your PTC license file with the license files of other software vendors on the same FLEXlm license server. Although FLEXlm can handle combining license files, PTC’s cpu_id routine requires PTC licenses to be located in their own file. In addition, Globetrotter no longer recommends combining license files from different vendors. Additional License File Information More details on FLEXlm license files can be found in Chapter 2 of Globetrotter’s FLEXlm end-user documentation.   --------------AC003D95440B3B29DE712507 Content-Type: text/html; charset=us-ascii; name="contents.htm" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="contents.htm" Content-Base: "file:///C|/FLEX/web/contents.htm" Table of Contents
 
Table of Contents

 

About This Guide

 

Overview *

Section 1: The Installation Process Chapter 1: Overview of the Installation Process

Streamlined Installation 1-*

On the License Server(s) 1-*

On the License Client(s) 1-*

Default Installation Directories 1-*

Chapter 2: Getting Started

Obtaining Your FLEXlm Codes 2-*

Via the Web 2-*

Via E-mail 2-*

Chapter 3: Installing a Floating License
Section 2: Release Notes Chapter 4: Major Licensing Enhancements In Release 20.0 Serial Numbers Replaced with Configuration IDs 4-*

Floating and Locked Licenses 4-*

FLEXlm License Codes 4-*

License Counts 4-*

Internet Access 4-*

Consolidation of Multiple Serial Numbers 4-*

Serial Numbers Spanning Multiple License Servers 4-*

Locked Licenses 4-*

Product Specific Changes 4-*

Pro/PDM Licenses 4-*

Revision Compatibility 4-*

Triad Installations 4-*

Floating Options 4-*

Time-Sensitive Licenses 4-*

Evaluation Licenses 4-*

Rep Licenses 4-*

AE Licenses 4-*

Demo Licenses 4-*

ENHANCEMENT BENEFITS 4-* Single Server Solution 4-*

Increased Flexibility 4-*

Immediate License Recovery 4-*

Less Security Code Management 4-*

Centralized License Storage 4-*

Multiple Licenses for a Single Command 4-*

License Information can be Imported 4-*

On-line Help Screens 4-*

What's New And What's Not? 4-*

Chapter 5: New Software Licensing

Configuration IDs 5-*

Feature Lines 5-*

Pro/SETUP and the License File 5-*

FLEXlm and PTC Software 5-*

Configuration IDs 5-* Configuration IDs and Locked Licenses 5-*

On-line Configuration ID Information 5-*

Chapter 6: License Conversion (Serial Numbers to Configuration IDs) Serial Numbers Replaced with Configuration IDs 6-*

Floating and Locked Licenses 6-*

FLEXlm License Codes 6-*

License Counts 6-*

Internet Access 6-*

Consolidation of Multiple Serial Numbers 6-*

Serial Numbers Spanning Multiple License Servers 6-*

Product Specific Changes 6-*

Conversion Examples 6-* Locked Licenses 6-*

Floating Products 6-*

Chapter 7: License Codes

License Packs 7-*

Server Lines 7-*

Daemon Lines 7-*

Feature Lines 7-*

Feature Line Components 7-*

Feature Line Comments 7-*

License File 7-6

Combining License Files from Different Vendors 7-6

Additional License File Information 7-6

Chapter 8: FLEXlm and PTC Software

FLEXlm Daemons 8-*

The lmgrd Daemon 8-*

Vendor Daemons 8-*

Floating License Acquisition 8-*

Additional Notes 8-* Chapter 9: License Administration

Utility Name Changes 9-*

ptcmonitor 9-*

ptcflush 9-*

Starting and Stopping the FLEXlm Server 9-*

Fault Tolerant (Triad) Installations 9-*

License Timeout Parameter 9-*

Starting the Server Upon Reboot 9-*

Appendixes 9-*

Appendix A: Software Licensing Terminology

Appendix B: Feature Line Examples

Server and Daemon Lines (single server) A-*

Server and Daemon Lines (triad servers) A-*

Floating License, Pro/ENGINEER, 5 Licenses, Configuration ID 366 A-*

Locked License, Pro/ENGINEER, 1 License (uncounted),
Configuration ID 44333 A-*

Counted Locked License, Pro/MECHANICA 1 license,
Configuration ID 11323 A-*

Floating Option, Pro/CABLING 1 license A-*

Evaluation License, Pro/ENGINEER 1 Floating License,
Expiration date = May 1, 1998 A-*

Appendix C: Feature Name Prefixes

Appendix D: Getting Additional Help

 

.
 
  --------------AC003D95440B3B29DE712507 Content-Type: text/html; charset=iso-8859-1; name="feat_names.htm" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="feat_names.htm" Content-Base: "file:///C|/FLEX/web/feat_names.htm" Feature Name Prefixes
Feature Name Prefixes
The following table lists FLEXlm feature name prefixes. The license’s Configuration ID follows the prefix to complete the feature name.

 

 
Product
Feature Name Prefix 
Pro/ENGINEER PROE_
Pro/PDM  PDM_
Pro/NCPOST NCPOST_
Pro/FLYTHROUGH FLYTHRU_
Pro/INTRALINK CLIENT  INTRALINK_
Pro/MECHANICA Structure UI MECSTRUCUI_
Pro/MECHANICA Structure Engine MECSTRUCENG_
Pro/MECHANICA Motion UI MECMOTUI_
Pro/MECHANICA Motion Engine MECMOTENG_
Pro/MECHANICA Thermal UI MECTHERMUI_
Pro/MECHANICA Thermal Engine MECTHERMENG_
Pro/MECHANICA Equations Runtime MECEQRUN_
Pro/MECHANICA Interfaces MECINTERFCE_
Pro/MECHANICA Tire Model MECTIREMOD_
 

 

Feature names for floating options appear only as a number denoting the option. The feature name does not contain the product and Configuration ID. .
 
  --------------AC003D95440B3B29DE712507 Content-Type: text/html; charset=us-ascii; name="fl_examples.htm" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="fl_examples.htm" Content-Base: "file:///C|/FLEX/web/fl_examples.htm" Feature Line Example
Appendix B
Feature Line Examples
The following examples represent individual FLEXlm feature, server, and daemon lines for specific software configurations. Server and Daemon Lines (single server) SERVER spock PTC_HOSTID=08-00-76-32-E4-22 7788

DAEMON ptc_d /opt/ptc/flexlm/hp8k/obj/ptc_d

Server and Daemon Lines (triad servers) SERVER spock PTC_HOSTID=08-00-76-32-E4-22 7788

SERVER kirk PTC_HOSTID=72-72-76-50 7788

SERVER sulu PTC_HOSTID=08-00-2B-BC-4E-EF 7788

DAEMON ptc_d /opt/ptc/flexlm/hp8k/obj/ptc_d

 

 

 

Floating License, Pro/ENGINEER, 5 Licenses, Configuration ID 366 INCREMENT PROE_366 ptc_d 20.0 1-jan-0 5 \ 85739247224342AD332C VENDOR_STRING="VSVER=1.0 \

LO=(0 2 4 6 7 9 10 17 19 21 22)"\

SUPERSEDE ISSUED=01-Feb-1998

Locked License, Pro/ENGINEER, 1 License (uncounted), Configuration ID 44333 INCREMENT PROE_44333 ptc_d 20.0 1-jan-0 0 \ BC157229299924342EB7 VENDOR_STRING="VSVER=1.0 \

LO=(0 2 4 6 7 9 10 17 19 21 22)"\

HOSTID="PTC_HOSTID=08-00-4E-22-AB-08" \

SUPERSEDE ISSUED=01-Feb-1998

Counted Locked License, Pro/MECHANICA 1 license, Configuration ID 11323 INCREMENT MECSTRUCUI_11323 ptc_d 20.0 1-jan-0 1 \ 647C529BDE5333973h39 \

VENDOR_STRING="VSVER=1.0 LO=(85)"\

HOSTID="PTC_HOSTID=08-00-4E-22-AB-12" \

SUPERSEDE ISSUED=01-Feb-1998

 

INCREMENT MECSTRUCENG_11323 ptc_d 20.0 1 \ 0D7E7537EF83397984B3 \

VENDOR_STRING="VSVER=1.0 LO=(85)"\

HOSTID="PTC_HOSTID=08-00-4E-22-AB-12" \

SUPERSEDE ISSUED=01-Feb-1998

Floating Option, Pro/CABLING 1 license INCREMENT 48 ptc_d 20.0 1-jan-0 1 \

FC1534342999CA242EB7 \

SUPERSEDE ISSUED=02-Jan-1998

Evaluation License, Pro/ENGINEER 1 Floating License, Expiration date = May 1, 1998 INCREMENT PROE_65443 ptc_d 20.0 1-may-1998 1 \ 0E3247FEA342ADA50332 VENDOR_STRING="VSVER=1.0 \

LO=(0 2 4 6 7 9 10 17 19 21 22)" \

SUPERSEDE ISSUED=01-Feb-1998

.

  --------------AC003D95440B3B29DE712507 Content-Type: text/html; charset=iso-8859-1; name="flex.htm" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="flex.htm" Content-Base: "file:///C|/FLEX/web/flex.htm" FLEXlm
FLEXlm and PTC Software
This chapter contains some basic FLEXlm information as it pertains to PTC software. For comprehensive details, refer to the FLEXlm End User Manual. FLEXlm Daemons For floating licenses, two FLEXlm daemons work in conjunction: the FLEXlm license manager daemon ( lmgrd) and at least one vendor daemon. Both daemons run on the license server, but function differently. The lmgrd daemon is standard for all installations, while the vendor daemon is customized by the vendor (PTC) to manage license usage. The lmgrd Daemon The FLEXlm license manager daemon (lmgrd) runs on the license server and works in conjunction with the vendor daemons. The lmgrd daemon does not manage license usage. The lmgrd daemon: Refer to the floating license acquisition process for more details on how lmgrd works with the PTC daemon. Vendor Daemons Vendor daemons are customized FLEXlm software programs that are developed by the vendor who has integrated FLEXlm into their licensing environment. PTC is considered a vendor and has developed a vendor daemon called "ptc_d". The ptc_d daemon runs on the license server as well as lmgrd.
    1. Only one ptc_d may be running on a single license server at any one time. Pro/SERVER can run in parallel with ptc_d on the same license server.
Like all other vendor daemons, ptc_d’s function is to grant/deny floating licenses upon request from client applications. The ptc_d daemon, developed by PTC, contains the authentication information for license security; not lmgrd.

For customers who have multiple products licensed with FLEXlm, it is common to have a single lmgrd daemon running along with multiple vendor daemons.

Floating License Acquisition For floating licenses, the license acquisition process works as follows:

 

1. The PTC client communicates with the lmgrd daemon on the server requesting a PTC license.

2. The lmgrd daemon refers the PTC client to the ptc_d daemon for a PTC license. The lmgrd daemon does not issue licenses.

3. The PTC client requests the usage of a license by feature name from ptc_d.

4. The ptc_d daemon grants or denies the license depending upon availability.

Additional Notes . --------------AC003D95440B3B29DE712507 Content-Type: text/html; charset=iso-8859-1; name="sug_tech.htm" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="sug_tech.htm" Content-Base: "file:///C|/FLEX/web/sug_tech.htm" Installation Process  

 

Chapter 1
Overview of the
Installation Process

Streamlined Installation

Pro/SETUP has been enhanced to streamline the installation process. Since Pro/SETUP can now import licensing data, your installation should be faster and easier than ever. The License Manager is installed and configured on the license server, and then Pro/ENGINEER is installed and configured on each machine, including the license server machine.
    1. You must install the new Release 20.0 PTC software that uses FLEXlm into a new directory, that is, Pro/ENGINEER Release 19.0 cannot be updated to Pro/ENGINEER Release 20.0
On the License Server(s) The following steps outline the basic process for installing the FLEXlm license server and Pro/ENGINER on the license server machine 1. Obtain license information (codes) electronically from PTC and save this information to a text file. This step is not required, but recommended.

2. Execute Pro/SETUP.

3. Install FLEXlm into its own directory.

4. Import the license information file from step 1 into Pro/SETUP. Pro/SETUP starts the FLEXlm server after the installation is complete

5. Install Pro/ENGINEER into its own directory.

6. Define commands to run Pro/ENGINEER and "attach" the licenses listed within your license information file(s) to the command.

7. Install the optional applications such as the PTC Application Manager and Pro/HELP.

8. Initiate Pro/ENGINEER.

On the License Client(s) The client installation basically replicates a server installation without loading the License Management software. 1. Execute Pro/SETUP and install the PTC application (Do not install the license management software).

2. During the installation of the application,.

3. Install Pro/ENGINEER into its own directory.

    1. Define commands to run Pro/ENGINEER:
a. Specify the hostname of the license server,
b. "Attach" the licenses listed within your license information file(s) to the command.

5. Install the optional applications such as the PTC Application Manager and Pro/HELP.

6. Initiate Pro/ENGINEER.

Default Installation Directories Pro/SETUP now defines and installs software into a default installation directory that can be modified for your environment. The default directory is:

/system_directory/ptc

where system_directory is platform specific

Pro/SETUP now installs the license management software, PTC application software, and other software into subdirectories within the ptc directory.

 

Example: If Pro/ENGINEER Release 20.0, Pro/HELP, the PTC Application Manager, and Pro/FLY-THROUGH are all installed on a single license server, the /system_directory/ptc will contain a separate installation directory for each.

 

.
Chapter 2
Getting Started

Obtaining Your FLEXlm Codes

A License Pack is included with PTC maintenance shipments only as of Release 20.0. The License Pack contains the license information (feature lines) required to use your new software. The Pro/SETUP installation utility allows this information to be added manually or imported automatically with an electronic copy of the file, thus streamlining the installation process.

PTC provides two mechanisms for receiving an on-line copy of the License Pack for the Maintenance Shipment only. Both options require two important pieces of information from the License Pack: the Install Site Number and the Maintenance Shipment Number (MSN). With this information the License Pack can be requested through PTC's web site or e-mail. The License Pack will then be returned through an e-mail.

Via the Web The License Pack provides instructions for obtaining the License Pack information on-line via the PTC web page. With the Install Site Number, MSN, and an e-mail address, the License Pack information can be requested through the License Management section of the PTC web page. http://www.ptc.com/olmgmt/index.htm Via E-mail To receive a copy of the License Pack through e-mail, send an e-mail to the following address with the Install Site Number and Maintenance Shipment Number (MSN) as the Subject.

Send to: lmcodes@ptc.com

Subject: [Install Site Number] [Maintenance Shipment Number]

 

Example: 1234 112233445566

Where: Install Site Number - 1234

Maintenance Shipment Number - 112233445566

Mail Text: The body of the e-mail may be left blank.

    1. Obtaining an on-line copy of license information will make your installation process much faster and easier. Your License Pack has instructions for obtaining codes on-line.
Chapter 3
Installing a Floating License
    1. Obtain License
    2. Obtain license information (codes) electronically from PTC and save this information to a text file. This step is not required, but recommended.

       

    3. Execute Pro/SETUP as follows:
    4. Mount the Pro/ENGINEER CD per instructions in the Installation Guide or CD Jacket and execute the installation process through the setup command.
          example: Unix setup
      NT/95 setup.exe

      (If the installation process does not start automatically, execute from a DOS prompt or double click on the icon.)

       

    5. Install FLEXlm into its own directory as follows:
    1. Make sure that the License Management option has been selected, and choose Next to install the license server and licensing information.
    1. Use the Next command on each screen to proceed in the installation process.  The <<Back option allows for modifications or corrections in the installation parameters during installation.
    1. Select Next on the LICENSE MANAGEMENT (FLEXlm) SOFTWARE INSTALLATION screen.
    2. On the LICENSE MANAGER INSTALLATION DIRECTORY screen, specify the full path to the directory in which FLEXlm will be installed. Use the default listed directory or the Browse tool to identify and specify an alternative path for the desired directory.
    1. This directory must be either a new or an empty directory when doing a new installation. Pro/SETUP will create the directory during the installation process if necessary. For an Update installation, select the existing Pro/ENGINEER installation directory.
    1. Select Next to continue.
    1. Import the License file as follows:
Import the license information file from Step 1 into Pro/SETUP. Pro/SETUP starts the FLEXlm server after the installation is complete.
    1. After obtaining your codes as described in Chapter 2, select Next on the  OBTAIN YOUR LICENSE INFORMATION (CODES) screen.
    2. On the LICENSE INFORMATION screen, specify the file that contains your license information.  This should be an e-mail sent by the PTC License Management Group specifying your "License Pack" information.  The Browse tool can be used to identify and specify the appropriate file.
    1. Obtaining your license information on-line or by e-mail is highly recommended to facilitate the installation process.  Refer to your installation guide if your license information is not available through e-mail.
    1. At the LICENSE EDITOR screen, select the check button to verify that each of the licenses within the file are valid.
    2. Select Next to continue.
    3. On the INSTALLATION SUMMARY screen, select Install to load and initiate the License Server on this machine.  Pro/SETUP will then begin copying files and setting file permissions. It will attempt to start the server when completed. A message should appear stating that the installation was successful.
The LICENSE SERVER installation is now complete. Verify that the LICENSE SERVER has been successfully executed by running ptcstatus on the server machine before configuring Pro/ENGINEER.  The ptcstatus command has been installed in the /bin directory of the LICENSE SERVER loadpoint (e.g.. c:\ptc\flexlm\bin\ptcstatus).  This command must be run from an MS-DOS command prompt on a Windows NT or 95 machine.

If successful, continue to the next step to configure Pro/ENGINEER on the server machine or a license client machine.

    1. Install Pro/ENGINEER into its own directory as follows:
    1. On the Server Machine—Continue the installation process after installing the License Server.

    2. On a Client Machine—Mount the Pro/ENGINEER CD and execute the installation process through the setup command as defined above. Make sure that only the Pro/ENGINEER option has been selected and not the License Management option.
    3. Select Next on the PTC PRODUCT SOFTWARE INSTALLATION screen.
    4. On the DEFINE INSTALLATION COMPONENTS screen, define the following parameters for the software installation:
    1. Installation Directory (new)—Specify the full path to the directory in which Pro/ENGINEER will be installed. Use the default directory or the Browse tool to identify and specify the required path to the desired directory.
    1. This directory must be either a new or an empty directory when doing a new installation and should NOT be the LICENSE SERVER directory. Pro/SETUP will create the directory during the installation process if necessary. For an Update installation, select the existing Pro/ENGINEER installation directory. However, a Pro/ENGINEER Release 19.0 directory should not be updated to Release 20.0. The initial installation of Release 20.0 should be in a new directory.
    1. Architecture(s)—Pro/SETUP sets the default architecture to the current machine type. Use the Modify button to select any additional architecture. The appropriate architecture for each machine type that will access this Pro/ENGINEER installation directory should be selected. Use the Control key in conjunction with the left mouse button to select new items from the list.
    2. Language(s)—Pro/SETUP sets the default language to English.  Use the Modify button to select any additional languages to be used with this installation.
    3. Components—Select the desired components to install by selecting the box next to the appropriate component. An "X" next to the component indicates that the item has been selected for installation. The possible components for a Pro/ENGINEER installation are as follows:
Once all of the required information for Installation directory and components has been successfully selected, select Next to continue.
    1. Define Pro/ENGINEER commands
Define commands to run Pro/ENGINEER and "attach" the licenses listed within your license information file(s) to the command.
    1. The SPECIFY LICENSE FILE screen provides a list of available license servers or license files for acquiring available licenses to run the product.
    1. Select Next to continue.
    2. On the SPECIFY COMMAND screen, define a list of commands for initiating the various licenses for this PTC product. To begin defining commands select Add. Once all of the desired combinations of commands and licenses have been defined, proceed with the installation process.
    3. From the COMMAND INFORMATION screen, define the various parameters for each command to be used on this client the following input is required:
    1. The INSTALLATION CONFIGURATION screen provides several additional configuration options for the software on this client machine.  For a simple default installation, simply select Next to continue the installation process.  Each of these options can be reconfigured at a later date. The following outlines each of the Optional Configurations:
    1. On the INSTALLATION SUMMARY screen, a summary of the product configuration as defined will be displayed, select Install to load and initiate the product on this machine.  Pro/SETUP will then begin copying files and setting file permissions.
    2. Pro/SETUP will then begin copying files, setting file permissions and creating links. A message should appear stating the installation was successful. Select Ok and then Exit.
Pro/ENGINEER installation on the client machine is complete. Repeat this process for all clients.

If Pro/ENGINEER does not execute successfully, a Suggested Technique is available for troubleshooting Pro/ENGINEER floating installations in the Customer Service area of the PTC Web site.

 

    1. Install the optional applications
Install the optional applications such as the PTC Application Manager and Pro/HELP.
    1. See the Pro/ENGINEER Installation Guide for instructions on installing these applications.
 
    1. Initiate Pro/ENGINEER as follows:
Once everything has been completely installed, start Pro/ENGINEER as follows: Unix -Execute the command name defined in the installation process from a UNIX prompt (for example. pro20).

NT - Execute Pro/ENGINEER using the shortcut defined in the "Pro/ENGINEER" program group with the command name defined in the installation process (for example pro20).

 

 

 

 

 

 

 

 

 

--------------AC003D95440B3B29DE712507 Content-Type: text/html; charset=iso-8859-1; name="sysadmin.htm" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="sysadmin.htm" Content-Base: "file:///C|/FLEX/web/sysadmin.htm" License Administration
License Administration

Utility Name Changes

To allow Pro/SERVER and FLEXlm specific utility commands to coexist and function in parallel on a single license server, FLEXlm utility command names have been changed as follows.

 

 
Pro/SERVER Utility Name PTC/FLEXlm Utility Name
prostatus ptcstatus
proflush ptcflush
prostartserver ptcstartserver
proshutdown ptcshutdown
promonitor ptcmonitor
ptcsetup.csh setup.csh
ptcsetup.exe setup.exe
ptcutil ptcsetup
 

ptcmonitor

The ptcmonitor command replaces the promonitor command. This command can be used to monitor PTC license usage. ptcflush The ptcflush command replaces the proflush command. This command can continue to be used to release a floating license back to the license server. The following outline changes to ptcflush. Starting and Stopping the FLEXlm Server The ptcstartserver command replaces the prostartserver command. The command can be executed from the command line to start and stop the PTC/FLEXlm daemon ptc_d. Fault Tolerant (Triad) Installations Fault tolerant installations will continue to be supported with FLEXlm. An identical license file will be used by each triad partner. The license file will contain feature lines for all products licensed to the triad and any additional products licensed to any single partner. License Timeout Parameter The FLEXlm implementation has little effect on PTC’s license timeout policy. The default license timeout has been changed from 360 minutes to 120 minutes. This value can be increased to any integer larger than 120. There is no longer a maximum timeout restriction of 1440 minutes. The timeout can not be changed to less than 120 minutes. Starting the Server Upon Reboot

UNIX

Server startup scripts (for reboot) will be written to the ptc/flexlm/startup directory by default. This will occur regardless of UID.

The startup directory contains the boot scripts for all machine types along with a README.txt file with instructions for copying them to the appropriate files if the user desires.

If Pro/SETUP is executed as root and FLEXlm is to be installed, the user will be given a dialog box that informs the user that it is not recommended to run the server as root. An input field will be given to allow the user to specify a username for server execution.

For root installations, the server startup scripts will not automatically be written to the appropriate system files. Instead, Pro/SETUP will issue a dialog box asking the user if the files are to be installed. If OK is selected, the scripts are written to the system files. If Cancel is selected, the server will not automatically start when the machine is rebooted.

If Pro/SETUP is executed as a non-root user and "License Management" is selected, the server will be installed and executed as that user.

Windows NT If "License Management" is selected, Pro/SETUP will check for administrator privileges when the user selects "Next" on the front screen.

If the user does not have administrator privileges, a warning message is issued and the user is allowed to proceed. If the user does not have administrator privileges and imports or creates a license file that contains a server line, an error message will be given and the user will not be allowed to continue. If the license file does not contain a server line, the installation will continue as normal.

.

 

 

 

 

 

 

 

 

 

 

 

 
 
  --------------AC003D95440B3B29DE712507 Content-Type: text/html; charset=iso-8859-1; name="terminology.htm" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="terminology.htm" Content-Base: "file:///C|/FLEX/web/terminology.htm" PTC Licensing and Installation Terminology

Software Licensing Terminology
Term Definition
Configuration ID A unique number given to customers to identify their software.
Counted locked license A locked license whose usage is managed by a FLEXlm license server. Although it is managed by a license server, its usage is restricted to the machine for which it is licensed. The server will allow customers to use up to the number of licenses purchased at one time.
Datecode A unique number used to identify a specific version of PTC software. For example, Pro/ENGINEER Release 19.0 datecode 9744 identifies a specific version of Release 19.0 software.
Triad servers A configuration of three license servers on the same network that work together to manage a pool of floating licenses.
Feature line Text strings that define PTC software licenses.
Feature name A unique string within a feature line used to identify the license. The feature name format consists is product_configurationID i.e. PROE_12345; with the exception of floating options. The feature name for a floating option appears only as a number denoting the option number. 
FLEXlm Commercial license management software developed by Globetrotter, Inc.
Floating license A license to use PTC software that can be used on any supported client machine. A floating license is not licensed to be used on a specific workstation. The license is specific to a particular license server that controls usage. 
Floating option A module of PTC software that is not locked to a software license. Floating options are managed by a license server. The floating option is added to a session of a PTC application. Floating options can not be used as an independent piece of software.
Globetrotter, Inc. Developers of FLEXlm. Further Globetrotter information can be found at http://www.globetrotter.com.
Installation directory The directory where PTC software is installed.
License client A machine that requests a license from the license server in order to use the software. 
License file A text file written to disk by Pro/SETUP that contains FLEXlm feature lines and other license information.
License Management Software A software program that manages the usage of a software application such as Pro/ENGINEER, Pro/MECHANICA, etc. 
License Pack Documentation given to customers by PTC License Management that contains software licensing information.
License server A machine on which license management software is installed.
Lmgrd FLEXlm license manager daemon. 
Loadpoint The directory where PTC software is installed.
Locked License A license to use PTC software that can be used on a specific workstation only. Locked licenses can be "counted" or "uncounted".
Locked option An optional module of PTC software that is locked to a license of PTC software. When the license is successfully started, all locked options associated to the licenses are available.
Packing Slip A document included with all PTC software shipments that summarizes the contents of the shipment.
Pro/SERVER PTC’s proprietary license management software that manages floating PTC licenses and floating options.
Pro/SETUP PTC’s software installation program
ptc_d A customized FLEXlm vendor daemon that manages the use of PTC floating licenses using FLEXlm.
ptcflush Utility for manually releasing floating licenses and floating options back to the license server with FLEXlm. This utility’s command name is "proflush" with PTCLM.
PTC License Management PTC organization dedicated to administrative aspects of licensing of PTC products and the delivery of license codes.
PTCLM PTC’s serial number based licensing scheme. This system is involves generating a number of different security codes (revision codes, option codes, authorization codes, etc) all based off the serial number).
ptcmonitor Utility for monitoring and reporting license usage. This utility’s command name is "promonitor" with PTCLM.
ptcsetup Utility for reconfiguring installed PTC software licensed with FLEXlm. The utility can not be used to install new software. This tool’s command name is "ptcutil" with software using PTCLM licensing.
ptcstatus Utility that shows license availability for a license server. This utility’s command name is "prostatus" with PTCLM.
ptcutil Utility for reconfiguring installed PTC software licensed with PTCLM. The utility can not be used to install new software. This tool’s command name has changed to "ptcsetup" with software using FLEXlm.
Serial Number A set of alphanumeric numbers used with PTCLM for licensing PTC software. 
Uncounted Locked License A locked license whose permission to use the license is managed by the PTC application, not a license server. Unlimited number of uncounted locked license sessions can be run on a single machine at one time.
Vendor daemon A process or a Windows service that is customized by Globetrotter Inc.’s customers for managing software licenses using FLEXlm. The vendor daemon works in conjunction with the FLEXlm daemon, lmgrd.
 

.