Ensure that the system meets the requirements for installing Identity Server.
For information about the requirements, see NetIQ Access Manager System Requirements.
If you are 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 you are 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 how to open ports, see Configuring the Linux Administration Console Firewall and Configuring the Windows Administration Console Firewall.
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.