Requirements for installing on Linux using the unified product installer

This topic describes the requirements for installing BMC Server Automation on on Linux platform using the unified product installer.

The topic includes the following sections:

Requirements for using the unified product installer on Linux

Before installing BMC Server Automation using the unified product installer, ensure that you have performed the prerequisite tasks relevant to your operating system:

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

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


Ensure that you have a supported version of Perl installed on the host computer on which you are installing BMC Server Automation. (For information about the Perl versions that BMC 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 BMC 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.
  • Verify that the umask is 0022 for the root users on the Application Server host computer.
  • BMC 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 an 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 an RSCD agent (Windows).

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.

During installation, default security settings are applied to the Application Server and file server. BMC recommends that you adjust the security level on the Application Server host computer and the file server host computer after completing the installation, based on your unique needs and the IT security policies at your organization.

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:

*rw, user=root

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, BBSA<version_number>-<platform>\files\installers\other_files\\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 and shared library installed. Install the shared library before installing these components. For more information, see Requirement for installing the Application Server, BMC 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
Temp spaceEnsure that you have at least 4 GB of /tmp space for Linux installs.

Limitations when using the unified product installer 

The unified product installer does not support the following scenarios:

  • 32-bit Windows or 32-bit Linux machines
  • Solaris SPARC machines

  • A heterogeneous environment where the Application Servers and PXE server are not all installed on the same operating system. 

  • The unified product installer requires the database to be Oracle for Linux environments and SQL Server for Windows environments. In the case of Linux, you can use the Oracle Express database edition shipped with BMC Server Automation (for testing purposes) during the evaluation period for the express database edition. However, you must upgrade to Oracle Enterprise edition, after the evaluation period is over.

Where to go from here

Installing using the unified product installer

Was this page helpful? Yes No Submitting... Thank you