What is the significance of the new Environment Variable introduced in CA APM for SSO?
APM SSO 13.1 has a brand new installer built using InstallAnywhere. It is not rpm-based anymore
As a result, customers will have the exact same experience whether installing on Windows or Linux
CA APM 10.7
CA APM for SSO 13.1
The older version of APM for SSO was an rpm-based installer which required root privileges. With CA APM for SSO 13.1 a new and flexible installer is introduced.
This is based on Infrastructure Agent introducing a new environment variable
Once APM SSO 13.1 is installed, it is mandatory to immediately export this variable
The default install folder for APM SSO is /<user_home>/CA_APM_SSO_13.1.0
So, the variable is set as follows:
The variable may be saved in the bash profile of the user to avoid being exported each time. This requires root permissions.
For the logpath variable, the user who is setting the variable in a location where the path is being set should have the same permissions as the where Siteminder SSO has been installed
If Siteminder SSO has been installed in /home/CA/siteminder, the user setting the logpath variable needs to have read, write, execute permissions for home folder
Failure to do these will result in installation errors.