Compliance Content support and requirements

Core product

The computer on which you run the BMC Server Automation installer to install the Compliance Content libraries must have the following BMC Server Automation components installed:

• BMC Server Automation Application Server installed
  
  If the BMC Server Automation Application Server was installed using the -local option, ensure that the NSHDIR, LD_LIBRARY_PATH, and PATH environment variables were set correctly on the Application Server host computer. For information, see Installing components in non-default installation paths using the local flag.
• Network Shell installed

• RSCD agent installed and running. The RSCD agent must be licensed (if it is running on versions earlier than 8.2). In addition, root equivalency for the RSCD agent must be set.

Memory

2 GB of RAM

Disk space

Up to 8 GB, depending on how many content libraries you install

600 MB of temporary space

Installer

For the installer to function properly, you must ensure that the following requirements are met:

• Port 12333 (TCP) is free for use by the installer.
• On Linux and UNIX systems, you must have an X Window server installed and configured.
• On Red Hat Enterprise Linux systems, to support Compliance Content installation, you must have the following 32-bit library files (.i386 or .i686 extension) installed:
  • libstdc++-33 or compat-libstdc++-33

  • libtermcap (see further information about the libtermcap library)

  • libXi
  • libXext
  • libX11
  • (Red Hat Linux 6 or later) libxcb
  • libXau
  • libXtst
  • libXrender
  • glibc
  • gtk2

The OS user running the installer must also be granted root privileges through the users.local file on the Application Server and needs write access to the Applications Servers and File Server storage location.

For example, if you are logged onto the OS and you started the Compliance Content installer as Administrator, you need to have an entry such as the following in the users.local file on the Application Server(s) and File Server targeted by the installer:
Administrator rw,map=Administrator,hosts=<ip of system running content installer>

Or, if you are running the Compliance Installer as root:
root rw,map=root,hosts=<ip of system running content installer>

If the system that you are running the Compliance Content Installer from is configured to use a NSH proxy, you must ensure that the profile name used to authenticate in the Compliance Content Installer is configured in the local secure file as described in Setting up a Network Shell client to run in proxy mode.

2.0.1 of June, 2016
(as of BSA 8.9.01)

2.1.0 of June, 2016
(as of BSA 8.9.01)

2.2.0 of April, 2016

Version 6/
Release 1.31
of October, 2015

Version 2/Release 4

of April, 2016

Version 2/Release 4

of April, 2016

Version 2/Release 4

of April, 2016

Version 1/Release 1. 20 of January 2017 (As of BSA 8.9.02)

Version 1/
Release 14
of April, 2016

Version 1/Release 1. 27 of February 2017 (As of BSA 8.9.02)

Version 1/Release 3 of July, 2013
(as of BSA 8.5.01)

(as of
BSA
8.5.01)

(as of
BSA
8.5.01)