Requirements for installing individual components on UNIX and Linux

This topic describes the requirements for installing TrueSight Server Automation on on UNIX and Linux platforms.

The topic includes the following sections:

Requirements for installing product components on UNIX and Linux

You can also use the individual product installers to install single components.

Component	Requirements
All	The referenced document [xwiki:Automation-DevSecOps.Server-Automation.TrueSight-Server-Automation.Planning.System-requirements.Minimum-software-requirements.WebHome] was not found.
Application Server (with NSH and agent)	Linux platforms on which you plan to install the Application Server or Network Shell must have the appropriate version of libtermcap.so.2 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. The UNIX or Linux file system partition to which you plan to install the Application Server must not be mounted with the nosuid option. Set the umask for the root user to 0022 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 ensure that the following operating system parameters are set for the bladmin user. These settings should be permanently set for the user (for example, in the /etc/security/limits.conf file for Linux): Set core files to unlimited. Set the number of open file descriptors to 8192 Optionally, set the INSTALL_FILES_TEMP environment variable to a valid, writable directory. If this variable is set, the installer files are stored in that location, thereby reducing the disk space requirements for /tmpduring the installation. Enter the following commands at the operating system command line: INSTALL_FILES_TEMP=<temporaryDirLocation> export INSTALL_FILES_TEMP For more information, see Methods for reducing installation space on Linux and UNIX.
Agent only	Optionally, set the INSTALL_FILES_TEMP environment variable to a valid, writable directory. If this variable is set, the installer files are stored in that location, thereby reducing the disk space requirements for /tmp during the installation. At the operating system command line, enter the following commands: INSTALL_FILES_TEMP=<temporaryDirLocation> export INSTALL_FILES_TEMP For more information, see Methods for reducing installation space on Linux and UNIX.
File server	The referenced document [xwiki:Automation-DevSecOps.Server-Automation.TrueSight-Server-Automation.Installing.Installing-individual-components.Configuring-the-file-server.File-server-requirements.WebHome] was not found.
NSH only	Linux platforms on which you plan to install the Network Shell must have the libtermcap.so.2 shared library installed. Install the shared library before installing the Network Shell. For more information, see Requirement for installing the Application Server or Network Shell on Linux.

Required ports for installers

Note the following port-related information prior to installing TrueSight Server Automation:

Before you install the TrueSight Server Automation Console, make sure that port 9998 (TCP) is not being used. Installation of the console requires use of this port. If the port is already in use, the installer shows a progress bar but exits before launching and the installation fails.
For the UNIX agent installer, use either ssh or ftp/telnet to run the agent installer. Only the ports for the specific method of install need to be open.

For more information, see TrueSight-Server-Automation-ports.

Supported platforms for native installers

For several Linux and UNIX platforms, you can choose between a shell-based (.sh) installer and a native installer (.bff for AIX, .rpm for Linux, or .gz for Solaris). You might prefer to use the native installer, for example, to install in bulk.

Where to go from here

Installing-individual-components