Requirements for installing on Linux using the unified product installer

Default shell 

Bash UNIX shell must be the default shell on all machines that that TrueSight Server Automation is being installed.

Firewalls

Ensure that your firewall allows communication on all ports used by various components of TrueSight Server Automation. For more information on ports, see TrueSight-Server-Automation-ports.

Perl

Ensure that you have a supported version of Perl installed on the host computer on which you are installing TrueSight Server Automation. (For information about the Perl versions that TrueSight Server Automation supports, see Perl support.) Perl is required to access the Network Shell Perl modules installed with the Network Shell installation.

 If the host computer on which you are installing TrueSight Server Automation has:

• A supported version of Perl installed — The Network Shell installation automatically installs the Network Shell Perl module.
• An unsupported version of Perl installed — The installation copies files that allow you to install the Perl module after you have installed the supported version of Perl.

Permissions

• Verify that the umask is 0022 for the root users on the Application Server host computer.

• TrueSight Server Automation might have many open files at any given point in its operation. Therefore, unless your environment has specific needs for a more restrictive setting (depending on the specific operation of the Application Server), BMC recommends that you set the following operating system parameters for the bladmin user in /etc/security/limits.conf file (or add a /etc/security/limits.d/<file>.conf file):
  

  bladmin - nofile 8192

  bladmin - nproc 8292
  As needed, you can adjust the hard and soft limits if you do not have enough available file descriptors to proceed, for example, the open files to 65536. For more information, see Too-many-open-files-and-Java-out-of-memory.

• The Linux file system partition to which you plan to install the Default Application Server must not be mounted with the nosuid option.

Separate file server

If you plan to install a separate file server, ensure that you have performed the following prerequisite tasks:

• The unified product installer automatically installs the RSCD agent on the separate file server during installation. However, you can manually install the RSCD agent on your separate file server, as described in Installing-the-RSCD-agent-Windows or Installing-only-the-RSCD-agent-Linux-and-UNIX.
• If the Application Server is running on Linux, the unified product installer can only install the RSCD agent on a separate file server that is also running on Linux. If the separate file server is running on Windows, you must manually install the RSCD Agent based on the procedures in Installing-the-RSCD-agent-Windows.

Security

The unified product installer needs to be run by a super user — root or a root-equivalent user on Linux. This enables the installer to install components on the Application Server and File Server.

By default, the unified product installer configures the RSCD agent on the file server to map incoming connections to the Administrator or root user. The following mapping is added to the exports file:

This mapping allows any server (as root) user, access to the file server. BMC recommends to use <Application_Server_ip> rw,user=[root] in the exports file.

Note: The initial account used for mapping incoming connections to the file server must be a local account.

If you do not want to map the connections to the root user, you can manually modify the exports file to suit your needs. The exports file is located at the following path, BSA<version_number>-<platform>\files\installers\other_files\maintenance_scripts.zip\linux\. For more information, see Configuring the exports file. Alternatively, you can manually install the RSCD agent on the separate file server, see Installing-only-the-RSCD-agent-Linux-and-UNIX.

Shared library

• Linux platforms on which you plan to install the Application Server or Network Shell must have the appropriate version of libtermcap.so.2 and libtermcap.so.6 shared library installed. Install the shared library before installing these components. For more information, see Requirement for installing the Application Server, TrueSight Server Automation Console, or Network Shell on Linux.
• If you are using the RedHat offline patch downloader, ensure that the glibc.i386 or glibc.i686 library is present (due to the embedded JRE version 1.8).
  
  

Software and hardware

• Ensure that your machine meets the minimum software and hardware requirements as described in Minimum-software-requirements and Minimum-hardware-requirements.
• You must have an X Window display system installed and configured on your Linux machine.
• Ensure that you have set up a database for use by TrueSight Server Automation, as discussed in Setting-up-an-Oracle-database-for-TrueSight-Server-Automation and Setting-up-a-SQL-Server-database-and-user-for-TrueSight-Server-Automation.

Temp space

Ensure that you have at least 4 GB of /tmp space for Linux installs.