If you are installing Access Manager components on multiple machines, ensure that the time and date are synchronized on all machines.
Ensure that the Administration Console is running. (See Section 2.0, Installing the Administration Console.)
Do not perform any configuration tasks in the Administration Console during an Identity Server installation.
If you installed the Administration Console on a separate machine, ensure that the DNS names resolve between the Identity Server and the Administration Console.
When you are installing the Identity Server on a separate machine (recommended for production environments), ensure that the following ports are open on both the Administration Console and the 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 you are installing the Identity Server on a machine with the Administration Console (not recommended for production environments), do not run simultaneous external installations of the Identity Server and Access Gateway. These installations communicate with the Administration Console. During installation, Tomcat is restarted, which can disrupt the component import process.
Verify that the machine meets the minimum requirements. See Section 3.2.1, Installation Requirements on Linux.
You must establish a static IP address for your Identity Server to reliably connect with other Access Manager components. If the IP address changes, the Identity Server can no longer communicate with the Administration Console.