Problem

As part of the installation process, the Unix install.sh will ask for the full name of the license file. Can a relative path be used in this instance?

Resolution

No, an absolute path needs to be used in this situation as well as the full name of the license file.

If the following is entered then the license file will not be found and this may cause the installation to terminate:

            ../v1209_Lics/XBIS-Linux-Intel-32b-ID96117.lic

Instead the following needs to be entered:

                /install_area/12_09_32bit/v1209_Lics/XBIS-Linux-Intel-32b-ID96117.lic

The reason is that within the install process, the current directory can be changed from the directory that the install process was started from. This means that an absolute path name needs to be used when specifying the license file as the use of a relative path name (to the install directory) will not locate the license file.

An example of the error that can be reported is:

LicVerify for Linux Intel 32-Bit platform code 070

LicVerify: error 0xc1000002 (License file not found.) opening license

certificate file: ../v1209_Lics/XBIS-Linux-Intel-32b-ID96117.lic

Usage:

licverify license-file install-dir version {license-name | version} ...

Where:

     license-file is the license file to open.

     install-dir is the directory into which to install the license.

     license-name is the license within the file to open.

     version is the full version number of the license-names following

         the version argument being installed. Version is distinguished

         from license-name by beginning with a numeric character.

         License vault [/usr/local/liant/bis/bin/license.vlt] creation was not

         successful. Installation cannot continue.

If this occurs, then the RM has only partially been installed and it needs to be de-installed and then the installation needs to be rerun.

In the situation where the product has installed, but will not run please refer to the following wiki:

Is it possible to use a RM product if the license failed to be applied as part of installation process?

Incident #2684542