000030131 - How to install RSA IMG 6.9.1 on a Red Hat 5 update 11 (5u11) or 6 update 6 (6u6) environment

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000030131
Applies ToRSA Product Set: Identity Management and Governance, RSA Via Lifecycle and Governance (L&G), Aveksa ACM
RSA Version/Condition: 6.9.1
Platform: RSA Soft-Appliance Installation
O/S Version: Red Hat 5 update 11 (5u11) and  6 Update 6 (6u6)

Note:  RSA IMG (aka Aveksa ACM) has been re-branded to RSA Via Lifecycle and Governance  (RSA Via L&G).

The application is sometimes referred to as IMG or ACM and now RSA Via L&G.   They are all the same product.
IssueIMG 6.9.1 was not initially certified to run on Red Hat  5 update 11 ( 5u11 )  nor on 6 update 6 ( 6u6 ).  
When attempting to perform an install/upgrade on these OS versions, the installation will fail and the error message below is shown.

ACM is not supported on this version of Linux

Additional testing has been performed since the initial release of IMG 6.9.1, and Red Hat 5u11 and 6u6 are now supported versions for a software or soft-appliance installation.  
Update:   RedHat 5u11 is now a supported OS for Hardware Appliances which have been updated using the rsaimg_updater.   6u6+ are currently supported for software appliances only.    Always refer to the current 6.9.1 Platform Support Matrix.
A updated OS Supported Versions Matrix PDF document is available on the RSA SecurCare Online portal.
TasksThis article provides instructions on how to allow the install/upgrade of IMG 6.9.1 to occur on Red Hat 5u11 and 6u6.  
The instructions should not be used for any other IMG version other than 6.9.1.  These instructions should only be used for a software appliance.
Resolution

To allow Red Hat 5u11 and 6u6 to be used for an IMG 6.9.1 installation or upgrade, two (2) installation script files need to be modified on the Aveksa Linux server before the installation process is started.
The two files and their edits are shown below.  Copies of these files should first be made before making changes and saving any edits.
It is assumed that the default location of the staging installation directory is /tmp/aveksa/staging.  If a non-default location is used, the directory path noted in these examples should be adjusted accordingly. 
Note:  There may be times when patches may overwrite existing default installation files.  If this happens, it is appropriate to re-edit these files and re-implement the changes noted below.
In these examples, the Linux file editor vi was used.  Any editor compatible with Linux can be used.  Also note that the leading line numbers shown here are not normally visible in a file.  They are noted here for clarity and were displayed by using the 'set number' command option in the Linux vi editor.   For example, to display line numbers of a Linux file when using vi, upon initial execution of vi, before typing anything on the keyboard type : and at the : (colon) prompt, type set number and hit the <Return> key.  Line Numbers will then be displayed.
 


  1. Two changes should be made to the /tmp/aveksa/staging/deploy/common.sh script.
    Below is a snippet of lines 187 through 197.
    187 checkLocalOracleAllowed() {
    188         if [ -f /etc/redhat-release ]; then
    189                 cat /etc/redhat-release > /tmp/install.tmp
    190                 while read line ;do
    191                         for vers in $line
    192                         do
    193                                 case "$vers" in
    194                                 "5.8"|"5.10"|"6.4"|"6.5" )
    195                                         localOracleAllowed="yes"
    196                                         break
    197                                         ;;

    Line 194 needs to be changed to include 5.11 and 6.6.
    194                                 "5.8"|"5.10"|"5.11"|"6.4"|"6.5|"6.6" )

    Below is a snippet of lines 230 through 237.
    230         #### Check OS Release Version
    231         if [ -f /etc/redhat-release ]; then
    232                 cat /etc/redhat-release > /tmp/install.tmp
    233                 while read line ;do
    234                         for vers in $line
    235                         do
    236                                 case "$vers" in
    237                                 "5.3"|"5.8"|"5.10"|"6.1"|"6.2"|"6.3"|"6.4"|"6.5" )
    238                                         acmInstallAllowed="yes"
    239                                         break

    Line 237 needs to be changed to include  both 5.11 and 6.6.
    237                                 "5.3"|"5.8"|"5.10"|"5.11"|"6.1"|"6.2"|"6.3"|"6.4"|"6.5"|"6.6" )

     
  2. One change should be made to  the /tmp/aveksa/staging/deploy/install.sh script.
    Below is a snippet of lines 791 through 797.
    790 if [ -f /etc/redhat-release ]; then
    791         # RedHat
    792         if [ $IS64BIT = Y ]; then
    793                 # 64-bit
    794                 rpm -q sysstat >>/tmp/ip1
    795                 rpm -q libXp >>/tmp/ip1
    796                 rpm -q libaio >>/tmp/ip1
    797         fi

    Line 795 needs to be changed to by adding a # sign at the begining of the line to comment out this option:
    795                # rpm -q libXp >>/tmp/ip1


Once the three changes listed above are made, the documented installation process as noted in the 6.9.1 Installation Guide, and the 6.9.1 Upgrade guide,  is now possible for Red Hat 5u11 and 6u6.
If you are unsure of any of the steps above or experience any issues, contact RSA Support and quote this article number for further assistance.

NotesInformation regarding RedHat 5u11 on a hardware appliance can be found in the article below.
Problems with uninstall.sh and install.sh after applying rsaimg_updater P03 or higher for RSA Via L&G 6.9.1 on hardware appliance running RedHat OS

Attachments

    Outcomes