Minimum software requirements
The following sections describe software requirements for installing components of a BMC Server Automation 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 5 you can add the following settings to the /etc/security/limits.conf file.
bladmin - nofile 8192 bladmin - nproc 8292
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.
Console requirements for UNIX
To run the BMC Server Automation Console and the Post-Install Configuration wizard on UNIX, the OS-specific x11 libraries for the supported variants of UNIX are required.
The BMC Server Automation product supports the following database types and versions:
|Database type||Supported versions|
Enterprise Edition (EE) and Standard Edition (SE):
(not recommended for production setup) Express Edition (XE)
The following databases do not have support for IPv6 in BMC Server Automation:
If you plan to use Oracle version 126.96.36.199 as the database for BMC Server Automation, before you install BMC Server Automation, you must install the appropriate patch to Oracle 188.8.131.52:
To determine if this patch is installed on your Oracle 184.108.40.206 database:
|Microsoft SQL Server|
BMC Decision Support for Server Automation requirements
This section describes the requirements for installing and using BMC Decision Support for Server Automation in the BMC Server Automation system.
- The version and service pack of BMC BladeLogic Decision Support for Server Automation used in your environment should be the same or higher than the version and service pack of BMC Server Automation that you are using. For a list of BMC Server Automation versions supported for use with BMC Decision Support for Server Automation, see BMC Server Automation requirements in the BMC Decision Support for Server Automation documentation.
- The character set of the schema types for BMC BladeLogic Decision Support for Server Automation must match the character set of schema types for BMC Server Automation. For example, if the BMC Server Automation core database uses LATIN-1, the data warehouse must use the same character set or its subset character set. If the BMC Server Automation core database uses AL32UTF8, the data warehouse must use the same character set or its subset character set.
- BMC Decision Support for Server Automation does not support collation with case-sensitive database schema. If the BMC Server Automation database has collation with case-sensitive database schema, the database does not work with BMC Decision Support for Server Automation.
- The BMC Server Automation database password should not begin with an equal sign (=). If the password begins with an equal sign, installation of BMC BladeLogic Decision Support for Server Automation cannot proceed until the password is changed.
- If you modify the BMC Server Automation database details (for example: server name, SID, or password), you must change the BMC Decision Support for Server Automation site context to use the modified details. To change the site context, use the BMC Decision Support for Server Automation Console.
The following sections highlight specific installation requirements.
Requirements for libraries and files when installing on Red Hat Linux using UPI
To install BMC Server Automation on Red Hat Linux using the unified product installer (UPI), you must have the following items installed:
|File type||Specific details|
|32-bit library files (.i386 or .i686 extension)|
|64-bit library file (.x86_64 extension)||libtermcap.so.6 or compat-libtermcap|
|Red Hat Package Manager (RPM) file|
Ensure that you have a recent version of this RPM installed. However, ensure that you are not using version 3.2.8-33.
Requirement for libtermcap when installing the Application Server, BMC Server Automation Console, or Network Shell on Linux
For the installation of several BMC 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 RedHat Enterprise Linux (RHEL) version 5
If you plan to install the Application Server, the BMC Server Automation Console or the Network Shell on Linux, ensure that the libtermcap.so.2 shared library (and libtermcap.so.6 shared library in case of unified product installer) is installed. To determine if termcap is installed, run the following command:
rpm -qa | grep libtermcap
If this command does not return
libtermcap-xxx, install the library from installation media or download and install it from a trusted gnu distribution site.
The libtermcap.so.2 shared library you install depends on the platform of the Application Server, the BMC Server Automation Console or the Network Shell you are installing. If you are installing the:
- 32-bit version of these components on a 64-bit operating system--Install the 32-bit version of libtermcap.so.2.
- 64-bit version of these components on a 64-bit operating system--Install the 64-bit version of libtermcap.so.2.
Requirement for RHEL 6
In RHEL 6 the package name has changed to compat-libtermcap. To install compat-libtermcap on Red Hat version 6, you can use one of the following commands:
- If you have YUM installed and configured:
yum install compat-libtermcap
- If you have the RPM package (available from the installation CD):
rpm -Uvh compat-libtermcap-2.0.8-49.el6.x86_64.rpm
Requirement for RHEL 7
In RHEL 7, libtermcap is no longer available, and you must create a link to libtinfo instead. Use the following command:
ln -s /lib64/libtinfo.so.5 /lib64/libtermcap.so.2
If libtinfo is not available on your system, obtain it by installing the ncurses-libs package.
Installation of Perl module
BMC Server Automation provides integrated support for the Perl script programming language. This section lists operating systems and corresponding Perl support.
The BMC Server Automation Perl module integrates with libnc, the core library for BMC 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 BMC Server Automation Application Server, the Perl module of BMC Server Automation is automatically installed. The BMC Server Automation Perl module is compatible with the versions of Perl listed in the following table:
Supported Perl versions
Supported version of Perl
Microsoft Windows: versions 2008 R2 SP1, 2012, and 2012 R2
ActiveState Perl 5.16
|Oracle Enterprise Linux: versions 5.5, 6.x, and 7.x||Available on demand from Support|
Red Hat Linux: versions 5.5, 6.x, and 7.x
Available on demand from Support
SUSE Linux Enterprise Server: versions 11.x and 12.x
Available on demand from Support
Note the following considerations for the BMC Server Automation Perl module:
- The NSH.pod file shipped with the BMC 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
mancommand to access the help.
- If you are using Perl in conjunction with the BMC Server Automation Console, you must configure the Application Server so it knows the location of Perl, as described in Configuring Perl.
- 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 BMC Server Automation installation directory. You can use these files to install and configure Perl at a later time. For information about installing BMC Server Automation's Perl module manually, see Manually installing the Perl module.
Patch management requirements for specific platforms
The follow sections highlight requirements for implementing patch management on specific platforms.
Citrix patch requirements
To avoid JVM memory allocation issues, you must install a patch on Citrix Presentation Server 4.5 (32-bit) before installing the RCP client (BMC Server Automation Console) on that platform.
For information on obtaining and applying the patch, see the article on the Citrix Support site: http://support.citrix.com/article/CTX115868.
Solaris 10.0 patch requirements
Solaris 10.0 requires Patch 120460-19 (or later) before you install the RCP client (BMC Server Automation Console) on that platform. The patch installs the latest Solaris gnome base libraries that the platform needs for remote display of the BMC Server Automation Console using XServer. For information about obtaining and applying the patch, see the Oracle Sun website.
The following table lists the third-party software versions shipped with BMC Server Automation.
|BMC Server Automation |
|OpenSSL||Java Runtime Environment (JRE)*||Apache Tomcat Web server|
Shavlik SDK version
|Microsoft Visual C++ Redistributable|
|8.9.02 (service pack 2)||1.0.2j||1.8.0_152 (JRE 1.8 Update 152)||8.5.20||9.1.1037.0||Microsoft Visual C++ 2015 Redistributable Update 3|
8.9.01.001 (patch 1)
|1.0.2j||1.8.0_152 (JRE 1.8 Update 152)||8.0.22||9.1.1037.0||Microsoft Visual C++ 2005 Redistributable|
|8.9.01 (service pack 1)||1.0.2j||1.8.0_121 (JRE 1.8 Update 121)||8.0.22||9.1.1037.0||Microsoft Visual C++ 2005 Redistributable|
|8.9.00 (base version)||1.0.2f||1.8.0_102 (JRE 1.8 Update 102)||8.0.22||9.1.1037.0||Microsoft Visual C++ 2005 Redistributable|
|8.8.00.001 (patch 1)||1.0.2j on most platforms|
1.0.2f on Windows 32-bit
|1.8.0_71 (JRE 1.8 Update 71)||8.0.22||9.1.1037.0||Microsoft Visual C++ 2005 Redistributable|
|8.8.00 (base version)||1.0.2f||9.1.1037.0||Microsoft Visual C++ 2005 Redistributable|
|8.7.00 (base version)||0.9.8zg||1.8.0_45 (JRE 1.8 Update 45)||8.0.22||9.1.1037.0||Microsoft Visual C++ 2005 Redistributable|
|8.6.01.002 (service pack 1, patch 2)|
1.7.0_71 (JRE 1.7 Update 71)
Required by Application Server and RCP client.
Provides for the WebServices and hosts Dashboard page.
|8.0.87||Microsoft Visual C++ 2005 Redistributable|
|8.6.01 (service pack 1)||0.9.8zc||8.0.87||Microsoft Visual C++ 2005 Redistributable|
|8.6.00.001 (patch 1)||8.0.43||Microsoft Visual C++ 2005 Redistributable|
|8.6.00 (base version)||8.0.43||Microsoft Visual C++ 2005 Redistributable|
* BMC Server Automation installs multiple JREs for use by different product components. These JREs are installed in the following directories:
NSH/br/java: Used by the Application Server
- NSH/jre: Used by the Console
- NSH/jre-32: Additional JRE used by a Console on a Windows 64-bit machine, to enable use of Cygwin (which is always 32-bit)
To browse and view details about the software applications discovered by BMC Atrium Discovery and Dependency Mapping, see Browsing discovered software applications.
You can use the Servers workspace in BMC Server Automation to manage the virtual infrastructure of the platforms shown in the following table.
For requirement information, see
VMware vCenter environment
Solaris Zones environment
IBM Frame environment
Microsoft Hyper-V environment
If you are implementing BMC Server Automation in a virtual environment, review the requirements and instructions outlined in Setting up BMC Server Automation for virtual environments.