What changes does the CA Client Automation make when installing UNIX machines in /etc/profile and how can you prevent these changes from occurring during the installation?
search cancel

What changes does the CA Client Automation make when installing UNIX machines in /etc/profile and how can you prevent these changes from occurring during the installation?

book

Article ID: 24712

calendar_today

Updated On:

Products

CA Automation Suite for Data Centers - Configuration Automation CA Client Automation - Asset Management CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Remote Control CA Client Automation - Asset Intelligence CA Client Automation - Desktop Migration Manager CA Client Automation - Patch Manager

Issue/Introduction

This document details what changes the CA Client Automation install makes on UNIX and how to avoid the changes by configuring the response file prior to install. 

When DSM is installed on a UNIX machine, the following entry is added to /etc/profile:

test -r /etc/profile.CA && { CA_SECTION=all; export CA_SECTION; /etc/profile.CA; } # Added by Computer Associates

The DSM installation (irrespective of the agent being installed) writes to the /etc/profile to call the etc/profile.ca file. The profile.ca file is triggered every time a user logs on to the machine so that the following is accomplished:

  1. Check for the installed Ca Software components i.e. AMO Agent or SDO Agent etc

  2. Set the environment variable for the user profile so that the DSM Application specific commands like Caf stop/start/status, camstat, tngdts, etc., are available for execution.

Since /etc/profile file contains system wide environment settings and startup programs, all customizations that you put in this file will apply for the entire environment variable on your system. DSM software updates this file to set the environment variables for its applications by pointing it to /etc/profile.ca file.

Environment

CA Client Automation - All versions.

All Supported version of UNIX

Resolution

If writing to /etc/profile is not desired, you can try the following:

  1. Comment the lines in /etc/profile. This would cause that agent not to be triggered whenever the user logs onto the machine. In this case the Agent would have to be run manually.

  2. Change the response file with the following changes so that these entries are not made in the /etc/profile during the agent installation itself.

Modifying the response file:

In the response file of the agent, make the changes to the following line from '0' to '1'

ITRM_SETUP_SYS_PROFILE=1 to ITRM_SETUP_SYS_PROFILE='0 or 1'

Example:

ITRM_SETUP_SYS_PROFILE=1 to ITRM_SETUP_SYS_PROFILE=0

0 = False
1 = True

After making the above changes to the response file, point the installation to use the modified response file using the -r switch and the response file name i.e. '.rsp' file.

Example:

cd /cd_mount_point/SolarisProductFiles_sparc/agent ./installdsm -r install.rsp /RITRM_INST_CMDLINE=1 /RITRM_SERVER=myserver.mydomain /RITRM_MANAGER=mymanager.mydomain

This will prevent the installer from updating /etc/profile.

Powered by Wolken Software