Before installing BMC Atrium Single Sign-On, review the following requirements:
You cannot deploy BMC Atrium Single Sign-On on a Network File System (NFS) system. (LINUX and Oracle Solaris) The $TMP directory must have execute permissions for running the BMC Atrium Single Sign-On installer. You can assign the execute permissions by removing the Remove the For more information see,Installation failure due to insufficient execute permissions. The BMC Atrium Single Sign-On server supports the following operating systems and platforms. The server supports the listed version and later versions of vendor products. Note The Tomcat 6.x and later web/application server and servlet engine are supported on all operating systems and platforms supported by BMC as defined in the Supported hardware platforms and operating systems section. FirewallsThe ports that you selected when you installed the BMC Atrium Single Sign-On server must be accessible from the clients that are authenticated through the server. Configure the firewalls to allow access to the HTTPS port used for authentication, as well as the LDAP and Apache MQ ports in the nodes of a cluster. BMC Atrium Single Sign-On requires at least Java 6.0 or later.Supportedvendor is: Java SE 6 - 1.6.0_28 (32-bit or 64-bit) Java SE 7 - 1.7.0_17 (32-bit or 64-bit) Java SE 8 - 1.8.0_66 (32-bit or 64-bit) Note Oracle refers to Java 1.6 as “6.0”. For more details, see Java SE Naming and Versions. Supported platforms for BMC Atrium Single Sign-On agents Atrium Single Sign-On supports Atrium Single Sign-On agents running on the following operating systems versions or later versions. Operating Systems - Best performance Other Operating Systems If you are installing BMC Atrium Single Sign-On on Red Hat Enterprise Linux computers, the entropy level on the server must be at least 3000. Otherwise, you might experience installation issues. If an installation or silent installation aborts suddenly, finishes veryquickly,or takes a long time to complete, the computer might be experiencing low entropy issues. To avoid these issues, perform the following tasks: If the level of entropy is less than 3000, run the following commands as root user or restart your computer. Running the command is the preferred option as it helps in maintaining the entropy level after installation. If your server has a low entropy level, you should configure your server to run the following commands while starting up your server. You must also ensure that the "rngd" process is running.Limitation
Access and permissions
noexec
attribute from the /tmp
line in the /etc/fstab
file. For example,UUID=0aef28b9-3d11-4ab4-a0d4-d53d7b4d3aa4 /tmp ext4 defaults,noexec 1 2
noexec
attribute from the line and save the file.UUID=0aef28b9-3d11-4ab4-a0d4-d53d7b4d3aa4 /tmp ext4 defaults 1 2
Supported hardware platforms and operating systems
Platform Vendor products 32-bit or 64-bit x86 compatible PC Oracle SPARC Solaris 10 (64-bit only) 64-bit x86 compatible PC Red Hat Enterprise Linux 5, 6, 7 (64-bit only, for Server Editions) Sizing Information
Parameter Small environment Medium environment Large environment CPU 2 CPU 4 CPU 4 CPU RAM 4 GB 4 GB 8 GB Storage configuration 100 GB 100 GB 100 GB Supported browsers
Supported web or application servers
Java support
Operating system Vendor Minimum recommended versions Windows, Solaris, Linux (Red Hat) Oracle Entropy level requirements
yum install rng-tools
echo 'EXTRAOPTIONS="-i -o /dev/random -r /dev/urandom -t 10 -W 2048"' >>/etc/sysconfig/rngd
chkconfig rngd on
service rngd restart
1 Comment
Sanjay Prahlad