Prerequisites for installation
This topic describes the prerequisites for installing BMC Atrium Single Sign-On.
If you have not met all of the requirements before you begin the installation, you might have issues with the installation.You must fulfill the necessary requirements on this page before you begin with installation.
Do not deploy BMC Atrium Single Sign-On on an Network File System (NFS) file system.
Access and permissions
- If you are a nonroot runtime user of the BMC Atrium Single Sign-On web container instance, you must be able to write to your own home directory.
- (Microsoft Windows) You must have administrator privileges.
- (UNIX) You can be any user. However, root privileges are required to set up auto-startup of the services.
Disk space requirements
This section contains information about prerequisite storage space requirements for installation and log files.
Before installing BMC Atrium Single Sign-On, you must have at least the following available disk space:
- (Microsoft Windows) 650 MB
- (Linux) 750 MB
- (Oracle Solaris) 850 MB
If you are installing BMC Atrium Single Sign-On on an external Tomcat server, 1024K of RAM is required. For an extremal Tomcat 7 server and JDK 1.7, increase memory an additional 20% for a minimum of 1.2 MB.
Log file memory requirements
An additional 7-10 GB of space is recommended for log file growth, depending on the volume of users and products integrating with the BMC Atrium Single Sign-On server.
To manage log file storage space effectively, perform the following tasks:
- Delete the debug log files periodically, especially if the debug level is set to message.
- Check the .access and .error log files periodically in the logs directory.
- Consider configuring the log rotation to delete the oldest log files.
If you are installing BMC Atrium Single Sign-On on Red Hat Enterprise Linux (RHEL) 6.x, you must install the following 32-bit RPM packages to make 32-bit JRE support and the user interface available to the installer:
Entropy level requirements
If you are installing BMC Atrium Single Sign-On on Red Hat Enterprise Linux computers and the entropy level on the server is under 3000, you might experience installation issues. If an installation or silent installation aborts suddenly, finishes very quickly, or takes a long time to complete, the computer might be experiencing low entropy issues. To avoid these issues, perform the following tasks:
- Verify the level of entropy in the entropy_avail file at the following location:
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.rngd
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
The 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.