Resource Center

Frequently Asked Questions Pro/ENGINEER Installation Terminology

Installation theory and terminology

*What is setup (or Ptc.SETUP)?

Ptc.SETUP is the name of the Pro/ENGINEER Graphical Installation Utility that is executed from the Pro/ENGINEER CD to install and configure Pro/ENGINEER.

To execute setup on UNIX systems:

  1. Mount the Pro/ENGINEER CD.
  2. Change working directories to /tmp using the command cd /tmp
  3. Enter the following command: /cdrom/setup where cdrom refers to the directory to which the CD device is mounted to. The exact syntax required for setup is machine specific. See the Installation Guide or the cd jacket for further information.
To execute Ptc.SETUP on Windows NT, 95/98 or 2000 systems:
  1. The Ptc.SETUP utility should start automatically upon inserting the CD into the CDROM device. If that fails try the next two steps.
  2. From the DOS command line enter the CD drive designation followed by the path to ptcsetup. Example e:\setup e:
  3. Double Click on the setup.exe file in the CD drive
Details on execution of setup can be found in Pro/ENGINEER, Release 2000i2 Installation guide.
*What is ptcsetup (or Ptc.SETUP)?

Ptcsetup is the name of the command that is used to start Ptc.SETUP, the Pro/ENGINEER Graphical Installation Utility located in the loadpoint/bin directory. The utility can be used to modify or configure existing Pro/ENGINEER installations. Pro/ENGINEER software can not be installed from the Pro/ENGINEER CD using ptcsetup.

Ptcsetup can be used to:

  1. Add new code or licensing information
  2. Configure the FLEXlm server,  floating licenses and floating modules (options).
  3. Create links to Pro/ENGINEER commands from an existing bin directory on UNIX platforms only.
  4. Change the command to execute an existing Pro/ENGINEER feature (formerly key).
  5. Obtain the Host ID of the machine.
*What is meant by a major release of Pro/ENGINEER?

A major release of Pro/ENGINEER is one that contains significant modifications to the software product's functionality. This involves new functionality and hundreds of new customer enhancements and improvements to the user interface. Pro/ENGINEER major releases are identified numerically, with a new release available approximately every six months. For example, Pro/ENGINEER Release 2000i2 versus Pro/ENGINEER Release 2000i.

*What is meant by the Pro/ENGINEER loadpoint?

The Pro/ENGINEER loadpoint refers to the directory in which the Pro/ENGINEER software is installed.

Examples:

    On UNIX systems: /usr/local/proe20

    On Windows NT, 95/98 or 2000 Systems: C:\ptc\proe20

The Graphical Installation Utility will create this directory during the installation process. An existing EMPTY directory can exist previously for the Pro/ENGINEER loadpoint.

*What is a full installation?

A full installation is performed for new installations to install the Pro/ENGINEER software from the CD to the hard drive. A full installation will perform the following functions:

  1. Prompts for config id's and commands to execute Pro/ENGINEER from the command line.
  2. Installs the Pro/ENGINEER software from the CD to the hard drive.
  3. Sets file permissions on the Pro/ENGINEER files as needed.
  4. Creates links to Pro/ENGINEER commands from an existing bin directory (UNIX systems only).
*What is an update installation?

An update installation is performed to replace an existing Pro/ENGINEER installation with one of the following:

  1. The next major release of Pro/ENGINEER i.e. update Release 2000i to Release 2000i2. Pro/ENGINEER release 20.0 cannot be updated from release 19.0. A new installation must be performed.
  2. A more recent software datecode within the same major Release of Pro/ENGINEER i.e. update from 1999260 to 1999350 of Release 2000i.
  3. Add an architecture to an existing installation.
See a Suggested Technique for Adding Architectures to Existing Installations.

Unlike a full installation, an update installation will preserve all licensing information as well as some configuration files such as config.pro and config.sup located in the loadpoint/text directory.

*What is the purpose of the Pro/ENGINEER License Pack?

The Pro/ENGINEER License Pack is shipped with new installations and Maintenance Releases only. The License Pack contains security codes needed to install the licenses of PTC Products at your site.

Questions regarding License Packs and Pro/ENGINEER security codes should be directed to the PTC  License Management Department at 1-800-477-6435.  If you have any questions or concerns regarding PTC's implementation of FLEXlm - Send email to ptcflexlm@ptc.com.

*What is the purpose of the Pro/ENGINEER Packing Slip?

The Packing Slip (bill of materials) is shipped with all orders and contains the items which have been sent with this shipment.


*What is the purpose of the Shipment Confirmation Letter?

The Shipment confirmation letter is received prior to receipt of the PTC software.  This letter is sent either by fax or e-mail.  This correspondences introduces you to the software distribution process.  The Sales Order Number is included here for new software orders.


*What is the purpose of the READ THIS FIRST?

The READ THIS FIRST document notifies you of any changes you must make, such as machine settings and recommended operating system patches.  The online copy of this document for Pro/ENGINEER can be found at: http://www.ptc.com/cgi/cs/doc/document.pl?document=RTF


*What is the purpose of the Hardware/Software Configuration Notes?

The Hardware/Software Configuration Notes provide the PTC Certified & Tested Hardware Configurations for running PTC Software and the compatibility of the different packages.  The online notes are found at:

On-line Hardware Configuration Notes - http://www.ptc.com/partners/index.htm

On-line Software Configuration Notes - http://www.ptc.com/cs/doc/software.htm


*Should links be created to Pro/ENGINEER commands?

On UNIX systems, setup and ptcsetup can be used to create links from an existing bin directory (/bin by default) to the Pro/ENGINEER commands located in the loadpoint/bin directory. UNIX systems are typically configured to search the /bin directory to find system commands. Creating links between /bin and the Pro/ENGINEER commands in loadpoint/bin will enable the UNIX system to find the Pro/ENGINEER commands. Refer to the UNIX manual pages on "ln" for specifics on symbolic links.  This selection is available on the screen prior to beginning the installation or update on a Create Links tab.

The Windows NT, 95/98, and Windows 2000 equivalent is the PATH variable. Both ptcsetup and Pro/SETUP modify the PATH variable as required without any input from the user.  If Pro/ENGINEER is installed as a user without Administrative priveledges, it is recommended to login as ADMINISTRATOR or a user with such priveledges and set the PATH at a system level such that all user's will have this variable set, regardless of login.

*What is the Pro/ENGINEER config id used for?

The config id is a unique numeric string given to all licenses of PTC software at the time of purchase. The Pro/ENGINEER config id is used to identify the license configuration and is a fundamental part of the Pro/ENGINEER licensing scheme. Each config id will have a unique authorization strings based upon the config id, FLEXlm Server Host ID, number of copies, optional modules, release, date issued and expiration date (if applicable). Within each config id will be features such as PROE_55683 which is referred to as a feature line.

*What does Host ID mean?

The Pro/ENGINEER software is licensed to be executed on predetermined machines. Pro/ENGINEER security codes are generated using a variable called Host ID. The Host ID is obtained from one of two different sources: the hostid for Sun Microsystem machines, or the ethernet address obtained from the network card on all other platforms including Windows NT, 95/98 and 2000 workstations.

*What are the optional module codes used for?

During the full installation process, all Pro/ENGINEER software is installed to disk, regardless of the modules purchased. The optional module codes (also known as static/locked options) are used to unlock the functionality associated with the optional module, i.e. the Pro/MESH option code will allow access to the Pro/MESH functionality within Pro/ENGINEER. The license is generated based on a number for the named option and a file maps these features back to the name of the option.

The option codes are specific to the option name and the Pro/ENGINEER config id, and can be found listed on the Pro/ENGINEER License Pack.  The Help, Customer Services Info menu selection can be used to display the optional modules installed.

*What is a floating license?

A floating license refers to a licensing scheme where the permission to execute the Pro/ENGINEER config id is controlled by the FLEXlm server (the Pro/ENGINEER license server). In a floating environment, the FLEXlm server will allow any machine configured as a client to use the config id until the number of licenses purchased has been exhausted.

Installation of a floating license requires an authorization string, which is specific to the number of licenses (copies) of the floating license purchased and the Host ID of the flexlm server machine.
 

Code Type Dependent On
*Optional Module Codes (static/locked)
  • Config Id
  • Option Name
Authorization String
  • Config Id (specifically feature name)
  • Host ID of FLEXlm server machine
  • Number of copies of the feature name purchased.
*What is an authorization string used for?

The authorization string is a Pro/ENGINEER security code specific to the config id, the number of licenses (copies) of the config id purchased, and the Host ID of the FLEXlm server machine. This code is listed within the license file and will be detected by the setup utility during the installation of Pro/ENGINEER.

The authorization string can be found on the Pro/ENGINEER License Pack. If your License Pack does not list authorization strings for your floating installation, please call the PTC License Management Department at 1-800-477-6435.

*What is a FLEXlm server?

The FLEXlm server refers to the Pro/ENGINEER floating license server which administers the use of the Pro/ENGINEER floating licenses and floating optional modules.

*What is a floating optional module?

Unlike a static option, a floating optional module is not specific to a Pro/ENGINEER config id. Permission to access floating options is controlled by the FLEXlm server. Once the floating options have been added to the flexlm server, Pro/ENGINEER clients request usage of the floating options by selecting #Utilities #Floating Modules and placing a check mark next to the desired option(s), regardless of the config id being used in the Pro/ENGINEER session.

The floating optional modules are returned to the FLEXlm server by exiting Pro/ENGINEER or by selecting #Utilities #Floating Modules and unchecking the desired option.

Installation of a floating optional module requires an authorization string, which is specific to the name of the option, the number of licenses (copies) of the option purchased, and the Host ID of the FLEXlm server machine.
 

Code Type Dependent On
Floating Optional Module Code
  • Host ID of the FLEXlm Server machine
  • Number of copies of the option module purchased
  • Option Name
  • Time code (for Evaluation Floating options)
*Is there an advantage to installing Pro/ENGINEER locally on all client nodes, as opposed to installing on a single file server?

Installing Pro/ENGINEER locally on each client node has advantages and disadvantages as follows:

Advantage: A performance improvement may be noticed by installing Pro/ENGINEER on each client node since Pro/ENGINEER can directly access its installation directory for all required software, opposed to making system calls through a network. The magnitude of the performance difference will depend on system hardware and configuration.

Disadvantage: If Pro/ENGINEER is installed on each client node, multiple Pro/ENGINEER installation directories will exist, each consuming at least 160MB of disk space for Release 2000i2. With multiple Pro/ENGINEER installation directories, an update installation is required on each machine in order to update Pro/ENGINEER to the next major release. A file server environment will save disk space and is less time consuming to maintain, but performance may fall victim to convenience.  Batch tasks or simple drag and drop copies can be performed if the machines architectures are identical and the installation location is consistent.

*What license codes are needed for each license type?
 
Commercial
Evaluation
Rep
AE**
Authorization String Needed Needed Needed Needed
Password Not Needed Not Needed Not Needed Needed
**Note: License has full Pro/ENGINEER functionality.

*What does ptcstatus do?

Ptcstatus is a tool that allows system administrators and users to see the current usage and availability of licenses. Typing ptcstatus at either the DOS or UNIX prompt will display information for each FLEXlm server available to the client. For each Pro/ENGINEER config id authorized for each FLEXlm server, the command displays the number of available licenses, and the client hosts that are currently using licenses.

Example:

C:\revs\flexlm\bin>ptcstatus

Displaying status for license file: 7788@newark

Features on newark:
Users of PROE_041969         : 1 licenses in use, 14 free licenses.

 (csmetana newark) PROE_041969 newark 7788 110

Users of Pro/SHEETMETAL      : 0 licenses in use, 15 free licenses.
Users of Pro/MOLDESIGN       : 0 licenses in use, 15 free licenses.



*What does ptcflush do?

Ptcflush is a command used to free up licenses which are not cleared.  The format for the command is:

ptcflush  feature_name  hostname  port  handle

Example:

ptcflush  PROE_041969  newark  7788  110

Where the output is taken from the ptcstatus command as shown above.


*What is ptcmonitor and how can it be utilized to monitor license usage?

Ptcmonitor, the license usage monitor, can be utilized to report how often each license is being used over a period of time (including floating modules). Statistics can be gathered on specific license usage which provides a better understanding of how much a particular product is being used.

The license usage monitor is always on and can be invoked to send the data to the screen by entering ptcmonitor.

Example of ptcmonitor from a command prompt: 

C:\revs\flexlm\bin>ptcmonitor

lmutil - Copyright (C) 1989-1997 Globetrotter Software, Inc.

lmreread successful

PROE_041969 newark csmetana 08/21/1998 08:48:06 08/21/1998 09:17:07

PROE_041969 newark csmetana 08/21/1998 09:17:28 08/21/1998 10:47:00

PROE_041969 newark csmetana 08/25/1998 09:18:07 08/25/1998 09:20:05

PROE_041969 newark csmetana 08/25/1998 09:20:14 08/25/1998 09:34:11

PROE_041969 newark csmetana 08/25/1998 09:34:19 08/25/1998 09:38:53

PROE_041969 newark csmetana 08/25/1998 09:38:56 08/25/1998 09:53:57

PROE_041969 newark csmetana 08/25/1998 09:54:02 08/25/1998 10:54:13

PROE_041969 newark csmetana 08/25/1998 10:54:18 08/25/1998 11:55:23

PROE_041969 newark csmetana 08/25/1998 11:55:34 08/25/1998 12:00:03

PROE_041969 newark csmetana 08/25/1998 12:00:09 08/25/1998 12:02:34

PROE_041969 newark csmetana 08/25/1998 12:02:37 08/25/1998 12:17:32

PROE_041969 newark csmetana 08/25/1998 12:18:44 08/25/1998 13:00:42
If a file of the data is necessary, a line forcing the output can be run as follows:
C:\revs\flexlm\bin>ptcmonitor  >  usage_082598.txt
Which will write the file as shown here:
C:\revs\flexlm\bin>type C:\revs\flexlm\bin\usage_082598.txt

lmutil - Copyright (C) 1989-1997 Globetrotter Software, Inc.
lmreread successful
PROE_041969 newark csmetana 08/21/1998 08:48:06 08/21/1998 09:17:07
PROE_041969 newark csmetana 08/21/1998 09:17:28 08/21/1998 10:47:00
PROE_041969 newark csmetana 08/25/1998 09:18:07 08/25/1998 09:20:05
PROE_041969 newark csmetana 08/25/1998 09:20:14 08/25/1998 09:34:11
PROE_041969 newark csmetana 08/25/1998 09:34:19 08/25/1998 09:38:53
PROE_041969 newark csmetana 08/25/1998 09:38:56 08/25/1998 09:53:57
PROE_041969 newark csmetana 08/25/1998 09:54:02 08/25/1998 10:54:13
PROE_041969 newark csmetana 08/25/1998 10:54:18 08/25/1998 11:55:23
PROE_041969 newark csmetana 08/25/1998 11:55:34 08/25/1998 12:00:03
PROE_041969 newark csmetana 08/25/1998 12:00:09 08/25/1998 12:02:34
PROE_041969 newark csmetana 08/25/1998 12:02:37 08/25/1998 12:17:32
PROE_041969 newark csmetana 08/25/1998 12:18:44 08/25/1998 13:02:11