Page tree

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

The topic includes the following sections:

Requirements for using the unified product installer on UNIX and Linux

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

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

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.

Perl

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. (For information about the Perl versions that BMC Server Automation supports, see Perl support.)
  • 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
  • Set the umask for the root users to 0027 or 0022 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:
    • Set core files to unlimited: ulimit -c unlimited
    • Set the number of open file descriptors to 8192: ulimit -n 8192
  • 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).
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.

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\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, BMC Server Automation Console, or Network Shell on Linux.
  • For Red Hat Enterprise Linux version 6 x64 KVM, ensure that the glibc package is installed.
  • If you are using the RedHat offline patch downloader, ensure that the glibc.i686 library is present (due to Java 8.1 imbedded JRE).
Software and hardware

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.
     

Requirements for installing product components on UNIX and Linux

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

ComponentRequirements
All

Requirement for RedHat Enterprise Linux (RHEL) version 4 and 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, the agentctl start command fails to restart the RSCD Agent after the Agent is installed using a shell based installer.

As a workaround, run ln -s /lib64/libtinfo.so.5 /lib64/libtermcap.so.2 command before installing RSCD Agent.

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, BMC 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 0027 or 0022 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 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
  • If you are installing the RSCD agent on a computer running Red Hat Enterprise Linux version 6 x64 KVM, make sure that the glibc package is installed.
  • 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.

  • If you are installing the RSCD agent on a computer running Red Hat Enterprise Linux version 6 x64 KVM, make sure that the glibc package is installed.
Console
  1. Navigate to the directory containing installation files and run the installation script for the BMC Server Automation Console. (Script names follow the convention: BBSACONSOLEversion-platform.) You must execute the installation from a root shell. Do not execute the installation script from a non-root account.
  2. The BMC BladeLogic Server Automation Suite Installation window opens.
  3. Select a language, and then click OK.
    A series of messages indicate progress. This process might take several minutes. Then the Introduction window opens.
  4. Click Next.
    The Review License Agreement page opens.
  5. To accept the license agreement, select I agree to the terms of the license agreement, and then click Next.
    The User Inputs window opens.
  6. (optional) Remove the check marks from any components that you do not want to install, and then click Next.
    A series of messages indicate progress.
  7. (optional) Select Check to install the default .nsh resource files into /etc/skel.
  8. Click Next.
    The Installing window displays the features to be installed.
  9. To install, click Install. To change your selections, click Previous.
    A series of messages indicate progress. This process might take several minutes. Then the Installation Complete window opens, indicating successful installation.
  10. (optional) Click View Log.
  11. Click Done.
    The window closes. Installation is complete.
NSH onlyLinux 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, BMC Server Automation Console, or Network Shell on Linux.

Required ports for installers

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

  • Before you install the BMC 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 BMC 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.For more information about the platforms that support installation using a native installer, see "Supported platforms for native installers" under Supported platforms for version 8.7. 

Where to go from here

Installing using the unified product installer

Installing individual components

  • No labels