CATIA V5 LICENSING COOKBOOK
How To Set-Up Nodelock
or
Concurrent Licensing
for CATIA V5
Version 1.0
March 18, 2002
Pre-requisites
• You need an IBM Customer Number under which V5 products
have been purchased
• You need a computer that has a Network Interface Card (NIC)
installed
2
Getting Started:
The Target ID
• The Target ID is the unique identifier of each workstation where
you intend to install CATIA licenses
• For NODELOCKED (Standalone) licenses, this is the
identification of the workstation where CATIA is to be installed
• For CONCURRENT (Network) licenses, this is the identification
of the network license server
• The Target ID must be supplied when CATIA licenses are
ordered
3
Obtain the Target ID
• Obtain the Target ID of the machine on which you will be
installing licenses
• If you already have CATIA V5 installed, run the Nodelock Key
Management Tool from the Startà àProgramsà àCatiaà
àTools
Windows menu
4
Obtain the Target ID via LUM
• If you don’t have CATIA installed yet, you can obtain the Target
ID via the LUM (License Use Management) i4target tool
• The i4target tool will be installed when you install LUM
• The latest LUM code for all platforms can be downloaded from:
– http://www-4.ibm.com/software/is/lum/download.html
• Note: For Windows, the i4target executable can be
downloaded at the above site under the tools directory for the
Windows platform
• LUM code is also provided on a separate CD, packaged with V5
CATIA code
5
Locating LUM Code on Your System
• The i4target tool is located in the directory where LUM
executables get installed
• The location of the LUM tools for the various platforms is shown
on the next slide
6
Location of LUM Tools
• Windows NT/2000/XP
– \Ifor\Win\Bin
• AIX
– /var/ifor or /usr/opt/ifor/ls/os/aix/bin
• HP, IRIX, SOLARIS
– /var/lum
or
– /opt/lum/ls/os/hpux/bin (HP)
– /opt/lum/ls/os/svr4.sgi/bin (IRIX)
– /opt/lum/ls/os/solaris/bin (SOLARIS)
7
Obtain the Target ID (cont)
• Run the following command to display the Target ID:
i4target -O
• On Windows you may be able to just double-click on i4target.exe,
and a message box displaying the win32mac Target ID of the
machine will be displayed
• The Target ID is a number represented in hexadecimal notation
• Below is an example of the i4target –O output showing a valid
win32mac Target ID:
LUM Target ID
-----------------
745315e5 win32mac MAC-HW Address IBMTRP1
8
Target ID Problems (Windows only)
• For Windows, the hardware-based (win32mac) Target ID is
retrieved from the device driver that controls the network
adapter (not from the operating system)
• The entry I4DRIVER is stored in the Windows Registry, in the
path HKEY_LOCAL_MACHINE\SOFTWARE\IBM\License Use
Runtime, to record the name of the network device driver used
to retrieve the Target ID
• For this mechanism to work, a device driver that complies with
Network Driver Interface Specification (NDIS) 4 must be
installed on the workstation where licenses will be installed
• If you are not sure if your driver complies with NDIS 4, contact
the supplier of the driver to confirm NDIS 4 compliance
9
Target ID Problems (Windows only)
• If any of the following situations exists, perform the steps on the
following page to get a valid Target ID:
– The i4target –O command does not return a win32mac Target ID
– The i4target –O command returns a Target ID of all zeros
– The workstation has multiple network adapters
• If a valid Target ID is still not obtained after performing the steps on
the following page, submit an electronic pmr through the PLM
Technical Support website at:
http://techsupport.services.ibm.com/engineering/catia.probMgmt
10
Target ID Problems (cont)
Perform the following steps if you are not getting a valid Target ID:
(see example on next page)
1. Open a Command Prompt window.
2. Run regedit and remove the I4DRIVER entry from the registry under:
– HKEY_LOCAL_MACHINE\SOFTWARE\IBM\License Use Runtime
3. Run i4target –z from the command line.
– This will list the network adapters that can be used for the Target ID.
4. Run i4target –d devicename, where devicename is one of the
network adapters listed in step 3.
5. Run i4target –O to get a win32mac Target ID.
11
Example of Generating a Valid Target ID
12
Nodelocked vs. Concurrent
• CATIA licenses can be ordered in two different forms (types):
Nodelocked (Standalone) or Concurrent (Network)
• A Nodelocked license is stored in a nodelock file on a specific
workstation, and allows one use of a CATIA product at a time on
the specific machine
• A Concurrent license is a license stored on a License Use
Management (LUM) Server, that can be used by any client
workstation
13
Nodelock Guidelines
• A Nodelocked license restricts the use of a CATIA product to
the workstation specified in the license
• The IBM LUM software for managing nodelocked licenses is
integrated into the CATIA Version 5 software (LUM does not
need to be installed)
• CATIA, rather than LUM, manages use of nodelocked licenses
• Passwords (Nodelock Keys) for CATIA products are stored in a
nodelock file
• When you start CATIA, it checks the nodelock file to ensure
that you have a valid license
• The use of a local display of the hardware configuration is
mandatory for Version 5 usage in nodelock mode
14
Concurrent Guidelines
• Many LUM clients can share the licenses for CATIA
• LUM must be installed and configured on the server and each
client, and each client workstation must be connected to a server
• When a user at a client starts CATIA, LUM at the license server
determines whether a license is available
• When CATIA is running, the licenses that have been reserved for
that session of CATIA remain unavailable to other users
• When CATIA stops running, the licenses are returned to the
server, where they become available to other users
• Concurrent licenses allow as many users to run CATIA
simultaneously as there are valid licenses for CATIA available
from the network license servers in your licensing environment
15
Order Licenses
• Call the IBM Registration Center to order licenses
Ø (800) 446-8989 (USA)
or
Your Local Key Center
• You will need to provide the following:
– IBM Customer Number
– Target ID
– CATIA Product Number(s)
– Software Serial Number(s) (for configurations)
– Platform (operating system)
– License Type – Nodelocked or Concurrent
– Number of Licenses (always 1 for nodelocked product licenses)
16
Verify License Information
• Check the email that you receive from the License Key Center
to verify that the following information for your licenses is correct
(as shown on the next page):
– Target type (Platform)
– Target ID
– License type (Nodelock or Concurrent)
17
License Information
----------------------------------------------------------------------------------------
Product name . . . . . . . . . : MD2-Catia Mechanical Design C2
Product number . . . . . . . . : 5691MD2
Target type. . . . . . . . . . . . : win32mac Target id. . . . . . . : 745315e5
Password type. . . . . . . . . : LICENSE
No. of connections . . . . . : 1 License type . . . . : NODELOCKED
Passwords are valid From : 2002-03-04 To . . . . . . . . . . . . : 2003-03-04
Generated by userid. . . . . : KEYREGS1 Generated by sys : BLD-MENU
Generation reference No. : 2002-03-05-11.46.57.624231
Vendor name. . . . . . . . . . : Dassault Systemes
Vendor id. . . . . . . . . . . . . : 5242378dbf8d.02.c0.09.c8.93.00.00.00
Vendor Password. . . . . . . : dgq5mxkpvqhbi
Product Password . . . . . . : kukeitb8ipbgnvnnwc32g9apdhu7s5hauzackdimangaa
Product Version . . . . . . . : 5.1
18
Create License Certificate Files
• A License Certificate file can be created by cutting and pasting the
license certificate lines from the email that you receive from the
License Key Center into a file
• Create a separate License Certificate file for each license you have to
install
• The lines you need to cut and paste from your email into a file are
shown on the next page
19
License Certificate File
Cut and Paste the following lines into a file:
[LicenseCertificate] 1st line
.
VendorName=Dassault Systemes
VendorPassword=dgq5mxkpvqhbi
VendorID=5242378dbf8d.02.c0.09.c8.93.00.00.00
ProductName=MD2-Catia Mechanical Design C2
ProductVersion=TMPMCFA
ProductPassword=kukeitb8ipbgnvnnwc32g9apdhu7s5hauzackdimangaa
ProductAnnotation=TMPMCFAAAAA-
.
TargetTypeName=MS Win-32 MAC
TargetID=745315e5
.
SerialNumber=TMPMCFAAAAA
.
InstallProgram= Last line
-------------------------------------------------------------------------------------------
20
License Certificate File (cont)
• You can name each License Certificate file almost anything you
want (i.e. MD2.lic)
• The normal naming convention for License Certificate files is to
use a .lic extension
• The previous page showed the partial contents of a License
Certificate file to clearly display the first and last lines of the file
• The next page shows the complete contents of a License
Certificate file
21
[LicenseCertificate]
CheckSum=2CA72409B863E93B74449C72A0AD6F19
TimeStamp=1015354197
PasswordVersion=7
VendorName=Dassault Systemes
VendorPassword=dgq5mxkpvqhbi
VendorID=5242378dbf8d.02.c0.09.c8.93.00.00.00
ProductName=MD2-Catia Mechanical Design C2
ProductID=2119
ProductVersion=TMPMCFA
ProductPassword=kukeitb8ipbgnvnnwc32g9apdhu7s5hauzackdimangaa
ProductAnnotation=TMPMCFAAAAA-
LicenseStyle=nodelocked
LicenseStartDate=03/04/2002
LicenseDuration=366
LicenseEndDate=03/04/2003
LicenseCount=1
MultiUseRules=
RegistrationLevel=3
TryAndBuy=No
SoftStop=No
TargetType=26
TargetTypeName=MS Win-32 MAC
TargetID=745315e5
ExtendedTargetType=
ExtendedTargetID=
DerivedLicenseStyle=
DerivedLicenseStartDate=
DerivedLicenseEndDate=
DerivedLicenseAggregateDuration=
SerialNumber=TMPMCFAAAAA
Upgrade=No
CapacityType=
Bundle=No
Registration=No
Uniqueness=No
Capturable=No
InstallProgram= 22
Installing Licenses
Nodelock licenses are installed by importing License Certificates
via the Nodelock Key Management Tool
Concurrent licenses are installed by either:
• Importing License Certificates via the LUM Basic License Tool
Graphical User Interface (GUI)
or
• Using the i4blt command
• *Note: To be able to access the Basic License Tool (or i4blt), a
LUM Server must already be configured. For more information on
configuring a LUM server, refer to the LUM documentation,
Using License Use Management Runtime - Version 4.6.4, at:
– http://www-3.ibm.com/software/is/lum/library.html
23
Installing a Nodelock License by Importing a
License Certificate File
• To install a NODELOCK license run:
• On Windows:
StartàProgramsàCatiaàToolsàNodelock Key Management
• On UNIX, Enter the following command:
./catstart -run CATNodeLockMgt
This command is located in the directory:
/usr/DassaultSystemes/Bxx/OS_a/code/command
where Bxx is the CATIA release (i.e. “B08”) and
OS_a is the operating system:
• aix_a
• hpux_a
• irix_a
• solaris_a
24
Nodelock License Manager Warning
• If you haven’t installed any nodelock licenses previously, you
may get the following Warning when you first bring up the
Nodelock Key Management Tool:
• Select OK to Close the Warning
25
Importing a License Certificate File (cont)
• Select Import from the FILE menu in the Nodelock License
Manager window
26
Importing a License Certificate File (cont)
• Select the location of the License Certificate file that you created
and then press Open
27
Editing the Nodelock File
• If you need to manually edit the nodelock file, refer to the table
on the next chart for the location of the nodelock file on each
platform
• The contents of a nodelock file look like this:
• The format of the nodelock file is:
# Comment (included for product information only)
VendorID ProductPassword “ProductAnnotation” “Version” [“SerialNumber”]
28
Location of the Nodelock File
Platform Location
Windows NT \Ifor\Ls\Conf
Windows 2000 and XP \Documents and Settings\All Users\
Application Data\IBM\LUM *
AIX /var/ifor
HP, IRIX, SOLARIS /var/lum or /opt/lum/ls/conf
* Note that if LUM is installed on Windows 2000, the location of the
nodelock file will be \Ifor\Ls\Conf
29
Installing a Concurrent License by Importing
a License Certificate File
• To install a CONCURRENT license on a LUM License Server,
use the Basic License Tool provided with LUM (LUM must
already be installed and the machine configured as a License
Server)
• A License Certificate can be imported by using either the Basic
License Tool Graphical User Interface (GUI) or the i4blt
command
30
Enrolling a License using the Basic License
Tool GUI
• Run StartàProgramsàLicense Use RuntimeàBasic License
Tool to bring up the Graphical User Interface (GUI)
• Using the GUI, select Enroll à Single product from the
Products menu
31
Enrolling a License using the Basic License
Tool GUI (cont)
• Select the Import button at the bottom of the Enroll Product Window
32
Enrolling a License using the Basic License
Tool GUI (cont)
• Select the location of the License Certificate file that you created
and press Open
• Press OK in the Enroll Product Window
33
Importing a License Certificate File For a
Concurrent License Using the i4blt Command
• If you don’t have the LUM GUI, you can use the i4blt command
to import a License Certificate
• To import a License Certificate using the LUM i4blt command,
enter:
Ø i4blt -a -f filename
where filename is the name (including path) of the License
Certificate file you created
34
Installing Licenses Using the i4blt command
• To install licenses without creating License Certificates, use the
i4blt commands provided in the email that you received from the
License Key Center
• From the command line (on any platform), cut and paste the
i4blt commands listed after the line:
– Install commands for server xxxxxxxx
where xxxxxxxx is the TargetID of your server
35
Command to Install Licenses
• Following is an example of an i4blt command as provided by the
License Key Center:
(This command should be entered all on 1 line, with a space in place of each +)
i4blt -a -v "'Dassault Systemes' 5242378dbf8d.02.c0.09.c8.93.00.00.00 +
dgq5mxkpvqhbi" -p "'MD2-Catia Mechanical Design C2' TMPKCFA +
zvexusn7favx3gumftmccdk7i3gzrg29krttcaadg6fsgcsa TMPKCFAAAAA-" –S +
TMPKCFAAAAA
• The syntax for the i4blt command is:
i4blt -a -v "'VendorName' VendorID VendorPassword" -p "'ProductName'
ProductVersion ProductPassword ProductAnnotation" –S SerialNumber
* Note that each i4blt command should be all on 1 line (the above 2 lines should
be all on 1 line, with a space between 'Product Name' and ProductVersion)
36
Reserve Licenses in the CATIA License Manager
via Settings Management
• The role of the CATIA License Manager is to allow you to
reserve licenses before using the products
• You can reserve the licenses you want to start CATIA with
before you actually start CATIA by using the Settings
Management Tool
• Select the Settings Management menu under
StartàProgramsàCatiaàTools
37
Select Licenses (cont)
• Select the Licensing tab in the Options window to display the
License Manager
• Select the licenses that you want to start CATIA with (they must be
intensified) and then select OK (see example on the next page)
• You must select at least one configuration license
• Note that when you are working with nodelock licenses, those
licenses will be reserved by default when you start your CATIA
session, even if you unchecked the corresponding boxes in the
License Manager (Licensing tab of the Options window)
• During a CATIA session, you can reserve and release licenses
using the License Manager accessible via the Tools-->Options
menu, but you must then exit and restart your session
38
CATIA Licensing Options Window
39
You Are Now Ready to . . .
START CATIA
40
