Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Requirements for running the installers

This topic provides requirements related to installing the product using the individual component installers. It includes the following sections:

Requirements for installing on Microsoft Windows

ComponentRequirements
Agent
  • For a server to provide information about Windows Group Policy objects, the file secedit.exe must be installed on the server, and it must be included in the server's executable path.
  • If the server is a domain member or domain controller, confirm that the Net Logon service is enabled and running before installing the RSCD agent. The agent uses the Net Logon service to determine the domain and obtain information about the machine. If the server is not part of a Windows domain, the agent uses a different method for determining machine information. Additionally, the automation principal feature uses the Net Logon service to access domain user information so the automation principal can act as a domain user.

    Note

  • The patch analysis function of BMC Server Automation requires the Microsoft XML (MSXML) parser version 6.0 SP2 or later to be installed on the server on which the RSCD agent is installed. You can install the RSCD agent on a computer on which MSXML is not installed, but patch analysis does not function correctly until MSXML 6.0 SP2 or later is installed.
  • If you are using Windows Terminal Services or Citrix Presentation Server to install or if you are installing on Windows 2003 or 2008, use one of the following methods to install:
Application Server (and NSH)
  • To perform this installation, you must have local administrator privileges.
  • If you are using Windows Terminal Services or Citrix Presentation Server to install or if you are installing on Windows 2003 or 2008, use one of the following methods to install:
  • You must set up your database schema. See Setting up the database.
  • On 64-bit Windows systems, confirm that the <WINDIR>\SysWOW64 directory contains a copy of the chcp.com file. The installer uses this file to set the code page of standard output (stdout). You can obtain the file from a 32-bit version of Windows.
  • If you plan to use the bljython utility, install the Application Server before installing Jython.
Console (and NSH)
  • BMC recommends that you do not install the console on the same system as the Application Server.
  • Before you install the BMC Server Automation Console, ensure that port 12333 (TCP) is not being used. Installation of the console requires use of this port; if it is already in use, the installation fails.
  • Update the Windows Terminal Services Server Settings for temporary folders. (In Windows Server 2008 R2 and later versions, Terminal Services is renamed to Remote Desktop Services).
    The installation program uses temporary folders to preserve the install log. Usually, you can perform this update only one time; you do not need to update the configuration every time you install the console. However, if your Server Settings are different from those needed for installation, after you finish installing the console you can change the settings back to their previous settings.
NSH only
  • To perform the Network Shell installation, you must have local administrator privileges.
  • If you are using Windows Terminal Services or Citrix Presentation Server to install or if you are installing on Windows 2003 or 2008, use one of the following methods to install:
  • On 64-bit Windows systems, confirm that the <WINDIR>\SysWOW64 directory contains a copy of the chcp.com file. The installer uses this file to set the code page of standard output (stdout). You can obtain the file from a 32-bit version of Windows.

Requirements for installing on UNIX and Linux

ComponentRequirements
All

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 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.
     

In Red Hat version 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

Note that Red Hat Enterprise Linux version 7 is not supported.

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
  • 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
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 the following tables.

Supported platforms for IBM AIX native installers

Operating system

BFF RSCD agent install

BFF NSH install

AIX 5.2

Yes

Yes

AIX 5.3

Yes

Yes

AIX 6.1

Yes

Yes

AIX 7.1

Yes

Yes

 Supported platforms for Linux native installers

Operating system

RPM RSCD agent install

RPM NSH install

SUSE 9.0 x86

Yes

Yes

SUSE 10.0 x86

Yes

Yes

SUSE 11.0 x86

Yes

Yes

SUSE 9.0 x64

Yes

Yes

SUSE 10.0 x64

Yes

Yes

SUSE 11.0 x64

Yes

Yes

Red Hat Enterprise Linux 3.0 x86YesYes
Red Hat Enterprise Linux 4.0 x86YesYes
Red Hat Enterprise Linux 5.0 x86YesYes

Red Hat Enterprise Linux 6.0 x86

Yes

Yes

Red Hat Enterprise Linux 4.0 x64

Yes

Yes

Red Hat Enterprise Linux 5.0 x64YesYes
Red Hat Enterprise Linux 6.0 x64YesYes
Red Hat Enterprise Linux 4.0 (zSeries)YesNo
Red Hat Enterprise Linux 5.0 (zSeries)YesNo
Red Hat Enterprise Linux 6.0 (zSeries)YesNo

Cent OS 4.6 x86

Yes

Yes

Cent OS 5.2 x86

Yes

Yes

Cent OS 4.6 x64

Yes

Yes

Cent OS 5.2 x64

Yes

Yes

Oracle Enterprise Linux 4.0 x86

Yes

Yes

Oracle Enterprise Linux 5.0 x86

Yes

Yes

Oracle Enterprise Linux 6.0 x86

Yes

Yes

Oracle Enterprise Linux 4.0 x64

Yes

Yes

Oracle Enterprise Linux 5.0 x64

Yes

Yes

Oracle Enterprise Linux 6.0 x64

Yes

Yes

 Supported platforms for Oracle Solaris SVR4 package native installers

Operating system

Package RSCD agent install

Package NSH install

Solaris 9 x86YesYes
Solaris 10 x86YesYes
Solaris 10 x64YesYes
Solaris 11 x64YesYes

Solaris 9.0 SPARC

Yes

Yes

Solaris 10.0 SPARC

Yes

Yes

Solaris 11.0 SPARCYesYes

Supported platforms for Debian package native installers

Operating system

Package RSCD agent install

Package NSH install

Debian 5.0 x86YesYes
Debian 6.0 x64YesYes
Debian 5.0 x86

Yes

Yes
Debian 6.0 x64YesYes
Ubuntu 10YesYes
Ubuntu 11YesYes
Ubuntu 12YesYes

Note

BMC supports use of the Debian package installer only for installation of the Network Shell or the RSCD agent. BMC does not support using the Debian package installer to upgrade these components. To upgrade, you must uninstall the earlier version and install the version to which you want to upgrade.

For information about using these installers, see:

 



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

Comments