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.

Minimum software requirements

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

Supported databases

The BMC Server Automation product supports the following database types and versions:

Database type Supported versions
Oracle
  • 11g R2
  • 11g R2 RAC

Note

Microsoft SQL Server
  • 2008
  • 2008 Cluster
  • 2008 R2
  • 2008 R2 Cluster

Oracle 11.2.0.2 patch requirement

If you plan to use Oracle version 11.2.0.2 as the database for BMC Server Automation, before you install BMC Server Automation, you must install the appropriate patch to Oracle 11.2.0.2:

  • Linux and UNIX platforms: Patch 9620994
  • Windows 32 and 64-bit platforms: Oracle 11.2.0.2 Patch 4 (or later) bundle, which contains Patch 9620994.

To determine if this patch is installed on your Oracle 11.2.0.2 database:

  1. On the database server, ensure that the ORACLE_HOME variable is set to the 11.2.0.2 installation directory.
  2. Run the command to locate Patch 9620994:
    • Linux and UNIX platforms:
      $ORACLE_HOME/OPatch/opatch lsinventory | grep 9620994
    • Windows:
      %ORACLE_HOME%\OPatch\opatch lsinventory | findstr 9620994

JRE version for the Application Server and RCP client

The Application Server and the RCP client works with Java RunTime Environment (JRE), version 1.6.0_37. This JRE version is installed automatically by the product installer.

Requirements for GUI support on 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 should have version GTK+ 2.2.1 and its dependencies or above.

Requirements for installing the Application Server, BMC Server Automation Console, or Network Shell on Linux

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

Note

In Red Hat version 6 the package name has changed to compat-libtermcap.To check if compat-libtermcap is installed you can run:

rpm -q compat-libermcap

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

To run any of the GUI-based Application Server configuration utilities, the OS-specific x11 libraries for the supported variants of UNIX should have version GTK+ 2.2.1 and its dependencies or above.

Requirements for installing the RSCD agent on Linux

For the RSCD agent on the s390 platform (SUSE or other Linux platforms), the supported C++ library is compat-libstdc++-7 and above. 

Virtualization support

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


Supported virtual environments

Platform

For requirement information, see

VMware vCenter environment

Reviewing minimum requirements for VMware environments

Solaris Zones environment

Reviewing minimum requirements for Solaris Zones environments

IBM Frame environment

Reviewing minimum requirements for IBM PowerVM environments

Microsoft Hyper-V environment

Reviewing minimum requirements for Microsoft Hyper-V environments

Red Hat Enterprise Linux

Reviewing minimum requirements for Red Hat environments

Citrix XenServer

Reviewing minimum requirements for Citrix XenServer environments

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

Perl support

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

Operating system

Supported version of Perl

Microsoft Windows XP, 2003, 2008, and Vista

ActiveState Perl 5.16

Oracle Solaris 8, 9, and 10

Perl 5.8.8

Red Hat Linux 2.1 AS/ES, 3.0 AS/ES, 4.0 AS/ES, and 5.0 AS/ES

Perl 5.8.8

Novell SUSE SLES 9.x and 10.x

Perl 5.8.8

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.

BMC BladeLogic Decision Support for Server Automation requirements

This section describes the requirements for installing and using BMC BladeLogic 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 BladeLogic Decision Support for Server Automation, see the BMC BladeLogic Decision Support for Server Automation Release Notes.
  • 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 BladeLogic 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 BladeLogic 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 BladeLogic Decision Support for Server Automation site context to use the modified details. To change the site context, run the set context command by using the Report Administration Utility. For more information about this command, see the BMC BladeLogic Decision Support for Server Automation User Guide.

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 on obtaining and applying the patch, see the Oracle Sun website.

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

Comments