Revision history

1. Install may be done in either of 2 ways
   
   
2. Via the install script wrapper provided.
   If invoking via the install script, run: install <absolute installpath>
   
   where: <absolute installpath> is an optional argument.
   
   If $CASHCOMP is defined in the user environment, the installpath will be ignored. If $CASHCOMP is not defined and installpath is not provided then /opt/CA/SharedComponents will be assumed as the default value of installpath.
   
   In this case, the rpm file must be in the same directory as the install script.
   
   
3. Directly from the command line
   
   First, the value of CASHCOMP must be obtained. This must be done by sourcing either /etc/profile.CA or /etc/csh_login.CA.
   
   The following usage is required if $CASHCOMP is defined:
   
   rpm -U --replacefiles --replacepkgs --prefix $CASHCOMP ca-lic-01.0062- 0007.<arch>.rpm
   
   The following usage is required if $CASHCOMP is not defined and a non-default install location is desired:
   
   rpm -U --replacefiles --replacepkgs --prefix <path> ca-lic-01.0062- 0007.<arch>.rpm
   
   The following usage is required if $CASHCOMP is not defined and the default install location /opt/CA/SharedComponents is desired:
   
   rpm -U --replacefiles --replacepkgs ca-lic-01.0062-0007.<arch>.rpm
   
   where: <path> is any directory other than the root directory. <arch> is the hardware architecture of the target machine (i386, ia64, or s390).
   
   
4. The following pre-requisites are noted:
   Linux Intel:
   Architecture: Linux for Intel or Itanium 64-bit
   Devices: Any TCP/IP supported network connection
   Prerequisites: glibc 2.x
   Linux kernel: 2.4.x
   
   Linux for s390:
   Architecture: Linux for S/390 and zSeries in 31 bit mode
   Devices: Any TCP/IP supported network connection
   Prerequisites: glibc 2.x
   Linux kernel: 2.4.x



5. Upgrade on Linux
   
   When upgrading from version 1.90.03 or earlier, several CA License folders and symbolic links may be incorrectly deleted by the installer script. This issue can cause products to stop functioning properly. To avoid this issue,  one should first backup important CA License files, then uninstall the old version of CA License, and finally install the new version (1.90.04 or later). Below are the detailed steps.
   
   STEPS:
   
   
   1. First, take backups of the ca.olf file and the lic98.dat file.
   2. Uninstall the existing/old version of CA License. Refer section 6.
   3. Perform the installation of CA License 1.90.04. Refer section 2 or 3.
   4. Confirm the successful installation of 1.90.04. Refer section 7.
   5. Replace the existing ca.olf file and lic98.dat file with the files backed up in step 1.



6. Uninstall on Linux/Unix
   
   Uninstallation on Unix can be done by invoking a uninstaller script 'rmlicense' residing in the CA Licensing installed folder(i.e. $CASHCOMP/ca_lic folder).
   
   Where as uninstallation on Linux can be done in 2 ways:
   
   
   1. Either logon to the system as root and then on the console type 'rpm -e --nodeps ca-lic'.
   2. Or by invoking a uninstaller script 'rmlicense' residing in the CA Licensing installed folder(i.e. $CASHCOMP/ca_lic folder).
      
      
7. Check for successful installation
   
   A successful installation can be verified by invoking the script 'lic98version' residing in the CA licensing folder (i.e. $CASHCOMP/ca_lic folder). The 'lic98version' generates a 'lic98version.log' file which contains the versioning info along with the CA Licensing utilities installed.
   
   In case of an failed installation an appropriate error message is outputted to the console. Refer the README inside the CA Licensing standalone package.