Minimum software requirements

The following sections describe software requirements for installing components of a  system:

Application Server tuning parameters for Linux

Most Linux and Solaris systems have fairly low settings for the number of files that a user can have open, as well as the number of processes that they can run.  These settings should be increased from the default values for the bladmin user. The Application Server startup script will attempt to set an open file and process limit of 8192.  This requires that the operating system configuration be adjusted to allow these values.  For example, in Redhat Linux, you can add the following settings to the /etc/security/limits.conf file.

Restart the application server service to ensure that the new settings are picked up.

RSCD tuning parameters for UNIX

Due to the use of setuid for Impersonation-and-privilege-mapping on the Unix RSCD agent, you might need to either change the configuration of the Pluggable Authentication Modules (PAM) mechanism so that setuid calls can read the limits values for mapped users, or increase these limits for the root user. This might be required if the Application Server is running on the same host as the file server.

Supported databases

The  product supports the following database types and versions:

Data Warehouse requirements

This section describes the requirements for installing and using  in your  environment.

• The version and service pack of  used in your environment should be the same or higher than the version and service pack of  that you are using. For a list of  versions supported for use with , see Compatibility matrix.

• The character set of the schema types for  must match the character set of schema types for . For example, if the  core database uses LATIN-1, the data warehouse must use the same character set or its subset character set. If the  core database uses AL32UTF8, the data warehouse must use the same character set or its subset character set.
•  does not support collation with case-sensitive database schema. If the  database has collation with case-sensitive database schema, the database does not work with .
• The database password should not begin with an equal sign (=). If the password begins with an equal sign, installation of  cannot proceed until the password is changed.
• If you modify the  database details (for example: server name, SID, or password), you must change the  site context to use the modified details. To change the site context, use the  Console.

Installation requirements

The following sections highlight specific installation requirements.

• Requirements for libraries and files when installing on Red Hat Linux using UPI
• Requirements for package when installing RSCD Agent on Red Hat Linux 
• Requirement for libtermcap when installing the Application Server or Network Shell on Linux
• Requirement for RPM resource when installing the RSCD agent on SuSE 15
• Requirements for packages when installing RSCD Agent on AIX

Requirements for libraries and files when installing on Red Hat Linux using UPI

To install TrueSight Server Automation on Red Hat Linux using the unified product installer (UPI), you must have the following items installed:

Requirements for package when installing RSCD Agent on Red Hat Linux

• For the installation of RSCD Agent on Red Hat Linux (RHEL), the libstdc++ package is required.
• For the installation of RSCD Agent on RHEL 9, the following packages are required:
  • chkconfig
  • libxcrypt-compat

Requirement for libtermcap when installing the Application Server or Network Shell on Linux

For the installation of several TrueSight Server Automation components on Red Hat Linux (RHEL), the libtermcap library is required. Further details regarding this library depend on the version of RHEL.

Requirement for RPM resource when installing the RSCD agent on SuSE 15

For the installation of an RSCD agent on SuSE 15 platform, the insserv-compat rpm package is required.

Requirements for packages when installing RSCD Agent on AIX

For the installation of RSCD Agent on AIX, the following packages are required. These packages are usually available under Aix Toolbox Software.

• libstdcplusplus10
• libgcc10

Once the packages are installed, create the symbolic links as shown below:

• ln -s /opt/freeware/lib/gcc/powerpc-ibm-aix7.1.0.0/10/libstdc++.a /opt/freeware/lib
• ln -s /opt/freeware/lib/gcc/powerpc-ibm-aix7.1.0.0/10/libgcc_s.a /opt/freeware/lib

Supported version of script programming languages

Installation of Perl module

TrueSight Server Automation provides integrated support for the Perl script programming language. This section lists operating systems and corresponding Perl support.

The TrueSight Server Automation Perl module integrates with libnc, the core library for TrueSight Server Automation, which functions like a network-enabled version of libc. Because of this integration, you can use Perl scripts to perform functions on remote hosts (such as open, read, and write files) as long as those hosts are running RSCD agents.

When you install Network Shell on a platform that can support a TrueSight Server Automation Application Server, the Perl module of TrueSight Server Automation is automatically installed. The TrueSight Server Automation Perl module is compatible with the versions of Perl listed in the following table: 

Note the following considerations for the TrueSight Server Automation Perl module:

• The NSH.pod file shipped with the TrueSight Server Automation Perl module is incorrectly formatted. This file is not a POD file, but a MAN file. Therefore, you cannot open it using POD type help. You can use the man command to access the help.
• When you are installing Network Shell, if the installer does not find a supported version of Perl on the server, the installer stores the files needed for the Perl module in the TrueSight Server Automation installation directory. You can use these files to install and configure Perl at a later time.

Supported PowerShell versions

TrueSight Server Automation 8.9.04 and later supports integrated PowerShell script execution for PowerShell 4.0 and later. For information about system requirements for PowerShell 4.0, see herein the Microsoft documentation. 

Patch management requirements for specific platforms

The following sections highlight requirements for implementing patch management on specific platforms.

Linux patch requirements

To run patching jobs, ensure that the libnsl.so.1 library is installed on the RHEL targets.

Virtualization support

You can use the Servers workspace in TrueSight Server Automation to manage the virtual infrastructure of the platforms shown in the following table.

If you are implementing TrueSight Server Automation in a virtual environment, review the requirements and instructions outlined in Setting-up-TrueSight-Server-Automation-for-virtual-environments.

Related topic

Minimum-hardware-requirements