Preparing Linux computers for Infrastructure Management
Perform the following tasks before launching the TrueSight Infrastructure Management installer on a Linux computer.
- The TrueSight Infrastructure Management Server and the Integration Service are not supported on the Solaris operating system. Only the Remote cell is supported on it.
- BMC recommends that you have a dedicated host computer for TrueSight Infrastructure Management and do not install any other applications on it.
- It is not recommended to install the PATROL Agent and the TrueSight Infrastructure Management server on the same Unix computer. The PATROL Agent startup scripts set some environment variables that prevent the TrueSight Infrastructure Management server from starting after the computer is restarted.
Ensure that the target computers for TrueSight Infrastructure Management meet or exceed the system requirements listed in System requirements and product compatibility for Infrastructure Management and in the following sections.
Ensure that port 80 is available for installing the Apache web server. If any other application is using the port, change the port allocation to make the port 80 available for TrueSight Infrastructure Management installation. On the system where you want to host the TrueSight Infrastructure Management Server or the Integration Service, verify the TCP control port (port 80) availability by running the following command from a command line:
After TrueSight Infrastructure Management has been installed, you can change the port for the Apache web server to free port 80 for use by your other application. For instructions, see Ports used by Infrastructure Management.
BMC Software recommends that you install TrueSight Infrastructure Management from a local copy of the installation image and not from a network drive. Installing from a network drive can cause delays in completing the installation.
For successful installation, ensure that the host name or the cluster name does not contain an underscore (_).
Disable any anti-virus software on each host computer on which you are installing a component, or exclude the TrueSight Infrastructure Management installation directory from virus scanning. Disable the following programs on the target computer:
Close all applications that are running and do not perform other installation or configuration activities during the TrueSight Infrastructure Management installation process.
You can install the TrueSight Infrastructure Management Server or the Integration Service as a root user as well as a non-root user. However, you must provide certain permissions to the non-root user as the root user.
If you are installing the TrueSight Infrastructure Management Server as a non-root user, ensure that the non-root user who installs the product has the home directory on the computer where the product is installed. Ensure that the user's home directory contains the user profile file. This is required for the
gzip and unzip
Ensure that gzip and unzip are installed and present in the PATH environment variable.
Ensure that tcsh shell is installed on the server where you plan to install TrueSight Infrastructure Management.
The installation script creates the installation directory during installation.
The directory where the TrueSight Infrastructure Management Server is installed and all its parent directories must have 755 permissions and must be owned by root, as well as the other group. Without these permissions and ownership, you will not be able to log into the TrueSight Infrastructure Management Server.
Do not install the Integration Service in the /usr directory.
Clean your temporary directories. Start with the temporary folder in your home folder. You may not be able to delete all the files, but BMC recommends that you remove any files or directories that begin with TrueSight or Infrastructure Management.
Configure your firewall to allow TCP port 7, which is used to communicate with other TrueSight Infrastructure Management hosts
|X Windows access|
Disable X Windows access control by using the xhost command.
|Nobody user account||Ensure that the nobody user account exists on the target computer.|
|ed Text Editor|
Ensure that the ed text editor exists on the computer where TrueSight Infrastructure Management will be installed.
Ensure that Arial fonts are present on the Linux OS on which you plan to install Infrastructure Management.
Steps for installing the fonts
Permissions required by a non-root user for installing the Integration Service and remote cell
On Linux computers, you can install the Integration Service as a root user as well as a non-root user. However, to enable non-root users to install the Integration Service, as a root user, you need to provide the following permissions to the the non-root user.
- Provide read, write, and execute permissions for the following directories:
- Installation directory (destination directory where you are planning to install the product)
- /opt/bmc directory to create ProductRegistry.xml file
- /etc/patrol.d directory to create patrol security
- /etc/init.d, /etc/rc.d/rc0.d, /etc/rc.d/rc1.d, /etc/rc.d/rc3.d, and /etc/rc.d/rc5.d directories to create service
- /tmp and /var/tmp directories
- Provide read and write permissions for the following files and directories:
- /etc/csh.cshrc file
- /etc/profile directory to set environment variable permission
- (Remote cell on AIX only) /home directory
- If the init file is not copied to the /etc/rc3.d directory, the Integration Service corresponding to the init file is not listed as installed (in the list of existing Integration Service installations) during installation of other integration services.
- Ensure that you remove the /etc/bmc.cshrc and /etc/bmc.profile files if they already exist.
Installing the Integration Service with the non-root user is supported only on the Linux operating system. It is not supported on the Solaris or AIX operating system.
Permissions required by a non-root user for installing TrueSight Infrastructure Management
On Linux computers, you can install TrueSight Infrastructure Management as a root user as well as a non-root user. However, to enable non-root users to install TrueSight Infrastructure Management, as a root user, you need to provide read, write, and execute permissions to the non-root user, for the following directories:
- Read, write, and execute permissions for the TrueSight Infrastructure Management installation (destination directory where you are planning to install the product) and /tmp directories.
- Verify the filesystem that the /tmp directory resides in is mounted with exec option by running the findmnt command. If it shows noexec for /tmp, remount it with exec option. For example, mount -o remount,exec /tmp.
/opt/bmc directory to create ProductRegistry.xml file
- /usr and /usr/bin directories to create softlink
- /tmp and /var/tmp directories
(For Oracle database only) /etc/profile
After completing the installation of TrueSight Infrastructure Management, you can revoke the permissions provided for the /etc/profile directory.
You can configure these permissions by running a script. For more information, see Configuring permissions required by a non-root user for installing Infrastructure Management.
When you run the script, in the /etc/security/limits.conf file, the following minimum limits are set for creating the number of files and processes.
<Non-root-User-Name> soft nofile 16096
<Non-root-User-Name> hard nofile 16096
<Non-root-User-Name> soft nproc 4096
<Non-root-User-Name> hard nproc 4096
- You can manually edit the limits.conf file to increase the limits. However, BMC recommends you to not reduce the limits. Unless these limits are set, you cannot upgrade TrueSight Infrastructure Management as a non-root user.
- While installing the TrueSight Infrastructure Management server as a non-root user, you need to change the port numbers for Apache and Apache SSL between 1025 to 65535 because the non-root user does not have permissions to use ports below or equal to 1024.
After configuring the permissions and changing the limits, you need to start a new session for the changes to take effect.
Configuring permissions required by a non-root user for installing TrueSight Infrastructure Management
To install TrueSight Infrastructure Management as a non-root user, as a root user, you need to provide a set of permissions. You can set these permissions by running the
config_nonroot.sh script as described in the following procedure.
You can also run this script for setting permissions for a non-root user while upgrading from a previous version of TrueSight Infrastructure Management.
- Locate the script at <Infrastructure-Management-Download-Location>/TSIMServer/Disk1/Utility.
- As a root user, run the script in the following format:
config_nonroot.sh <Non-root-User-Name> <Directory-Location>
In the preceding script syntax, the following definitions apply:
<Non-root-User-Name>refers to the non-root user to whom you want to provide permissions.
<Directory-Location>refers to the absolute path to the directory where you plan to install or upgrade the TrueSight Infrastructure Management product.
After setting the new permissions by running the script, you need to start a new session for the changes to take effect.
Preinstallation requirements check by installer
When you start the TrueSight Infrastructure Management Server installation, the installer checks to ensure that the target computer is configured based on the recommended settings. The installer checks the environment and reports a status of OK or Not OK for each configuration variable that it checks.
For Linux, the following preinstallation checks are run:
Checks whether this operating system is a supported Linux operating system.
Checks if the kernel version is according to the supported operating system.
Root [ / ] partition
Ensures that the root partition is not 100% full. The installation may fail if there is insufficient space available in the root partition.
Checks if BMC Impact Solutions components are present. If they are present, they must be uninstalled.
Verifies the IP address
Host names resolved IP against IP
Checks if the resolved IP for the host name matches the IP address
Checks whether DNS is configured on the system. This is required for DHCP support for the TrueSight Infrastructure Management Server.
Permissions on /tmp
Checks if /tmp directory has read, write, and execute permission for owner, group, and others
Checks if the gzip compression utility is present in the /usr/bin/gzip or /bin/gzip or /usr/local/bin/gzip path. Gzip is no longer shipped with TrueSight Infrastructure Management Server and is required for successful installation.
Checks if the gunzip compression utility is present in the /usr/bin/gunzip or /bin/gunzip or /usr/local/bin/gunzip path directory
Checks if the default gateway is configured
Checks whether the required ports are available. For the list of ports required, see Network port schematics for Infrastructure Management.
Note: If you are using a dual-stack computer, the preinstallation check for port availability may not be performed. Therefore, you must manually check for the availability of ports in case of dual-stack computers.
Available swap space
Checks if the computer has a minimum of 3 gigabytes of swap space available
File mode creation mask
Checks if the umask value is 022
Checks if the computer has a minimum of 4 gigabytes of memory available
Checks for mail configuration
Checks for required libraries. For information about the required libraries, see Installing the Infrastructure Management Server on Linux with SAP SQL Anywhere and Installing Integration Service on Linux and Remote Cell on Linux, IBM AIX, or Solaris.
If the installation program encounters a failed check on a mandatory setting, it aborts the installation. To resolve any failed checks, review the prerequisites in this page to ensure that you have implemented all of them. If all the prerequisites have been implemented and the preinstallation check still fails for some checks, see the Infrastructure Management installation and uninstallation issues.
Before installing TrueSight Infrastructure Management, disable the on-demand scan of the antivirus system.