Ensure that the system meets the requirements for installing Identity Server.
For information about the requirements, see NetIQ Access Manager System Requirements.
When installing Access Manager components on multiple machines, ensure that the time and date are synchronized on all machines.
Ensure that the hard disk has ample space for logging in a production environment. This disk space must be local and not remote.
Ensure that Administration Console is running. See Installing Administration Console.
Do not perform any configuration tasks in Administration Console during an Identity Server installation.
If you installed Administration Console on a separate machine, ensure that the DNS names resolve between Identity Server and Administration Console.
When installing Identity Server on a separate machine (recommended for production environments), ensure that the following ports are open on both Administration Console and Identity Server:
For information about ports, see Configuring the Administration Console Firewall.
NOTE:Install the insserv-compat package for SLES installation.
IMPORTANT:When installing Identity Server on a machine with Administration Console (not recommended for production environments), do not run simultaneous external installations of Identity Server and Access Gateway. These installations communicate with Administration Console. During installation, Tomcat is restarted, which can disrupt the component import process.
You must establish a static IP address for your Identity Server to reliably connect with other Access Manager components. If the IP address changes, Identity Server can no longer communicate with Administration Console.
If you have custom partitioned your hard disk as follows, ensure that the free disk space mentioned against each partition is available:
|
Partition |
Disk Space |
|---|---|
|
/opt/novell |
1 GB |
|
/opt/volera |
5 MB |
|
/var/opt/novell |
1 GB |
|
/var |
512 MB |
|
/usr |
25 MB |
|
/etc |
1 MB |
|
/tmp/novell_access_manager |
10 MB |
|
/tmp |
10 MB |
|
/ |
512 MB |
NOTE:These are the minimum free disk spaces that must be available before installation or upgrade. However, it is recommended to maintain more than the specified free disk space based on the requirement of your production environment.
(Conditional) For SLES, ensure that the following packages are installed:
rsyslog-module-gtls - The required TLS encryption support module for rsyslog
rsyslog - The required software for forwarding audit messages
bind-utils - The package contains utilities (host, dig, and nslookup) used to test and query the Domain Name System (DNS) and also the libraries required for the base ‘Bind’ package
glibc-32bit - To install the 32bit glibc libraries on 64 bit Ubuntu
iputils - This package contains small network tools for IPv4 and IPv6 like ping, arping, and tracepath
(Conditional) For installing RHEL packages manually, see Installing Packages and Dependent RPMs on RHEL for Access Manager.
NOTE:You can select to install these RPMs automatically along with Access Manager installation. While installing Access Manager, specify N when you get the following prompt:
Enter the local mount directory if you have the OS ISO mounted locally. This will be used as the local catalog for the additional rpms. Do you have a locally mounted ISO (y/n)?
The Access Manager installer checks the online catalog and then installs the required RPMs automatically.
gettext
python (interpreter)
IMPORTANT:
No LDAP software, such as eDirectory or OpenLDAP, can be installed. (A default installation of SLES installs and enables OpenLDAP).
If the OpenLDAP server is installed, uninstall it. If you do not want to uninstall it, ensure that it does not use the port 636 or does not bind the port 389 to localhost.
Because of library update conflicts, you cannot install Access Manager on a Linux User Management (LUM) machine.
For information about browser support, see Browser Support in NetIQ Access Manager System Requirements.
For information about network requirements, see Section 1.3, Network Requirements.