Procision Installation Notes

PROCISION INSTALLATION NOTES

    1. Obtaining software
    2. Obtaining license
    3. Obtaining host ID
    4. Software installation
        4.1. Windows
        4.2. Unix
    5. Registering with Pro/ENGINEER
        5.1. Understanding protk.dat file
        5.2. Compatibility with different Pro/ENGINEER versions
        5.3. Pro/INTRALINK
    6. License setup
        6.1. Understanding Procision licensing
        6.2. Understanding license file
        6.3. Windows license setup
        6.4. Unix license setup
        6.5. Shareware license setup
    7. Installation test

1. Obtaining software

Procision software is available for download from http://www.procision.com/downloads.html. Otherwise contact your local Rand Worldwide office, or call 1-877-726-3243 to obtain a CD-ROM copy of the software.

Procision software is updated frequently; be advised to visit http://www.procision.com/downloads.html to download most recent build.

2. Obtaining license

Procision is licensed using FlexLM license server. A license file is required. Please contact your local Rand Worldwide office, or call 1-877-726-3243 to obtain license file(s) for purchased seats. Be advised that your license server host ID must be available in order to obtain the license file.

License file for the shareware license is available free of charge. The shareware license file is included with the installation package, and is copied into Procision <machine>\bin directory upon the software installation. Should the installation package contain an expired shareware license file, the up-to-date file may be downloaded from http://www.procision.com/downloads.html.

3. Obtaining host ID

To obtain an authorization code you will need to provide the Host ID for your license server. Host ID can be obtained as follows:

Windows (installed Pro/ENGINEER required):     cpu_id
SGI IRIX:                                                         sysinfo -s
HP UX:                                                            uname -i
Sun Solaris:                                                     hostid

4. Software installation

4.1. Windows

If software is obtained from http://www.procision.com/downloads.html, then a) download file pr_vXXX_intelwin.zip; b) extract to a temporary folder; c) run setup from within the temporary folder.
If software is obtained on a CD-ROM, then a) insert the CD-ROM into the CD-ROM drive; b) if the installation does not start automatically, run <cdrom_driveletter>:\setup.

Browse to the desired installation directory (also referred to as <Procision_loadpoint> directory); default location is C:\Apps\Procision_X.XX.

Browse to select Procision working directory (default <Procision_loadpoint>\wrk).

Select Pro/E installation directory (also referred to as <Proe_loadpoint> directory). This is the directory where the Pro/E software, with which you intend to run Procision, is installed (for example, C:\Program Files\proe2001). This step allows the setup to determine the version of Pro/E product and to create an appropriate protk.dat file. By default (if this step is cancelled), the setup will create protk.dat file suitable to run Procision with Pro/E version 2001. Note that this file may be edited later to register Procision to run with other versions of Pro/E (see Compatibility with different Pro/ENGINEER versions for more information).

Select whether or not to install a previously obtained license file. If yes, select the directory where this license file (must be called license.dat) is currently located; the setup will copy the file into the <Procision_loadpoint>\i486_nt\bin directory.

Restart Windows.

4.2. Unix

If software is obtained from http://www.procision.com/downloads.html, then a) download file pr_vXXX_<platform>.tar, where <platform> is sgiirix for SGI IRIX or sunsolaris for Sun Solaris; b) run tar -xvf pr_vXXX_<platform>.tar, which will extract the installation files into a new directory pr_vXXX; c) change directory to pr_vXXX; d) run installation script ./setup.sh.
If software is obtained on a CD-ROM, then a) insert the CD-ROM into the CD-ROM drive; b) mount the CD-ROM if necessary (your Unix system administrator would know how to do that); c) run installation script <cdrom>/setup.sh.

Select your platform (sgi_mips4 for SGI IRIX, or sun4_solaris for Sun Solaris). By default, the platform is automatically determined by the setup script; confirm if correct.

Type in the desired installation directory (also referred to as <Procision_loadpoint> directory); default location is /opt/procision_vXXX. Make sure you have permission to write into this directory.

Select whether or not to create a protk.dat file. If yes, the setup script will create the protk.dat file in the <Procision_loadpoint> directory.

If protk.dat file has been requested, select Pro/E version you wish to run with Procision -- 2000i/2000i2 or 2001.

Read file <Procision_loadpoint>/Unix.txt before attempting to run Procision. Make sure you have all necessary environment variables set.

5. Registering with Pro/ENGINEER

5.1. Understanding protk.dat file

Registering Procision means providing information to Pro/ENGINEER about the files that form Procision application. This is done via a small text "registry file", that Pro/E will find and read. Pro/E searches for the registry file in the following locations, in the following order:

A file called protk.dat in the Pro/E current directory (this is normally Pro/E startup directory).
A file named in a PROTKDAT statement in the Pro/E configuration file.
A file called protk.dat in the directory <Proe_loadpoint>/<machine>/text/<language>.
A file called protk.dat in the directory <Proe_loadpoint>/text.

Option 1 is most restricted, because in this case Procision will be seen by Pro/E only if Pro/E is started from the specific directory that contains the appropriate protk.dat file. Options 2 and 4 make sure that the registry file is always found, and Procision is seen by Pro/E, no matter what directory is used to start Pro/E. Option 3 is not normally recommended.

At installation, Procision creates a protk.dat file in <Procision_loadpoint>\wrk directory (Windows), or in <Procision_loadpoint> directory (Unix). At this point, further choices of registering Procision with Pro/E are as following:

As per option 1 above. On Windows: create a shortcut to Pro/E startup .bat file, starting in the Procision working directory (Note that you may use any directory as Procision working directory, just make sure this directory contains a copy of Procision protk.dat file as well as a shortcut to Pro/E that starts in this directory). Always use this designated shortcut to run Procision. The disadvantage of this option is that Procision will start with this designated Pro/E shortcut only; the advantage is that Procision application will not attach to Pro/E application (it may be desired since Procision, when attached to Pro/E, increases RAM taken by Pro/E application) if Pro/E is started in another directory. On Unix: copy Procision protk.dat file into directory you choose as Procision working directory, then always start Pro/E in the Procision working directory if you wish to run Procision; all other considerations mentioned above are valid for Unix too.
As per option 2 above. Add statement 'PROTKDAT <path_to_protkdat_file>' to the config.pro file that is read by Pro/E at startup (for more information about config.pro file please refer to Pro/E documentation). Note that you may remove/comment this statement should you wish to run Pro/E without Procision attached, then later add/uncomment the statement to run Procision again.
As per option 4 above. Copy Procision's protk.dat file into <Proe_loadpoint>/text directory. In this case, Procision will always be active no matter from which directory Pro/E starts.

5.2. Compatibility with different Pro/ENGINEER versions

Procision requires different application files be registered with different versions of Pro/ENGINEER:

Pro/E 2000i/2000i2 -- file pr_proe2000i.dll
Pro/E 2001 -- file pr_proe2001.dll
Pro/E Wildfire -- file pr_proewildfire.dll

The name of Procision application file to be registered is contained in the exec_file statement of the protk.dat file. For example:

exec_file C:\Apps\Procision_4.13\i486_nt\bin\pr_proe2001.dll

Procision setup creates an appropriate protk.dat file upon software installation, given the user's input on which Pro/E version will be used. The exec_file statement of this file may later be edited, should the user wish to use a different version of Pro/E.

5.3. Pro/INTRALINK

If Pro/ENGINEER is started by Pro/INTRALINK, then PROTKDAT statement in config.pro file should be used to register Procision (see Understanding protk.dat file for more information). In this case, make sure the Pro/INTRALINK startup directory contains this config.pro file.

6. License setup

6.1. Understanding Procision licensing

Procision licensing is based upon FlexLM licensing software. The components of Procision licensing are as follows:

License file (default name license.dat). This is a text file containing information about the license(s) to use Procision software, for example, number and type of licenses, expiration date, version of software, etc., as well as the authorization code.
License server lmgrd.
License daemon procisiond.
Various licensing utilities: lmtools, lmutils, installs, lmdiag, lmdown, etc.

The license file is normally sent to the end-user by e-mail upon issuance of a license. Other licensing components are supplied with Procision software and installed into <Procision_loadpoint>\i486_nt\lmgr directory on Windows, or <Procision_loadpoint>/<platform>/lmgr directory on Unix. Note that lmgrd server may already be present on your computer, since other applications installed on your computer might utilize FlexLM licensing software too.

Three kinds of licensing activity take place when Procision is used (this is an approximate description, intended to demonstrate the main ideas only):

License server startup: a) lmgrd starts and reads the license file (the pathname for the license file must be supplied as an argument in the command that starts lmgrd), b) lmgrd starts procisiond daemon (hence procisiond must either be in the same directory where lmgrd starts, or VENDOR line in the license file must contain the correct path to procisiond), c) procisiond checks validity of the license file, and d) lmgrd memorizes the number of licenses available and stays active until explicitly shut down.
License check-out (takes place when PROCISION item in the PART menu is clicked): a) Procision application finds and reads the license file and checks its validity, b) Procision sends a signal to the lmgrd license server that a check-out is requested, c) lmgrd asks procisiond to check the validity of the request, and d) lmgrd decrements the number of licenses available (thus counting the number of licenses in use) and sends a signal back to Procision that the license check-out is permitted.
License check-in (takes place when Procision menu is exited): a) Procision application sends a signal to lmgrd that Procision is no longer running, b) lmgrd increments the number of available licenses.

Note that for the above scheme to work it is critical to ensure that both license server and Procision application either read the same license file, or read two different files that contain identical Procision-related information (could be copies of Procision license file, or contents of Procision license file could be appended to other FlexLM license files).

By default, Procision application looks for a file called license.dat in the <Procision_loadpoint>\i486_nt\bin (Windows) or <Procision_loadpoint>/<platform>/bin (Unix) directory. This can be changed, though, by using the LICENSE_FILE statement in the Procision configuration file config.szf (refer to Procision User's Manual for details).

The license server lmgrd, as already mentioned, requires the license file pathname be supplied at the lmgrd startup.

A variety of options how the license file(s) can be configured is available; below are the most commonly used:

Both lmgrd and Procision read the same license file, for example, located in <Procision_loadpoint>\i486_nt\bin (Windows) or <Procision_loadpoint>/<platform>/bin (Unix) directory. This option is most convenient if both license server and Procision run on the same computer.
Lmgrd and Procision read identical copies of the same license file, possibly located on different computers. This option is most convenient if Procision is required to run on any computer in a network; in this case only lmgrd is 'locked' to a particular computer.
Procision reads the original license file while lmgrd reads a license file that contains Procision license information along with licenses for other applications. This option conveniently allows to have single lmgrd process serving several different applications that utilize FlexLM licensing (for example, Procision, Pro/E, Rational Rose, etc).

Note that described later Windows license setup and Unix license setup procedures realize option 1.

Please visit http://www.macrovision.com/solutions/esd/index.html should you require more information on FlexLM licensing.

6.2. Understanding license file

The default name for the Procision license file is license.dat; it is a small text file similar to:

    SERVER <hostname> <host_id>
    VENDOR [<path>]procisiond
    PACKAGE modules_<feature> procisiond <version> COMPONENTS="procision_pre_<feature> \
    procision_solver_<feature> procision_post_<feature>" SIGN="<signature_1>"
    FEATURE modules_<feature> procisiond <version> <expiration_date> <no_of_lic> \
    SIGN="<signature_2>"
    PACKAGE components_<feature> procisiond <version> \
    COMPONENTS="procision_struct_<feature> procision_thermal_<feature> \
    procision_modal_<feature> procision_imp_<feature> procision_freq_<feature> \
    procision_rand_<feature>" OPTIONS=SUITE SIGN="<signature_3>"
    FEATURE components_<feature> procisiond <version> <expiration_date> <no_of_lic> \
    SUITE_DUP_GROUP=SITE SIGN="<signature_3>"

<hostname> is your computer's hostname (network name); this may appear as unknown if you did not provide the hostname while requesting the license. If this is the case, enter the correct hostname in that field. Important: this is the first of two fields in the license file (the second is <path>) that may be safely modified; modifying any other field will invalidate the license, and Procision will not start.

<host_id> is your computer's host ID.

<path> is the path to the procisiond daemon (<Procision_loadpoint>\i486_nt\lmgr\ on Windows, or <Procision_loadpoint>/<platform>/lmgr/ on Unix). This field allows the license server lmgrd (see Understanding Procision licensing for more information) to find and start procisiond daemon; it may be empty if lmgrd is started in the same directory where procisiond is located (this is the default configuration upon Procision installation). Important: this is the second of two fields in the license file (the first is <hostname>) that may be safely modified; modifying any other field will invalidate the license, and Procision will not start.

<feature> indicates the type of Procision license (see http://www.procision.com/support.html for more information). This field may appear as main (full Procision version), light ('lite' version), edu (educational, or student version), eval (evaluation version), or shw (shareware version).

<version> is the version of Procision licensing scheme, tied to Procision version number. Important: the licensing scheme changes with major Procision releases only; currently it appears as 4.0 and is good for Procision versions from 4.0 up to 4.49.

<expiration_date> is the license's expiration date. It may also appear as permanent if the license has no expiration date.

<no_of_lic> is the number of licenses, i.e. the number of concurrent Procision sessions this license file allows to have.

<signature_1>, <..._2>, <..._3> are 'signatures' used by the licensing software to verify the validity of the license file.

6.3. Windows license setup

You will likely be provided with the license file as an attachment by e-mail. The file you receive would likely be named license.dat.ABCcorp where ABCcorp would correspond to your company name. Rename this file to license.dat and put it in the <Procision_loadpoint>\i486_nt\bin directory (it is recommended to save already existing there license file, if any, under a different name). Also make sure the SERVER statement in the license.dat file contains the correct hostname (network name) of your computer; edit this line if necessary.

Next, we must create the means to start the license server.

One way is to set up a shortcut on your desktop that can be double-clicked to start the license server. The server needs to be started only once, or after a reboot. Once the shortcut is created, you may copy it into your startup folder so it will initiate automatically.

Right-click on an empty space of your desktop, and select NEW > SHORTCUT. In the box COMMAND LINE enter:

<Procision_loadpoint>\i486_nt\lmgr\lmgrd -app -c <Procision_loadpoint>\i486_nt\bin\license.dat

Double-click the icon to start the license server.

Another way is to create a Windows service that will start Procision license server automatically each time Windows is started:

Start (double-click) lmtools application found in <Procision_loadpoint>\i486_nt\lmgr directory.
Select Configuration using Services in the Service/License File tab.
Go to Configure Services tab.
Enter a new service name in the Service Name drop-down menu.
Browse to <Procision_loadpoint>\i486_nt\lmgr\lmgrd in Path to the lmgrd.exe file field.
Browse to <Procision_loadpoint>\i486_nt\bin\license.dat in Path to the license file field.
The Path to the debug log file field can be anything.
Save the service, then check both Use Services and Start Server at Power Up checkboxes.
Go to Start/Stop/Reread tab and stop the service.
Press Start Server button to start the service. Press Start Server button once again; If the message at the bottom says "Server Start Failed. The Server May Already Be Running!!", then the service is up and running.
Go to the Service Status tab and perform a status enquiry. Should the service time out, start it again.
Exit lmtools application.

6.4. Unix license setup

You will likely be provided with the license file as an attachment by e-mail. The file you receive would likely be named license.dat.ABCcorp where ABCcorp would correspond to your company name. Rename this file to license.dat and put it in the <Procision_loadpoint>/<platform>/bin directory (it is recommended to save already existing there license file, if any, under a different name). Also make sure the SERVER statement in the license.dat file contains the correct hostname (network name) of your computer; edit this line if necessary.

Next, the license server must be started. From Unix shell, execute the command:

<Procision_loadpoint>/<platform>/lmgr/lmgrd -c <Procision_loadpoint>/<platform>/bin/license.dat

Your Unix system administrator would know how to setup this command to execute automatically upon system startup by including it in one of many possible startup scripts. Otherwise, you must execute this command manually each time the system is rebooted.

6.5. Shareware license setup

The shareware license file is installed by default by Procision setup program. On Windows, this is file license.dat.shareware located in <Procision_loadpoint>\i486_nt\bin directory; just rename this file to license.dat to have the shareware license set up. On Unix, this is file license.dat located in <Procision_loadpoint>/<platform>/bin directory; here no other steps are required to have the shareware license active.

7. Installation test

To test the installation:

Start Pro/ENGINEER.
Open or create a simple part.
A menu item PROCISION should appear on the PART menu. If not, it means that Procision application is not seen by Pro/E -- check if Registering with Pro/ENGINEER has been done correctly.
Click on PROCISION menu item.
PROCISION should initialize provided everything is setup correctly. If a window appears with error messages related to licensing -- check if License setup has been done correctly.

If you still have trouble, contact Rand hotline at 1-800-625-RAND.