I M NSTALLATION

XFILEV5
2.x.x
for CATIA® V5
Text version 16-Apr-14 4:35 PM
INSTALLATION MANUAL
Orientation Symbols Used in the Manual
Warning triangle
The warning triangle refers to critical circumstances ,
which should be considered i m p e r a t i v e l y
in order to avoid s e r i o u s problems in your work.
Hint symbol
The light bulb relates to hints ,
which provide you with practical examples
to simplify your work.
Note symbol
The hand symbol relates to notes ,
which you should pay attention to in order to assure
that you can work with out problems .
Info symbol
The info symbol relates to
background information .
Step symbol
The work steps symbol
refers to a
step -by-step instruction sheet.
TRANSCAT on the Internet:
http://www.transcat-plm.com
TRANSCAT Hotline:
Phone: +49 721 970 43 35
E-mail: [email protected]
© TRANSCAT PLM GmbH 2014
Transcat PLM GmbH
2
XFileV5 2.x.x
TABLE
OF
CONTENTS
Table of Contents
1.
Software and Hardware Requirements ........................................ 4
2.
Installing and Uninstalling under W I N DO W S ................................. 5
2.1
Installing .............................................................................................................. 5
2.2
Uninstalling .......................................................................................................... 5
3.
Installation under U N I X ............................................................. 6
3.1
Unpacking Files ................................................................................................... 6
3.2
The Created Directory Structure ........................................................................... 7
3.3
Adapting XF ILE V5 to the Local C ATIA Installation .................................................. 8
3.3.1
3.3.1.1
3.3.1.2
3.3.1.3
3.3.1.4
Creating a New CATIA Environment .......................................................................................... 8
Adapting the Declarations to the Existing Directories............................................................10
Specifying the Action Options .................................................................................................10
Creating an Environment ......................................................................................................... 11
Example of a CATIA Environment File ...................................................................................... 12
3.3.2
3.3.2.1
3.3.2.2
Extending an Existing CATIA Environment............................................................................... 13
Adapting the Declarations to the Existing Directories............................................................ 13
Starting CATIA with the XFILEV5 Environment ......................................................................... 14
4.
Environment Variables ............................................................. 15
5.
Installation of License Passwords ............................................. 16
5.1
License Request .................................................................................................. 16
5.2
Installation of Nodelock Licenses ....................................................................... 17
5.3
Installation of Concurrent Licenses ..................................................................... 18
***
Transcat PLM GmbH
3
XFileV5 2.x.x
1. SOFTWARE
1.
AND
HARDWARE REQUIREMENTS
Software and Hardware Requirements
Hardware:
CATIA:




All CATIA platforms (P1, P2 and P3) are supported.
PC
IBM RS/6000
HP
SUN
Minimal required version: V5 R16
Depending on the CATIA platform, the following
CATIA configuration packages must be installed and
the following licenses must be available:
Operation system:
CATIA P1 platform:
 all configuration packages (complete installation)
 PX1 and at least MD1 license
(minimal requirements):




WINDOWS 2000/XP
AIX 5.1, 5.2, 5.3
HP-UX 11.11
SOLARIS 2.8
CATIA P2 platform:
 all configuration packages (complete installation)
 PX1 and at least MD2 license
CATIA P3 platform:
 on request
Additionally required software
 A DOBE A CROBAT R EADER (minimal required version 5.0)
The ACROBAT READER is required to browse the XFILEV5 online-help.
To determine if you have ADOBE ACROBAT READER installed on your UNIX system, enter the
following command:
which acroread
This command displays the directory where ADOBE ACROBAT READER is installed.
Transcat PLM GmbH
4
XFileV5 2.x.x
2. INSTALLING
AND
UNINSTALLING
UNDER
WINDOWS
2.
Installing and Uninstalling
under W INDOWS
2.1
Installing
Steps:
To install TransCAT XFILEV5, follow these steps:
(1) Insert the XFILEV5 CD-ROM in the CD-ROM drive.
(2) Start the installation routine in WINDOWS Explorer, double-clicking on
the file name XFileV5Rx_xxx_setup.exe.
(3) Follow the installation instructions, edited on the display.
The installation results in creating:
 two icons—one for interactive mode, the interactive mode
 three bat files for batch mode—one for the XFileV5 export, one for the
XFileV5 import, and one for CONSISTENT FILE SET.
 Manual XF ILE V5 installation using zip file
If you don’t want to install XFILEV5 via setup.exe, as described above,
you can as an alternative perform a manual installation, using zip file.
This might be necessary e. g. in case of server installation. Further
information about this installation you can find in the document
Product_Installation_using_ZIP-archive.pdf, that you can
download from the Q-CHECKER download site
http://www.transcat-plm.com/tcsoft/downloads/q-checker_v5.html .
2.2
Uninstalling
Steps:
To uninstall TransCAT XFILEV5, follow these steps::
(1) Click in the Windows taskbar on the Start button and select the menu
item:
Settings > Control Panel > Add/Remove Programs.
(2) Select XFILEV5, and click on the button Change/Remove.
Transcat PLM GmbH
5
XFileV5 2.x.x
3. INSTALLATION
UNDER
UNIX
3.
Installation under U NIX
3.1
Unpacking Files
In case you have a compressed and packed XFileV5Rx_xxx.tar.gz file2, proceed as
follows:
Action
OS 1
Example
2
Copy TAR archive into an *
installation directory of
choice of choice.
cp XFileV5Rx_xxx.tar.gz /catdat/tcsoft
Change directory to the
installation directory
*
cd /catdat/tcsoft
Unpack the archive file
*
gzip –d XFileV5Rx_xxx.tar.gz | tar –xvf -
2
Note:
1
2
* stands for e v e r y CATIA UNIX operation system
xxx stands for the current version number.
Rx stands for CATIA release number
Transcat PLM GmbH
6
XFileV5 2.x.x
3. INSTALLATION
3.2
UNDER
UNIX
The Created Directory Structure
Directory
OS 1 Description
XFileV5Rx_xxx/aix_a
AIX
XFileV5Rx_xxx/hpux_b
HP
XFileV5Rx_xxx/solaris_a
SUN
XFileV5Rx_xxx/doc/German
AIX
XFileV5Rx_xxx/doc/German
HP
XFileV5Rx_xxx/doc/German
SUN
XFileV5Rx_xxx/doc
AIX
XFileV5Rx_xxx/doc
HP
XFileV5Rx_xxx/doc
SUN
XFileV5Rx_xxx/readme.txt
*
Latest program information and
changes
XFileV5Rx_xxx/XFileV5Env.csh
*
C shell script to extend an existing
environment
XFileV5Rx_xxx/XFileV5Env.sh
*
Shell script to extend an existing
environment
XFileV5Rx_xxx/XFileV5SetEnv.sh
*
Shell script to create a new
environment
Program modules and message files
Product documentation in PDFformat in German
Product documentation in PDF
format in English
Note:
1
2
* stands for e v e r y CATIA UNIX operation system
xxx stands for the current version number.
Rx stands for CATIA release number
Transcat PLM GmbH
7
XFileV5 2.x.x
3. INSTALLATION
3.3
UNDER
UNIX
Adapting XF ILE V5 to the Local C ATIA
Installation
There are two ways to adapt XFILEV5 to the local CATIA installation:
(1) Creating a new CATIA environment with automatic creation of a XFILEV5 icon in the
application manager (see chapter 3.3.1).
(2) Extending an existing CATIA environment (see chapter 3.3.1.4).
3.3.1
Creating a New C ATIA Environment
To create a new CATIA environment with XFILEV5 the shell script XFileV5SetEnv.sh is
delivered.
In the following, you will find an excerpt from this file. Adapt in this file the passages
marked gray to the realities of your local XFILEV5 installation. Further information to this
subject you can find in the following subchapters.
...
# environment name
#-----------------XFILEV5_ENV="CATIA_XFileV5"
#
# existing directory for environment
#-----------------------------------XFILEV5_ENV_PATH="${HOME}/CATEnv"
#
# TC XFileV5 directory (where aix_a ... is)
#---------------------------------------------XFILEV5_INSTALLATION="/catdat/tcsoft/XFileV5"
#
# Catia installation directory
#-----------------------------CATIA_INSTALLATION="/usr/catiav5r16/B16"
#
# get os dependent path
#----------------------export OSDS=`${CATIA_INSTALLATION}/GetOSDS`
#
# Load directory
#----------------------XFILEV5_LOAD="${XFILEV5_INSTALLATION}/${OSDS}/code/bin"
#
# Admin directory
#----------------------XFILEV5_ADMIN="${XFILEV5_INSTALLATION}/admin"
#
# User manual
#----------------------XFILEV5_DOC="${XFILEV5_INSTALLATION}/doc/manual.pdf"
...
Transcat PLM GmbH
8
XFileV5 2.x.x
3. INSTALLATION
UNDER
UNIX
...
setcatenv
-e $ XFILEV5_ENV
-d $ XFILEV5_ENV_PATH
-p $CATIA_INSTALLATION:$XFILEV5_INSTALLATION
-new yes
-desktop yes
–a global \
&& change_cat_env || echo "\aCreating the environment failed."
Transcat PLM GmbH
9
XFileV5 2.x.x
3. INSTALLATION
3.3.1.1
UNDER
UNIX
Adapting the Declarations to the Existing Directories
Adapt the following XFILEV5 variables to your local directory structure. The specifications
in the example above are only an e x a m p l e .
Variable name
Explanation
 XFILEV5_ENV
 Name of the new CATIA environment
 XFILEV5_ENV_PATH
 Path where the CATIA environment file is created
 XFILEV5_INSTALLATION
 Path where XFILEV5 is installed
 CATIA_INSTALLATION
 Path where CATIA V5 is installed
 XFILEV5_LOAD
 Directory of the executable files
 XFILEV5_ADMIN
 Directory of the XFileV5.par for default settings
 XFILEV5_DOC
 Directory of the user manual file
3.3.1.2
Specifying the Action Options
To generate CATIA environments, different options are available:
Variable
Value
Description
-new
yes
An already existing environment with the same name will be
o v e r w r i t t e n . (Recommended)
no
An already existing environment with the same name will n o t be overwritten, the existing environment remains.
yes
A desktop i c o n of the environment is generated. (Recommended)
no
N o desktop icon of the environment is generated.
global
A g l o b a l environment will be created.
Note:
To create a global environment, you must have the administrator rights.
user
A u s e r environment will be created.
-desktop
-a
Transcat PLM GmbH
10
XFileV5 2.x.x
3. INSTALLATION
3.3.1.3
UNDER
UNIX
Creating an Environment
To create the above defined CATIA environment,
execute the XFileV5SetEnv.sh shell script.
Action
OS 1
Example
(1) Go to the installation
directory
*
cd /catdat/tcsoft/XFileV5_xxx
(2) Execute the script
*
./ XFileV5SetEnv.sh
Note:
1
2
* stands for e v e r y CATIA UNIX operation system
xxx stands for the current version number.
Rx stands for CATIA release number
ATTENTION:
To create a global environment, you must have the
administrator rights.
NOTE:
The CATIA—XFILEV5 icon (see the following screenshot) is
displayed in the my_CATIA folder of the Application
Manager only after re-log in.
Transcat PLM GmbH
11
XFileV5 2.x.x
3. INSTALLATION
3.3.1.4
UNDER
UNIX
Example of a C ATIA Environment File
!---------------------------------------------------------!
DASSAULT SYSTEMES - V5 ENVIRONMENT FILE
!---------------------------------------------------------! MODE : Global
! TYPE : CATIA
! TMSTMP : 1179298808
!---------------------------------------------------------CATEnvironment=/catiav5/R17/$OSDS:/catdat/tcsoft/XFileV5/load/$OSDS
CATInstallPath=/catiav5/R17/$OSDS:/catdat/tcsoft/XFileV5/load/$OSDS
LIBPATH=/catiav5/R17/$OSDS/code/bin:/catdat/tcsoft/XFileV5/load/$OSDS/code/bin:$LIBPATH
LD_LIBRARY_PATH=/catiav5/R17/$OSDS/code/bin:/catdat/tcsoft/XFileV5/load/$OSDS/code/bin:$LD_LIBRARY_PATH
LD_LIBRARYN32_PATH=/catiav5/R17/$OSDS/code/bin:/catdat/tcsoft/XFileV5/load/$OSDS/code/bin:$LD_LIBRARYN32_PATH
SHLIB_PATH=/catiav5/R17/$OSDS/code/bin:/catdat/tcsoft/XFileV5/load/$OSDS/code/bin:$SHLIB_PATH
CATICPath=/catiav5/R17/$OSDS/code/productIC:/catdat/tcsoft/XFileV5/load/$OSDS/code/productIC
CATCommandPath=/catiav5/R17/$OSDS/code/command:/catdat/tcsoft/XFileV5/load/$OSDS/code/command
CATDictionaryPath=/catiav5/R17/$OSDS/code/dictionary:/catdat/tcsoft/XFileV5/load/$OSDS/code/dictionary
CATDocView=/catiav5/R17/$OSDS/doc:/catdat/tcsoft/XFileV5/load/$OSDS/doc
CATReffilesPath=/catiav5/R17/$OSDS/reffiles:/catdat/tcsoft/XFileV5/load/$OSDS/reffiles
CATFontPath=/catiav5/R17/$OSDS/resources/fonts:/catdat/tcsoft/XFileV5/load/$OSDS/resources/fonts
CATGalaxyPath=/catiav5/R17/$OSDS/resources/galaxy:/catdat/tcsoft/XFileV5/load/$OSDS/resources/galaxy
CATGraphicPath=/catiav5/R17/$OSDS/resources/graphic:/catdat/tcsoft/XFileV5/load/$OSDS/resources/graphic:/catiav5/R17/$OSDS/resour
ces/graphic/icons:/catdat/tcsoft/XFileV5/load/$OSDS/resources/graphic/icons:/catiav5/R17/$OSDS/resources/graphic/figures:/catd
at/tcsoft/XFileV5/load/$OSDS/resources/graphic/figures:/catiav5/R17/$OSDS/resources/graphic/splashscreens:/catdat/tcsoft/XFile
V5/load/$OSDS/resources/graphic/splashscreens:/catiav5/R17/$OSDS/resources/graphic/symbols:/catdat/tcsoft/XFileV5/load/$OSDS/r
esources/graphic/symbols:/catiav5/R17/$OSDS/resources/graphic/textures:/catdat/tcsoft/XFileV5/load/$OSDS/resources/graphic/tex
tures
CATMsgCatalogPath=/catiav5/R17/$OSDS/resources/msgcatalog:/catdat/tcsoft/XFileV5/load/$OSDS/resources/msgcatalog
CATFeatureCatalogPath=/catiav5/R17/$OSDS/resources/featurecatalog:/catdat/tcsoft/XFileV5/load/$OSDS/resources/featurecatalog
CATDefaultCollectionStandard=/catiav5/R17/$OSDS/resources/standard:/catdat/tcsoft/XFileV5/load/$OSDS/resources/standard
CATKnowledgePath=/catiav5/R17/$OSDS/resources/knowledge:/catdat/tcsoft/XFileV5/load/$OSDS/resources/knowledge
CATStartupPath=/catiav5/R17/$OSDS/startup:/catdat/tcsoft/XFileV5/load/$OSDS/startup
CATW3ResourcesPath=/catiav5/R17/$OSDS/docs:/catdat/tcsoft/XFileV5/load/$OSDS/docs
CATReconcilePath=
USER_HOME=$HOME
CATReferenceSettingPath=
CATUserSettingPath=\$USER_HOME/CATSettings
CATCollectionStandard=
CATTemp=\$USER_HOME/CATTemp
CATMetasearchPath=/tmp
CATW3PublishPath=/tmp
CATSharedWorkbookPath=/tmp
CATErrorLog=\$USER_HOME/CATTemp/error.log
CATReport=\$USER_HOME/CATReport
CATDisciplinePath=
JAVA_HOME_aix_a=$JAVA_HOME
JAVA_HOME_aix_a64=$JAVA_HOME
JAVA_HOME_irix_a=$JAVA_HOME
JAVA_HOME_hpux_b=$JAVA_HOME
JAVA_HOME_solaris_a=$JAVA_HOME
JAVA_HOME=\$JAVA_HOME_$OSDS
CLASSPATH_JDBC_aix_a=
CLASSPATH_JDBC_aix_a64=
CLASSPATH_JDBC_irix_a=
CLASSPATH_JDBC_hpux_b=
CLASSPATH_JDBC_solaris_a=
CLASSPATH=\$CLASSPATH_JDBC_$OSDS:$CLASSPATH
PATH=/catiav5/R17/$OSDS/code/bin:/catdat/tcsoft/XFileV5/load/$OSDS/code/bin:/catiav5/R17/$OSDS/code/command:/catdat/tcsoft/XFileV
5/load/$OSDS/code/command:$JAVA_HOME/bin:$PATH
XFILEV5_PATH=/catdat/tcsoft/XFileV5
XFILEV5_LOAD=/catdat/tcsoft/XFileV5/$OSDS/code/bin
XFILEV5_ADMIN=/catdat/tcsoft/XFileV5/admin
XFILEV5_DOC=/catdat/tcsoft/XFileV5/doc
Transcat PLM GmbH
12
XFileV5 2.x.x
3. INSTALLATION
3.3.2
UNDER
UNIX
Extending an Existing C ATIA Environment
To extend an existing CATIA environment, with the XFILEV5 the shell scripts
XFileV5Env.sh or XFileV5Env.csh are delivered .
In the following, we give an extract of this file. Adapt in this file the passages marked gray
to your local XFILEV5 installation. For further information to this subject, please refer to the
following subchapters.
set +u
XFILEV5_PATH=/catdat/tcsoft/XFileV5
\export XFILEV5_PATH
XFILEV5_DOC=$XFILEV5_PATH/doc
\export XFILEV5_DOC
XFILEV5_LOAD=$XFILEV5_PATH/${OSDS}/code/bin
\export XFILEV5_LOAD
XFILEV5_ADMIN=$XFILEV5_PATH/admin
\export XFILEV5_ADMIN
XFILEV5CAA=$XFILEV5_PATH/${OSDS}
\export XFILEV5CAA
CATEnvironment=$XFILEV5CAA:$CATEnvironment
\export CATEnvironment
3.3.2.1
Adapting the Declarations to the Existing Directories
The values in the example file above are given only as an e x a m p l e ; please adapt them to
realities of your local installation.
Variable name
Explanation
XFILEV5_PATH
Path, where XFILEV5 is installed
XFILEV5_LOAD
Directory of the executable files
XFILEV5_ADMIN
Directory of the XFileV5.par for default settings
XFILEV5_DOC
Path, where the XFILEV5 documentation is situated
Transcat PLM GmbH
13
XFileV5 2.x.x
3. INSTALLATION
3.3.2.2
UNDER
UNIX
Starting C ATIA with the XF ILE V5 Environment
To integrate XFILEV5 in an already existing CATIA environment, you have to
start CATIA as follows:
Step
OS 1
Example
Set CATIA environment (here:
CATIA default environment)
*
. /home/root/CATEnv/CATIA_P3.V5R16.B16.sh
Set XFILEV5 environment
*
. /catdat/tcsoft/XFileV5_xxx/XFileV5Env.sh
Start XFILEV5
*
For Interactive Mode:
CNEXT
For Utility Mode:
TCAXFileV5UtilityMd
For Batch Mode:
TCAXFileV5BatchMd
(for options see XFILEV5 manual—
section “Batch Mode”)
2
Note:
1
2
* stands for e v e r y CATIA UNIX operation system
xxx stands for the current version number.
Rx stands for CATIA release number
Transcat PLM GmbH
14
XFileV5 2.x.x
4. ENVIRONMENT VARIABLES
4.
Environment Variables
This table contains the complete overview of all environment variables, which may be used
for XFILEV5.
Variable name
Explanation
 XFILEV5_DOC
Path, where the XFILEV5 documentation is situated
 XFILEV5_LOAD
Directory of the executable files
 XFILEV5_ADMIN
Directory of the XFILEV5.par for default settings
 XFILEV5_ENV
Name of the environment with PX1 license
 XFILEV5_DIRENV
Directory of the environment with PX1 license
 XFILEV5_TMP_DIR
Directory for packing files to be exported or
unpacking files to be imported
 XFILEV5_EXP_TARGET_DIR
Default target directory for export container file
 XFILEV5_IMP_TARGET_DIR
Directory target directory for imported unpacked documents
 I4LIB_VERB
LUM environment variable. It is recommended to set this
variable to YES when running XFileV5 in batch mode.
Transcat PLM GmbH
15
XFileV5 2.x.x
5. INSTALLATION
5.
LICENSE PASSWORDS
OF
Installation of License Passwords
TRANSCAT PLM uses for XFILEV5 the license system LUM , which is also used for CATIA
licensing. TRANSCAT PLM offers two types of licenses:
License type
Description
 Nodelock
License for o n e only computer (license bound to the CPU-ID)
 Concurrent
License is available in the n e t w o r k . A license server is needed.
NOTE:
A license can be entered:
 on a UNIX workstation only by the r o o t - u s e r ,
 on PC only by users, having administrator rights.
5.1
License Request
To ensure a fast and errorless processing of your license request, we ask you to request
your license on the following website:
http://www.transcat-plm.com/license
The CPU-ID will be output if you enter one of the following commands:
Platform
Command
Example of a CPU-ID
AIX
uname -m
009481814C00
AIX
on p5-Series
Workstations
/usr/opt/ifor/ls/bin 9481768C
/i4target -O
IRIX
(FLEXlm host ID)
lmhostid
HP-UX
(Permanent Target ID) /var/lum/i4target
6909b894
ffff28ea
SOLARIS
hostid
807fe3ee
WINDOWS (win32mac)
i4target
5DDE26F2
i4target -O
557cd770
i4blt –H s –N
cluster_name
9c1bb2a7e1a8.8d.41.d1.9c.4c
.00.00.00
LINUX
(MAC/LLA Address)
CLUSTER
Transcat PLM GmbH
16
XFileV5 2.x.x
5. INSTALLATION
5.2
LICENSE PASSWORDS
OF
Installation of Nodelock Licenses
In the nodelock file, the Nodelock password must be entered, using a text editor. The
nodelock file is situated platform-depending in one of the following directories:
IBM:
/var/ifor
HP:
/var/lum
SGI:
/var/lum
SUN:
/var/lum
WINDOWS 2000/XP:
c:\Documents and Settings\All
Users\Application Data\IBM\LUM
Enrolling a Nodelock license under UNIX
Action
OS 1
Entries
(1) Log in as root user
*
su – root
(2) Go to the password directory
AIX
IRIX
HP
cd /var/ifor
cd /var/lum
cd /var/lum
SUN
cd /var/lum
(3) Create or edit the nodelock file
*
vi nodelock
(4) Add new lines at the end (vi command)
*
<ESC>Go
(5) Enter the password text
*
(see text below the table)
(6) Save the file (vi command)
*
<ESC>wq
(7) Specify the file permissions
*
chmod 644 nodelock
* stands for e v e r y CATIA UNIX operation system
Inserting Password text
In the license e-mail from TRANSCAT PLM, you will find a text analog to that in the following
example:
Copy the following 2 lines into your nodelock file:
# TransCAT: TC-XFileV5, Version 1.x, gueltig bis 31.12.2037
7db765b90080.02.81.96.00.18.00.00.00 64tkq3wfzxi2gzci5j7t8p49keaa "" "1"
To enter the password in the file, copy these two lines beginning from the # sign (and
including it) to your nodelock file.
Transcat PLM GmbH
17
XFileV5 2.x.x
5. INSTALLATION
LICENSE PASSWORDS
OF
Enrolling a Nodelock license under WINDOWS
To enroll nodelock licenses under WINDOWS, open in the password directory (see on the
top of this chapter) the nodelock file with any editor (e. g. WordPad).
If no nodelock file does yet exist, it must be created with an editor. Insert in the
nodelock file the password text as described above for UNIX.
NOTE:
The nodelock file has n o name extension—
n e i t h e r under UNIX n o r under WINDOWS.
Most of editors automatically add to the file name an extension (e. g. .txt). If an extension has been added, it
must be deleted— otherwise the file will be inoperative.
5.3
Installation of Concurrent Licenses
Concurrent licenses are generated for a specific license-server and are bound to its
CPU ID.
The prerequisite is that a LUM license manager is installed, configured and active, so that
you can enter the concurrent password text. To enroll the license keys of the Concurrent
type, you can use: the i4blt command line interface (in all platform cases) or the Graphic
User Interface (since LUM version 4.6.5 for WINDOWS and all UNIX platforms, previous
LUM versions only for AIX and WINDOWS).
For detailed information see your LUM documentation—chapter 6 "Using License Use
Management Runtime" which is delivered with your operating system.
NOTE:
A license can be entered
 on a UNIX workstation o n l y by the r o o t u s e r ,
 on PC o n l y by users, having a d m i n i s t r a t o r r i g h t s .
The tools and entries for the license manager are located in the following directories:
Operating System
Directory
 IBM (AIX)
/usr/opt/ifor/bin
Transcat PLM GmbH
18
XFileV5 2.x.x
5. INSTALLATION
LICENSE PASSWORDS
OF
Operating System
Directory
 HP (HP-UX)
/var/lum
 SGI (IRIX)
/var/lum
 SUN (SOLARIS)
/var/lum
 WINDOWS (2000/XP)
X:\ifor\WIN\BIN
(X is the drive, on which LUM is installed)
Enrolling a Concurrent license
For the registration the following possibilities are available:
 Automatic registration
If you have got the license certificate as a t t a c h m e n t , we recommend the automatic
registration. In order to install the license, store the license file in a directory of your choice
on the LUM server. Then enter the following command:
Command
Description
i4blt –a -f filename
‚filename’ stands for to the path and name of the license file.
 Registration using the IMPORT function of the GUI i4blt version
After starting the GUI i4blt version, the license certificate file can be read in and registered by the means of the IMPORT function.
STEPS
(1) Start i4blt Tool
(2) Select Products menu item and
go to the single product ... submenu.
(3) In the Enroll Product window press the Import key
(4) In the following IMPORT window select the license certificate and
confirm with 'OK' .
(5) After the return to the Enroll Product window conclude the
registration pressing the OK button.
***
Transcat PLM GmbH
19
XFileV5 2.x.x
http://www.transcat-plm.com/
> Products > XfileV5
© TRANSCAT PLM GMBH, 2014