CA Harvest client.tar on AIX not extracting scripts in client/bin folder
Article ID: 411573
Updated On:
Products
Issue/Introduction
We have an issue in test environment where we install the client.tar but script files are not getting created under bin directory.
Environment
Harvest SCM all versions
Linux/Unix/AIX environments
Cause
Though the standard and default way to install SCM is to install all components to the same $CA_SCM_HOME folder, this customer had installed SCM Agent software to one folder, and SCM Client software to a different folder. The way the setup.sh script works is that it will look in the $CA_SCM_HOME/lib folder and generate scripts for the bin folder corresponding to the executables it finds there. In this situation, we found that $CA_SCM_HOME was set to the SCM Agent's home folder, so the setup.sh script was only generating scripts for the bin folder corresponding to the three executables that are delivered when installing the SCM Agent. None of the script for the client command line utility executables were getting created.
Resolution
We reset $CA_SCM_HOME to the SCM Client's home folder and re-ran setup.sh. This time, the scripts for all the client command line utility executables were created in the $CA_SCM_HOME/bin folder as expected.
Additional Information
Installation information for Harvest SCM on the Linux and Unix platforms can be found here: Install CA Harvest SCM on UNIX, Linux, and zLinux
Feedback
