If you are installing the Access Manager components on multiple machines, ensure that the time and date are synchronized on all machines.

Make sure that the Access Manager Administration Console is running. (See Installing the Access Manager Administration Console.) However, you must 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), you need to ensure that the following ports are open on both the Administration Console and the Identity Server:

• 8444
• 1443
• 1289
• 524
• 636

For information on how to open ports, see Section 3.2, Configuring the Administration Console Firewall.

When you are installing the Identity Server on the same machine as the Administration Console (not recommended for production environments), do not run simultaneous external installations of the Identity Server, Access Gateway, J2EE Agent, or SSL VPN because 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 2.5, Identity Server Requirements.

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.